You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running configure --help it lists an option --without-zlib. This makes me accordingly assume the default is lcms2 to actually require zlib for something. On my system I need to tell any build system exactly where the correct zlib is located. Configure doesn't seem to have an option to specify the zlib location, so I have to manually ramp up the configure variables, something like this:
But ultimately it seems that extra hassle was for nothing. zlib doesn't seem to be used at all by lcms2? I also grepped for 'zlib.h' and got no hit, except inside the configure script.
Little CMS has no real dependencies at all other than libm. For building the utilities which can be regarded as demos, you need libtiff and libjpeg. Nonetheless, if you don't have those you can still build Little CMS at full functionality. In the case you wish to build the demos, which happens by default on "configure" script, you can link them statically or dynamically. By default it is done dynamically. In the case you wish to build the demos statically, then there is a problem with libtiff because it has a lot of dependencies on the configured codecs. One of the minimal configurations is using libz. Hence, libz is stated as a dependency only for those cases you want to build the demos statically. I specifically want to avoid calls to package manager in configure.
So, you hit an undocumented feature, which is only used for very specialized builds. You can safely ignore this in the command line of configure and follow what is documented in the manual.
When running
configure --help
it lists an option--without-zlib
. This makes me accordingly assume the default is lcms2 to actually require zlib for something. On my system I need to tell any build system exactly where the correct zlib is located. Configure doesn't seem to have an option to specify the zlib location, so I have to manually ramp up the configure variables, something like this:Which is obviously some extra typing work. 🥲
But ultimately it seems that extra hassle was for nothing. zlib doesn't seem to be used at all by lcms2? I also grepped for 'zlib.h' and got no hit, except inside the configure script.
If zlib is obsolete, then the respective zlib support should be removed from the configure script. E.g. also package systems like MacPorts still list zlib as dependency: https://github.com/macports/macports-ports/blob/master/graphics/lcms2/Portfile
The text was updated successfully, but these errors were encountered: