Re: [Help-glpk] [Fwd: Build glpk as a shared library on Cygwin, MinGW and similar systems]

[Jean-Pierre Flori]

2014-11-04 17:30 GMT+01:00 Marco Atzeri <address@hidden>:
> On 11/4/2014 5:11 PM, Jean-Pierre Flori wrote:
>>
>> Hey,
>>
>> I agree, but they may also end up being passed to the linker.
>
>
> Not that I am aware of. Libtool is correctly calling the linker.
>
Sure, but some evil software mix libtool with direct calls to the
compiler and linker.

>> And some of them choke when given flags they don't recognize.
>> IIRC I had this kind of issues with packages using gcc to link files.
>>
>> In fact, I just found the following of yours :)
>> http://cygwin.com/ml/cygwin/2013-07/msg00414.html
>
>
> It is the reason why in the patch that portion is at the end of the
> configure.ac otherwise it will be used by autoconf tests
>
And that's the reason why using lib*_la_LDFLAGS can help.
Of course it's not generic, so must be customized for each package and
therefore requires more work.
So it perfectly makes sense for someone maintaining a lot of cygwin packages.
In case of one particular upstream project, the other solution can be safer.
Please don't understand I say your solution is wrong, both have pros
and cons, that's all.

And as I said, as long as something gets merged into GLPK, I'll be happy.

Best,

--
Jean-Pierre Flori