Yes, this would be a request to get libz.a with the release. Whatever the minimal to get the example here working would be: https://freebasic.net/wiki/ExtLibzlib
To be honest I did not check the /bin directory for zlib1.dll. I suppose it wouldn't be the hardest to create the dll.a from that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah, I see. It may be helpful for me to report that the last couple of months I have been working on JayRM's FreeBASIC Load Out which includes a static build of libz.a plus the associated .bi header.
I am thinking I prefer this approach of separating compiler releases from other products to make fbc releases more efficient and maintainable. Because nothing in fbc compiler itself requires zlib.a to be present and ensuring that the correct library version is included and is working is just another extra point of failure for making a good compiler release. And if zlib.a is included, why not all library packages? It's too many. Maybe compiler release and extra packages can be combined in future for one whole comprehensive package (or some other contributor is welcome to do that and release it) but for now it is much more manageable to have them separated.
If you accept that separate download for zlib.a is acceptable, I will close the ticket. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Which release package exactly?
zlib1.dll has been included in every release since fbc-1.00.0
This is a feature request to include static
libz.awith the release?Release package: FreeBASIC-1.10.0-win64
Yes, this would be a request to get
libz.awith the release. Whatever the minimal to get the example here working would be: https://freebasic.net/wiki/ExtLibzlibTo be honest I did not check the /bin directory for
zlib1.dll. I suppose it wouldn't be the hardest to create the dll.a from that.Ah, I see. It may be helpful for me to report that the last couple of months I have been working on JayRM's FreeBASIC Load Out which includes a static build of
libz.aplus the associated.biheader.I am thinking I prefer this approach of separating compiler releases from other products to make fbc releases more efficient and maintainable. Because nothing in fbc compiler itself requires zlib.a to be present and ensuring that the correct library version is included and is working is just another extra point of failure for making a good compiler release. And if zlib.a is included, why not all library packages? It's too many. Maybe compiler release and extra packages can be combined in future for one whole comprehensive package (or some other contributor is welcome to do that and release it) but for now it is much more manageable to have them separated.
If you accept that separate download for zlib.a is acceptable, I will close the ticket. Thanks.
That sounds reasonable. I'll look forward to it's release then.
FYI, libz.a and header is available in the release packages linked. Thank you.