The Testing Area :: compile-3.3.5.uci



Ref ^thehatsrule^ :
Quote
Side note (Juanito): compile-3.3.5 has /tmp/{png,pngconf}.h points to libpng2's and not libpng12's; In .../include libpng points to libpng2 whereas in .../lib/pkgconfig libpng.pc points to libpng12.pc.  I'm wondering if there's some sort of disrepancy here.

The original idea was to enable the user the choice of selecting which libpng to compile against using /tmp to switch. Perhaps now, several years on, everybody would want to compile against the most recent libpng.

Any comments, should I only include devs for the most recent libpng?

Quote
Perhaps now, several years on, everybody would want to compile against the most recent libpng.
If that were the case, consider using libpng3 instead of libpng2.

Personally I haven't seen any problems with using libpng12 with the applications I've built for DSL.  My guess is that newer libs fix problems, but they appear to not be show stoppers.  If you were to include only the newer png in compile-3.3.5, would that mean packages would need to include a png library either dynamic or built-in?

Quote
If that were the case, consider using libpng3 instead of libpng2

Well OK, but the idea behind compile-3.3.5 was only to provide devs for items in the base dsl...

Looking at the various files in the base:
Code Sample
$ ls -l /usr/lib/libpng*
lrwxrwxrwx 1 root root 18 Feb 19 2008 /usr/lib/libpng.so.2 -> libpng.so.2.1.0.12
-rw-r--r-- 1 root root 175132 Jun 25 2005 /usr/lib/libpng.so.2.1.0.12
lrwxrwxrwx 1 root root 20 Feb 19 2008 /usr/lib/libpng10.so.0 -> libpng10.so.0.1.0.15
-rw-r--r-- 1 root root 130244 Jun 25 2005 /usr/lib/libpng10.so.0.1.0.15
lrwxrwxrwx 1 root root 19 Feb 19 2008 /usr/lib/libpng12.so.0 -> libpng12.so.0.1.2.5
-rw-r--r-- 1 root root 134384 Jun 25 2005 /usr/lib/libpng12.so.0.1.2.5

In terms of age from oldest to most recent, I have a feeling it goes libpng10.so.0.1.0.15 -> libpng.so.2.1.0.12 -> libpng12.so.0.1.2.5 based on the dates of the source tarballs in various archives, but I could easily be wrong.

Looking at the files in compile-3.3.5.uci:
Code Sample
$ ls -l /opt/compile-3.3.5/include/libpng*
/opt/compile-3.3.5/include/libpng [-> /opt/compile-3.3.5/include/libpng2]

/opt/compile-3.3.5/include/libpng10:
png.h
pngconf.h

/opt/compile-3.3.5/include/libpng12:
png.h
pngconf.h

/opt/compile-3.3.5/include/libpng2:
png.h
pngconf.h

$ ls -l /opt/compile-3.3.5/include/png*
lrwxrwxrwx 1 root staff 10 May 10 17:59 /opt/compile-3.3.5/include/png.h -> /tmp/png.h
lrwxrwxrwx 1 root staff 14 May 10 17:59 /opt/compile-3.3.5/include/pngconf.h -> /tmp/pngconf.h

$ ls -l /tmp/png*
lrwxrwxrwx 1 root root 40 Nov 2 10:29 /tmp/png.h -> /opt/compile-3.3.5/include/libpng2/png.h
lrwxrwxrwx 1 root root 44 Nov 2 10:29 /tmp/pngconf.h -> /opt/compile-3.3.5/include/libpng2/pngconf.h


$ ls -l /opt/compile-3.3.5/lib/pkgconfig/libpng*
lrwxrwxrwx 1 root staff 11 Jul 19 16:06 /opt/compile-3.3.5/lib/pkgconfig/libpng.pc -> libpng12.pc
-rw-r--r-- 1 root staff 247 Jul 19 16:06 /opt/compile-3.3.5/lib/pkgconfig/libpng10.pc
-rw-r--r-- 1 root staff 246 Jul 19 16:06 /opt/compile-3.3.5/lib/pkgconfig/libpng12.pc


To summarise, I see two options:

1. Eliminate the devs for all but one libpng - libpng12/libpng2?
2. Keep the devs for all three libpng, but tidy things up so everything points to the same version of libpng - libpng12/libpng2? Note that I should probably create a libpng2.pc, compiling libpng2 did not produce a pc file...

Suggestions?

Quote
Quote
If that were the case, consider using libpng3 instead of libpng2


Well OK, but the idea behind compile-3.3.5 was only to provide devs for items in the base dsl...

Oh, that's sensible...I didn't notice that libpng2 was in DSL base....maybe that's why I hadn't had any issues =o)

Originally I pointed this out because there were different libpng related symlinks in /tmp pointing to 2 different versions by default... but I'm guessing that's because libpng2 was made to the default but did not have the newer config tools, etc. that libpng12 has.  I would vote for libpng12 being the default, but I have no idea if that would cause more problems or not.  I've just had a couple libpng related problems in the past...
Next Page...
original here.