On Sun, Apr 14, 2013 at 2:00 AM, Ken wrote: > Announcing the latest in a long and boring series of documents > listing what I'm currently building on my desktops, and in what order. > This one is at >http://www.linuxfromscratch.org/~ken/desktop-builds/desktop-build-april-2013.txt > and is for LFS-7.3. Hopefully I'll get started on LFS-svn with > gcc-4.8 real soon now.
Actually I thought the list was quite interesting and pretty impressive. > As always, I'm willing to answer questions about those packages I do build. Would be very curious as to approximately how long it takes to complete the build of everything from start to finish on your system. > Replaced jpegsrc with libjpeg-turbo. For x86_64 this can use yasm >(x86_32 needs nasm), so I've moved that forward in my build. Am also curious if you notice any differences between jpegsrc and libjpeg-turbo and if there are any programs that may build with one that won't build with the other. >Dropped openjpeg - I very much doubt that anything I ever see > uses it. From memory, the current version requires cmake - I wasn't > willing to build that. I might change my mind about cmake - I still > loathe the way it reinvents the wheel, but I've now found some > documentation of the many -DCMAKE_FUBAR variables) at I use openjpeg with mupdf (an extremely fast, lightweight pdf viewer). Seems like a nuisance openjpeg dropped support to build using standard gnu autotools and switched only to using cmake. Other projects (like sdl) support multiple build methods. Don't know if it's good or bad news, but I've seen some bug listings that the latest version of mupdf doesn't work with the latest version of openjpeg anyway. I'm thinking of continuing to use an earlier version of openjpeg that doesn't require cmake for as long as I can. Would be nice if mupdf could use a different jpeg library besides openjpeg. Also, since they include the source for openjpeg with mupdf, there's always the possibility of forking openjpeg and creating a version specifically for mupdf. Was hoping to run across some more news on this topic, but haven't heard anything useful yet. When I have time to rebuild xine on my machine, I'm very curious about the issue you ran into. Hope to at least take a look at it. At least you found a work-around even if it doesn't make sense. Sincerely, Laura
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
