Bill Spotz wrote:
I recently came across a bug in swig version 1.3.21 and submitted it to
the SWIG bug tracking system, but it occurred to me that I should try
the latest version of swig to see if it had already been fixed.
The problem is that my build system depends on running "swig -python
-ldflags" to determine the swig library name and location. This worked
fine in swig 1.3.21, but -ldflags is not a valid command line option in
1.3.22. Why was this capability removed? Why is there no deprecation
warning? Is there a workaround so that I can get the same functionality?
The location of the swig library has always been determined by using -swiglib.
If you want the runtime library, see the CHANGES / CHANGES.current file where
you should find answers to the rest of your questions.
William
_______________________________________________
Swig maillist - Swig@xxxxxxxxxxxxxxx
http://mailman.cs.uchicago.edu/mailman/listinfo/swig
