| |
| |
On 8/4/24 18:50, 'Albrecht Schlosser'
via fltk.coredev wrote:
Questions regarding the library filenames you posted above:
1. How would we find the '*16*' versions of libpng? On Unix/Linux
systems there's usually a symbolic link from a non-versioned name
to the versioned name which we can use. In your case we can't
guess.
Use find_package(PNG). It will handle that for you looking for
extension names.
2. It
looks like you have two jpeg libs, 'jpeg-static.lib' and
'turbojpeg-static.lib'. According to their names these would be
two different static libs of 'libjpeg'. How could any build system
decide which one of these you *want* to use?
I could be wrong, but I believe they are the same. turbojpeg keeps
backwards compatibility with libjpeg.
3. What are these two files 'libpng16.cmake' and
'libpng16-release.cmake' good for? According to their names they
don't look like CMake CONFIG files which should be named
PNGConfig.cmake or similar, AFAICT.
Not sure.
Thanks in advance.
I opened Issue #949 with a project using ExternalProject_Add of
the FLTK libraries I mentioned. It is a tad convoluted, but you
should be able to follow it. You can run it on all platforms.
For Windows you will need MSys64 and MSVC2019 or MSVC2022 (I added
.bat files for them).
--
Gonzalo Garramuño
ggarra13@gmail.com
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/89599518-dc45-4420-8e06-86a5f4f5cba6%40gmail.com.
[ Direct Link to Message ] | |
|
| |
