On Mon, Feb 9, 2009 at 4:31 PM, Robin Cornelius <robin.cornel...@gmail.com> wrote: > On Mon, Feb 9, 2009 at 12:58 PM, Cyril Brulebois <k...@debian.org> wrote: >> Mathieu Malaterre <mathieu.malate...@gmail.com> (09/02/2009): >>> current debian package is not compatible with default installation >>> making it difficult to use. >> >> Hmm? From a codesearch.google.com search, it looks like there are a >> bunch of people just using "#include <openjpeg.h>". Why not doing that? > > I've actually seen openjpeg.h in 3 locations in the wild :- > > /usr/include/openjpeg.h > /usr/include/openjpeg/openjpeg.h > /usr/include/libopenjpeg/openjpeg.h > > Pretty much any project i use openjpeg in i now do the #include > <openjpeg.h> with the autotools/cmake etc rules for adding the correct > include search path to gcc. > > I'm on the fence w.r.t changing the location, as if we fix it for one > app, i suspect it will break others who are using it.
Hi Robin, There has been some work going on in openjpeg. They removed support for the old autotools based makefile (at least no more official support). They switch to cmake based system, and now openjpeg 1.x and openjpeg 2.x can be parallel uinstallable using the following convention: /usr/include/openjpeg-1.4/openjpeg.h /usr/include/openjpeg-2.0/openjpeg.h I believe this would be a better long term solution, if debian could switch to that convention. We could also install a symlink... -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
