Hi Ralf, thanks for your reply! I don't mind if you are not interested in the code (as I have a workaround), however...
On Mon, Jan 31, 2011 at 4:50 AM, <[email protected]> wrote: > I understand the problem. But dynamically loading shared libraries will > only create more problems for us. Why do you think that dynamically loaded libraries will create more problems? To clarify... you *are* currently using dynamically loaded libraries :-) -- if today what you have is: - re2c code gets transformed to C - C code gets compiled to a .o - setup.py uses swig in the background to generate bindings - a 'glue' SO is generated from the swig code + the .o, linked to libpython What I propose removes several moving parts, so it'll be much easier, and less breakable: - re2c code gets transformed to C - C code gets compiled and linked to a .so cheers, m -- [email protected] -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
