> Your object files are created without using libtool?
Yes, just g++.
>
> > ln: creating symbolic link `libGUI.so.0': Operation not supported
> > make: *** [libGUI.so] Error 1
>
> That's a new one for me, you snipped the ln command that fails though.
>
> I don't know how much you care about po
On 10/14/2011 08:45 AM, David Aldrich wrote:
Hi Peter
Thanks for your reply.
-shared is not a libtool flag
Oh, that's weird! We've been using that option for building other shared
libraries for a long time.
Yes, and older libtools used to pass it along to the compiler driver, so
on system
Hi Peter
Thanks for your reply.
> -shared is not a libtool flag
Oh, that's weird! We've been using that option for building other shared
libraries for a long time.
> does it work if you do:
>
> libtool --mode=link g++ -o libGUI.la -rpath /usr/local/lib
>
That doesn't work, but the result i
On 10/14/2011 02:10 AM, David Aldrich wrote:
Hi
I am using libtool in a makefile to create a shared library containing my
application code, which also links to wxWidgets libraries. As a consequence of
changing both platform (including gcc version) and wxWidgets packages, my
makefile ceases t
Hi
I am using libtool in a makefile to create a shared library containing my
application code, which also links to wxWidgets libraries. As a consequence of
changing both platform (including gcc version) and wxWidgets packages, my
makefile ceases to work. It seems that the libtool command is
Hi
I am using libtool in a makefile to create a shared library containing my
application code, which also links to wxWidgets libraries. As a consequence of
changing both platform (including gcc version) and wxWidgets packages, my
makefile ceases to work. It seems that the libtool command is
Hi
I am using libtool in a makefile to create a shared library containing my
application code, which also links to wxWidgets libraries. As a consequence of
changing both platform (including gcc version) and wxWidgets packages, my
makefile ceases to work. It seems that the libtool command is t
