gstreamer1-gst-plugins-bad checks for one of the last three openjpeg versions and defines, e.g. HAVE_OPENJPEG_2_2. It uses this to choose the correct path, e.g. #include <openjpeg-2.2/openjpeg.h>. This is hard coded, and has to be manually updated upstream.
> On Oct 6, 2017, at 4:50 PM, Ken Cunningham <[email protected]> > wrote: > > This port, and perhaps many of the the ones that use openjpeg.h, fall back to > look for ${prefix}/include/openjpeg.h . Should openjpeg symlink into that? > > Ken > > > > > > > On 2017-10-06, at 2:16 PM, Marius Schamschula wrote: > >> I was think about that last night, when I patched gstreamer1-gst-plugins-bad >> for this very reason. >> >> A note in the openjpeg Portfile would be helpful. >> >>> On Oct 6, 2017, at 4:06 PM, Ken Cunningham <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> sure. >>> >>> we should probably just search the macports database for everything that >>> requires port:openjpeg and flag them all. Almost all of them are probably >>> broken again - last openjpeg update just finished and we probably aren't >>> done cleaning up from that update ... >>> >>> >>> K >>> >>> . >>> On 2017-10-06, at 1:04 PM, db wrote: >>> >>>> On 6 Oct 2017, at 21:52, Ken Cunningham <[email protected] >>>> <mailto:[email protected]>> wrote: >>>>> Every time openjpeg does a decimal point update, it changes the headers >>>>> and everything breaks. What a PITA. -- Ken >>>> >>>> Thanks. I pinned ffmpeg 3.3.3 in my local repo. Should I file a ticket for >>>> 3.3.4? >>> >> >> Marius >> -- >> Marius Schamschula >> >> >> >> > Marius -- Marius Schamschula
