Ahhhhh, I wasn't aware of the fact that it has to be specified as an argument not as a variable before the configure script!
My patch makes it possible to specify it with "CXX=my-gcc ./configure"
When compiling with mingw it produces lzip.exe, but the install target still tries to copy lzip, thus failing! AFAIK the only way to find out what extension a given compiler produces is to compile a minimal example and look at the output, which is what I have added to the configure script.
Regards
Klaus
Hello Klaus,
Thank you for the patch.
Klaus Holst Jacobsen wrote:
> I have a patch which will enable the usage of a custom compiler.
You may already use a custom compiler with a command like this:
./configure CXX=your_compiler
See the output of "./configure --help" and the following message:
https://lists.nongnu.org/archive/html/lzip-bug/2020-03/msg00005.html
> It will also enable the use of mingw compiler to compile for windows (and
> recognise the .exe extension for the output)
I don't use Windows, but as far as I know, lzip compiles fine there without
special handling of the .exe extension.
Best regards,
Antonio.