| |
| |
On 4/9/24 02:03 Gonzalo Garramuño wrote:
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.
OK, I'll look into it...
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.
There's nothing like "the same" regarding two libraries. Yes,
turbojpeg may be backwards compatible (API-wise), but I'd assume
that the ABI is not the same. Therefore, if you link to one library
and compile with the headers of the other library you'll get
undefined behavior and can expect crashes. Didn't you recently
report that using an older FLTK 1.4 header mix with current 1.4
caused you problems, IIRC in this thread???
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).
I looked into your project on issue #949, and indeed, it's too
complex for a quick test. In particular I'm hesitating to download
libs from other sources than the original ones (PNG, IIRC) and I
don't want to install packages like 'nasm' on my test system(s) just
for testing your project.
I'll look into it anyway but I'd rather use a simpler project if you
could provide one that:
- downloads sources only from the original repos (see e.g. our
documentation/src/bundled-libs.dox)
- does not need to install any packages like nasm
- uses the stock libjpeg rather than turbojpeg for simplicity and
consistency with our build
- whatever else you can simplify.
I appreciate your testing and help, but please keep in mind: the
easier your "simple" test projects are for devs, the faster you will
likely get a solution.
That said, if I can look at a demo project and decide to use it in
about half an hour or less and if it works (i.e. I can see the
expected results), then I'll probably give it a try shortly, but if
it takes longer to evaluate it - or I need to modify it for my needs
- then I can't do it until I have a larger time frame available.
Sorry to say that, but that is real life...
--
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/c8e03816-4287-4902-af17-8f59ff853d58%40aljus.de.
[ Direct Link to Message ] | |
|
| |
