logo       

Re: Version 1.3.22 and -ldflags command line option: msg#00120

programming.swig

Subject: Re: Version 1.3.22 and -ldflags command line option

>>>>> " " == Bill Spotz <wfspotz@xxxxxxxxxx> writes:

> 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.

All of the runtime libraries are now depricated. As I understand
it, swig no longer builds these when it is installed. But there is a
workaround. You now build them yourself. Running:

swig -python -runtime swigrun.i

will produce a file called swigrun_wrap.c. You can then compile
this and link it with your code or put it into a library. It is
equivalent to what the old prebuild libraries were. I kinda like this
system better than what swig used to do.

Mike Romberg
_______________________________________________
Swig maillist - Swig@xxxxxxxxxxxxxxx
http://mailman.cs.uchicago.edu/mailman/listinfo/swig



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise