Go to file
Jean-Paul Chaput e11bd98f52 Correct for various warnings appearing under gcc 8.3.0 (Debian 10).
Note: We don't suppress warnings due to unused variables or functions,
      as we may need them later or in debug mode...

* Change: In Hurricane::DBo::~DBo, add a noexcept(false) because
    constructed by default destructor of derived classes seems to
    loosen it. The right solution whould be to explicitely define
    all virtual destructors (too lazy for now).
* Change: In Viewer::Script, replace the deprecated
    PyModule_GetFilename() by PyModule_GetFilenameObject(), Unicode
    support again...
2021-10-01 16:12:28 +02:00
anabatic Fix crash in Anabatic::AntennaProtect. 2021-09-30 19:59:28 +02:00
bootstrap Take account of more Python site-packages. 2021-10-01 00:30:10 +02:00
bora Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
coloquinte Add updators to modify cell sizes on the fly in Coloquinte. 2021-01-13 19:10:31 +01:00
crlcore Correct for various warnings appearing under gcc 8.3.0 (Debian 10). 2021-10-01 16:12:28 +02:00
cumulus Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
documentation Updated doc of the new Python/C++ template wrapper. 2021-09-26 17:27:57 +02:00
equinox Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
etesian Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
flute Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
hurricane Correct for various warnings appearing under gcc 8.3.0 (Debian 10). 2021-10-01 16:12:28 +02:00
ispd Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
karakaze Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
katabatic Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
katana Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
kite Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
knik Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
lefdef Migrating doc from Sphinx towards Pelican. 2020-02-03 17:44:15 +01:00
mauka Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
metis Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
nimbus Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
oroshi Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
solstice Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
stratus1 Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
tutorial Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
unicorn Migration towards Python3, first stage: still based on C-Macros. 2021-09-19 19:41:24 +02:00
unittests Migration towards Python 3, stage 2: C++ template wrapper ready. 2021-09-25 17:03:14 +02:00
vlsisapd Remove deprecated C++11 throw() specifications. 2021-10-01 00:26:58 +02:00
.gitignore Various bug corrections to pass the alliance-check-toolkit reference benchs. 2019-05-24 23:57:22 +02:00
Makefile Enabling the user to choose the devtoolset it needs. 2019-03-04 14:20:13 +01:00
README.rst Update doc link for the new Pelican generated one. 2020-02-10 13:38:06 +01:00

README.rst

.. -*- Mode: rst -*-


===============
Coriolis README
===============

Coriolis is a free database, placement tool and routing tool for VLSI design.


Purpose
=======

Coriolis provides several tools to perform the layout of VLSI circuits.  Its
main components are the Hurricane database, the Etesian placer and the Katana
router, but other tools can use the Hurricane database and the parsers
provided.

The user interface <cgt> is the prefered way to use Coriolis, but all
Coriolis tools are Python modules and thus scriptable.


Documentation
=============

The complete documentation is available here, both in pdf & html:

   ./documentation/output/html
   ./documentation/UsersGuide/UsersGuide.pdf

The documentation of the latest *stable* version is also
available online. It may be quite outdated from the *devel*
version.

    https://www-soc.lip6.fr/sesi-docs/coriolis2-docs/coriolis2/en/latex/users-guide/UsersGuide.pdf


Building Coriolis
=================

To build Coriolis, ensure the following prerequisites are met:

* Python 2.7.
* cmake.
* boost.
* bison & flex.
* Qt 4 or 5.
* libxml2.
* RapidJSON
* A C++11 compliant compiler.

The build system relies on a fixed directory tree from the root
of the user currently building it. Thus first step is to get a clone of
the repository in the right place. Proceed as follow: ::

   ego@home:~$ mkdir -p ~/coriolis-2.x/src/support
   ego@home:~$ cd ~/coriolis-2.x/src/support
   ego@home:~$ git clone http://github.com/miloyip/rapidjson
   ego@home:~$ git checkout ec322005072076ef53984462fb4a1075c27c7dfd
   ego@home:~$ cd ~/coriolis-2.x/src
   ego@home:src$ git clone https://www-soc.lip6.fr/git/coriolis.git
   ego@home:src$ cd coriolis

If you want to use the *devel* branch: ::

    ego@home:coriolis$ git checkout devel

Then, build the tool: ::

    ego@home:coriolis$ make install

Coriolis gets installed at the root of the following tree: ::

    ~/coriolis-2.x/<OS>.<DISTRIB>/Release.Shared/install/

Where ``<OS>`` is the name of your operating system and ``<DISTRIB>`` your
distribution.


Using Coriolis
==============

The Coriolis main interface can be launched with the command: ::

    ego@home:~: ~/coriolis-2.x/<OS>.<DISTRIB>/Release.Shared/install/bin/coriolis

The ``coriolis`` script detects its location and setups the UNIX
environment appropriately, then lauches ``cgt`` (or *any* command, with the
``--run=<COMMAND>`` option).

Conversely, you can setup the current shell environement for Coriolis by 
using the helper ``coriolisEnv.py``, then run any Coriolis tool: ::

    ego@home:~$ eval `~/coriolis-2.x/src/coriolis/bootstrap/coriolisEnv.py`
    ego@home:~$ cgt -V