Recently adds have been adjusted in PyDtr.py
Examples have been updated (c++ is tested, python fails on my Mac due to a strange python2.6.6 behavior I have to check this)
getRule method of Techno does not throw exception anymore if rule is not found : a NULL Rule* is returned instead.
but getValue methods throw exception if rule is not found
Since in CMakeLists.txt there is already a module target (for c++ library) and some file systems are not case sensitive, the target is still pyMODULE but the OUTPUT_NAME property is set to MODULE
I've updated all the example python scripts.
system component does not exist in boost 1.33
!!!!! Merci de ne commiter AUCUN changement dans vlsisapd tant que Jean-Paul et moi n'avons pas résolu les problèmes de bibliothèques statiques !!!!!!
when defining rule<minSpacing, nWell, active>
and then rule<minSpacing, nWell>
in technology file
the first rule was ever return even if techno.getRule(minSpacing, nWell) was called.
- Library linking: there must not be "target_link_library()" for libraries,
only when building binaries. Avoid clashes between static module
or class variables, and strange reinitialisation of those variables.
- Change: Boost is now always linked staticly.
* agds :
- all agds object now belong to AGDS namespace
- 'Gds' has been removed from all filenames
* cif
- all cif objects now belong to CIF namespace
- 'Cif' has been removed from all filenames
* dtr
- minor modifications in CMakeLists.txt since Boost Python is now used by other driver & parser
ADDS
* agds :
- new python module
* cif
- new python module
* doc
- brand new doxygen documentation with
global presentation
cif format (driver)
agds format (driver)
links & contacts
* examples
- examples files in C++ and Python for cif & agds drivers (others will follow)