|
Re: renaming the .so in C->python: msg#00146programming.swig
There was a recent thread on how to get libtool and automake to work nicely with SWIG. I posted some solutions for users of the libtool/automake/swig combination, but unfortunately it doesn't seem to have shown up in the archives (weird!). Therefore, I'll post it again shortly (corrected for one small error) and hope it makes it in this time. Sorry to the rest of you for the repeated post. On Wed, 2004-05-26 at 00:21, Martin F Krafft wrote: > I grok the _lib.so naming and interaction with lib.py. However, > since I want to use libtool, I am forced to name my libraries > lib*.so. it sucks. > > So my question: since _lib.so is hardcoded in lib.py as 'import > _lib', is there a better way to customise the name of the .so than > sed? -- Craig Scott, CSIRO (CMIS) Ph: +613 9545 8096 Computers are easy to reboot. Attitudes are much harder. _______________________________________________ Swig maillist - Swig@xxxxxxxxxxxxxxx http://mailman.cs.uchicago.edu/mailman/listinfo/swig |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: [PATCH] assortment of problems: 00146, Marcelo Matus |
|---|---|
| Next by Date: | RE: SWIG and autotools - some solutions (corrected): 00146, Craig N. Scott |
| Previous by Thread: | renaming the .so in C->pythoni: 00146, Martin F Krafft |
| Next by Thread: | RE: renaming the .so in C->python: 00146, William . Fulton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |