Re[3]: MSW DLLs support in libtool

2016-02-09 Thread Vadim Zeitlin
On Tue, 9 Feb 2016 21:29:23 -0600 (CST) Bob Friesenhahn wrote: BF> On Wed, 10 Feb 2016, Vadim Zeitlin wrote: BF> > BF> > Sorry but this is just not true for the MSW DLLs. If the libtool user BF> > tries to build a DLL, you can safely assume that it will not have undefined BF> > symbols. Anythin

Re[2]: MSW DLLs support in libtool

2016-02-09 Thread Vadim Zeitlin
On Tue, 9 Feb 2016 21:18:42 -0600 (CST) Bob Friesenhahn wrote: BF> On Tue, 9 Feb 2016, Vadim Zeitlin wrote: BF> > BF> > 2. Enabling this option is not enough as you must also painstakingly add BF> > -no-undefined to all LDFLAGS. Why does libtool need to force you to do BF> > it instead of ju

Re[2]: MSW DLLs support in libtool

2016-02-09 Thread Bob Friesenhahn
On Wed, 10 Feb 2016, Vadim Zeitlin wrote: Sorry but this is just not true for the MSW DLLs. If the libtool user tries to build a DLL, you can safely assume that it will not have undefined symbols. Anything else just doesn't make sense because it would always result in an error. Again, this is di

Re: MSW DLLs support in libtool

2016-02-09 Thread Bob Friesenhahn
On Tue, 9 Feb 2016, Nick Bowler wrote: In retrospect, the default (assume undefined symbols are possible) was probably a bad choice, because undefined symbols in libraries are rarely used. Thus, almost all libraries need to specify -no-undefined. But this can't be changed now without causing r

Re: MSW DLLs support in libtool

2016-02-09 Thread Bob Friesenhahn
On Tue, 9 Feb 2016, Vadim Zeitlin wrote: 2. Enabling this option is not enough as you must also painstakingly add -no-undefined to all LDFLAGS. Why does libtool need to force you to do it instead of just using it unconditionally for all MSW DLLs knowing that they can *never* have any undef

Re[2]: MSW DLLs support in libtool

2016-02-09 Thread Vadim Zeitlin
On Tue, 9 Feb 2016 18:44:24 -0500 Nick Bowler wrote: NB> On 2/9/16, Vadim Zeitlin wrote: NB> > I'd like to create Windows binaries for my software from Linux, which NB> > includes creating a couple of DLLs and EXEs that use them. This is not too NB> > difficult to do with just manual makefiles a

Re: MSW DLLs support in libtool

2016-02-09 Thread Nick Bowler
On 2/9/16, Vadim Zeitlin wrote: > I'd like to create Windows binaries for my software from Linux, which > includes creating a couple of DLLs and EXEs that use them. This is not too > difficult to do with just manual makefiles as both the cross-compiler and > linker work just fine. Libtool is anoth

MSW DLLs support in libtool

2016-02-09 Thread Vadim Zeitlin
Hello, I'd like to create Windows binaries for my software from Linux, which includes creating a couple of DLLs and EXEs that use them. This is not too difficult to do with just manual makefiles as both the cross-compiler and linker work just fine. Libtool is another matter entirely however: 1.

Rpath issues when attempting to cross compile

2016-02-09 Thread Alex Barker
Hi, I appear to be running into an at least 9 year old issue with rpath and the auto-magic that is libtool paths. According to the docs , the rpath should be calculated for me, however, upon installation, l