From: Jack J. <ja...@or...> - 2001-09-05 09:33:53
|
> two - more importantly, that sometimes tcl extension authors want to > offer the option of link against the extension libraries instead of > dynamically loading them e.g. to make available additional private > symbols in addition to the standard blah_Init and blah_SafeInit that > the dynamic loader binds. Ah. I now realise that I didn't tell everything. I'm building the core Python as a framework bundle (giving all the advantages of easy install, etc), but I'm not building the extension modules as plugin bundles. They're plain old .dylib shared libs. The core framework bundle already gives me all the advantages I want (relocatability from /Library to ~/Library by the user, self-containedness, version control, sharing between various apps such as the command line tool and the fullblown application, etc). Adding plugin bundles didn't seem worth the effort, and indeed your message seems to indicate it's not the right way to go. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jac...@or... | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm |