Handle GLPK library naming on windows

[jamiecook]

libglpk.a on linux, GLPK.lib on windows.

[Mizux]

AFAIK this file is for windows only but:

0. I didn't bump it since we use dynamic library (protobuf abseil-cpp) -> May need some extra changes
1. Why talking about Linux naming ?, this file is only a post process for windows, or is it for reference ?
2. Since it is windows only, why using *glpk.lib instead of just glpk.lib i.e. do you have some use case where the "*" is necessary/mandatory ?

BTW thx for this PR we definitively need to take a look at this file before next release

[jamiecook]

I missed that this was windows only, but that is obviously true with the .lib extension. When compiling on windows (so I can use glpk) I get a can't find file error, libglpk.lib doesn't exist but GLPK.lib does. - Jamie http://jamiecook.wordpress.com

…

On Sat, 23 Nov 2024 at 1:07 AM, Mizux ***@***.***> wrote: AFAIK this file is for windows only but: 0. I didn't bump it since we use dynamic library (protobuf abseil-cpp) -> May need some extra changes 1. Why talking about Linux, this file is only a post process for windows 2. In that case why using *glpk.lib instead of glpk.lib i.e. do you have some use case where the "*" is necessary ? BTW thx for this PR we definitively need to take a look at this file before next release — Reply to this email directly, view it on GitHub <#4447 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABE4VASAUQ75C5AKGVPTCT2B5CD5AVCNFSM6AAAAABSGKX7AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHE3TCMZSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>