Re: pkg-config and opencv4
I just opened a PR with the fix: https://github.com/macports/macports-ports/pull/9972 > On Feb 9, 2021, at 9:03 AM, Marius Schamschula wrote: > > Exactly my reading. However, there are many packages that depend on > opencv/opencv4 that prefer to use pkg-config rather than cmake. In my case > gmic in its multiple forms. > >> On Feb 9, 2021, at 8:44 AM, Joël Brogniart >> wrote: >> >> Even if posts in the issus show workarounds, it also looks like opencv >> developers consider the use of pkg-config .pc files obsolete so I will do >> without. >> >>> Le 9 févr. 2021 à 14:43, Marius Schamschula a écrit >>> : >>> >>> It looks like this is an open issue: >>> >>> https://github.com/opencv/opencv/issues/13154 >>> >>> It looks like one can patch opencv4 to fix this issue. >>> >>> PS: I meant .pc not .po files. >>> On Feb 9, 2021, at 7:40 AM, Marius Schamschula wrote: pkg-config only works if the package generates .po files. cairo does, opencv does, but opencv4 does not. > On Feb 9, 2021, at 6:44 AM, Joël Brogniart > wrote: > > > One should be able to obtain informations with pkg-config. ie. wiith > cairo installed it works fine > pkg-config --cflags cairo > pkg-config --libs cairo > But not with opencv4. > > Joël > >> Le 9 févr. 2021 à 12:10, Marius Schamschula a >> écrit : >> >> I haven’t had time to look into that. I’m not the maintain of opencv4. >> For the moment I downgraded opencv to version 3.4.13. >> >>> On Feb 9, 2021, at 2:28 AM, Joël Brogniart >>> wrote: >>> >>> I'm trying to adapt a portfile for a Linux application to depend on >>> opencv4 instead of opencv. The building of the application use >>> pkg-config to find directory, library et compiler settings for >>> different tools (opencv, cairo…). This works correctly except for >>> opencv. >>> >>> On Macports, the opencv4 port doesn't populate pkg-config data with its >>> own information. Is there an explanation for the missing data? >> >> Marius >> -- >> Marius Schamschula >>> >> > Marius -- Marius Schamschula
Re: 99 bottles of beer on the wall...
Down to only 2 pages and < 50 open PRs... it's starting to look like my Inbox Zero! Also, we're fast approaching PR #10,000! -- Jason Liu On Mon, Jan 25, 2021 at 3:39 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > the PR list is < 100 for the first time in a very very long time…. > > Keep ‘er going! > > K
Re: pkg-config and opencv4
Exactly my reading. However, there are many packages that depend on opencv/opencv4 that prefer to use pkg-config rather than cmake. In my case gmic in its multiple forms. > On Feb 9, 2021, at 8:44 AM, Joël Brogniart > wrote: > > Even if posts in the issus show workarounds, it also looks like opencv > developers consider the use of pkg-config .pc files obsolete so I will do > without. > >> Le 9 févr. 2021 à 14:43, Marius Schamschula a écrit : >> >> It looks like this is an open issue: >> >> https://github.com/opencv/opencv/issues/13154 >> >> It looks like one can patch opencv4 to fix this issue. >> >> PS: I meant .pc not .po files. >> >>> On Feb 9, 2021, at 7:40 AM, Marius Schamschula >>> wrote: >>> >>> pkg-config only works if the package generates .po files. cairo does, >>> opencv does, but opencv4 does not. >>> On Feb 9, 2021, at 6:44 AM, Joël Brogniart wrote: One should be able to obtain informations with pkg-config. ie. wiith cairo installed it works fine pkg-config --cflags cairo pkg-config --libs cairo But not with opencv4. Joël > Le 9 févr. 2021 à 12:10, Marius Schamschula a > écrit : > > I haven’t had time to look into that. I’m not the maintain of opencv4. > For the moment I downgraded opencv to version 3.4.13. > >> On Feb 9, 2021, at 2:28 AM, Joël Brogniart >> wrote: >> >> I'm trying to adapt a portfile for a Linux application to depend on >> opencv4 instead of opencv. The building of the application use >> pkg-config to find directory, library et compiler settings for different >> tools (opencv, cairo…). This works correctly except for opencv. >> >> On Macports, the opencv4 port doesn't populate pkg-config data with its >> own information. Is there an explanation for the missing data? > > Marius > -- > Marius Schamschula >>> >> >
Re: pkg-config and opencv4
Even if posts in the issus show workarounds, it also looks like opencv developers consider the use of pkg-config .pc files obsolete so I will do without. > Le 9 févr. 2021 à 14:43, Marius Schamschula a écrit : > > It looks like this is an open issue: > > https://github.com/opencv/opencv/issues/13154 > > It looks like one can patch opencv4 to fix this issue. > > PS: I meant .pc not .po files. > >> On Feb 9, 2021, at 7:40 AM, Marius Schamschula wrote: >> >> pkg-config only works if the package generates .po files. cairo does, opencv >> does, but opencv4 does not. >> >>> On Feb 9, 2021, at 6:44 AM, Joël Brogniart >>> wrote: >>> >>> >>> One should be able to obtain informations with pkg-config. ie. wiith cairo >>> installed it works fine >>> pkg-config --cflags cairo >>> pkg-config --libs cairo >>> But not with opencv4. >>> >>> Joël >>> Le 9 févr. 2021 à 12:10, Marius Schamschula a écrit : I haven’t had time to look into that. I’m not the maintain of opencv4. For the moment I downgraded opencv to version 3.4.13. > On Feb 9, 2021, at 2:28 AM, Joël Brogniart > wrote: > > I'm trying to adapt a portfile for a Linux application to depend on > opencv4 instead of opencv. The building of the application use pkg-config > to find directory, library et compiler settings for different tools > (opencv, cairo…). This works correctly except for opencv. > > On Macports, the opencv4 port doesn't populate pkg-config data with its > own information. Is there an explanation for the missing data? Marius -- Marius Schamschula >> >
Re: pkg-config and opencv4
One should be able to obtain informations with pkg-config. ie. wiith cairo installed it works fine pkg-config --cflags cairo pkg-config --libs cairo But not with opencv4. Joël > Le 9 févr. 2021 à 12:10, Marius Schamschula a écrit : > > I haven’t had time to look into that. I’m not the maintain of opencv4. For > the moment I downgraded opencv to version 3.4.13. > >> On Feb 9, 2021, at 2:28 AM, Joël Brogniart >> wrote: >> >> I'm trying to adapt a portfile for a Linux application to depend on opencv4 >> instead of opencv. The building of the application use pkg-config to find >> directory, library et compiler settings for different tools (opencv, >> cairo…). This works correctly except for opencv. >> >> On Macports, the opencv4 port doesn't populate pkg-config data with its own >> information. Is there an explanation for the missing data? > > Marius > -- > Marius Schamschula
Re: pkg-config and opencv4
A quick look at the Portfile shows that opencv4 uses cmake. It is rare that cmake based builds also gernerate .po files by default, but there may be a switch. It might be worth opening a trac ticket. > On Feb 9, 2021, at 5:37 AM, Joël Brogniart > wrote: > > One should be able to obtain informations with pkg-config. ie. wiith cairo > installed it works fine > pkg-config --cflags cairo > pkg-config --libs cairo > But not with opencv4. > > Joël > >> Le 9 févr. 2021 à 12:10, Marius Schamschula a écrit : >> >> I haven’t had time to look into that. I’m not the maintain of opencv4. For >> the moment I downgraded opencv to version 3.4.13. >> >>> On Feb 9, 2021, at 2:28 AM, Joël Brogniart >>> wrote: >>> >>> I'm trying to adapt a portfile for a Linux application to depend on opencv4 >>> instead of opencv. The building of the application use pkg-config to find >>> directory, library et compiler settings for different tools (opencv, >>> cairo…). This works correctly except for opencv. >>> >>> On Macports, the opencv4 port doesn't populate pkg-config data with its own >>> information. Is there an explanation for the missing data? >> >> Marius >> -- >> Marius Schamschula Marius -- Marius Schamschula
Re: Meson 0.56.2 and Python39 --> dav1d failing
> On Feb 9, 2021, at 12:04 AM, Ken Cunningham > wrote: > > > PS — any feedback on the success of the cross building, or any failures > encountered, would be much appreciated. I believe this is the only setup > that currently allows meson cross building on BigSur that is available for > macOS. Yep, success! meson cross-building to arm64 from BigSur Intel finally works now: % port -v installed dav1d The following ports are currently installed: dav1d @0.8.1_0+universal (active) platform='darwin 20' archs='arm64 x86_64' date='2021-02-09T01:15:26-0800' % file /opt/local/lib/libdav1d.5.dylib /opt/local/lib/libdav1d.5.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64] /opt/local/lib/libdav1d.5.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 /opt/local/lib/libdav1d.5.dylib (for architecture arm64): Mach-O 64-bit dynamically linked shared library arm64 and presumably the other way around as well. So that's something new. dav1d needs a couple of minor tweaks to get it to build universal, but they are minor. K
pkg-config and opencv4
I'm trying to adapt a portfile for a Linux application to depend on opencv4 instead of opencv. The building of the application use pkg-config to find directory, library et compiler settings for different tools (opencv, cairo…). This works correctly except for opencv. On Macports, the opencv4 port doesn't populate pkg-config data with its own information. Is there an explanation for the missing data?
Re: Meson 0.56.2 and Python39 --> dav1d failing
as meson was currently broken on older systems I pushed through a fix for this just now. We can revise it to whatever upstream wants to do when they get around to it, if they want to do anything about it. I took the opportunity to also add a cross file similar to the ones I added previously for i386 and x86_64, and this should allow cross building of meson ports on BigSur. I deeply apologize — I stupidly made a tiny typo by leaving in a testing tweak, and only saw it when I looked at the commit afterwards to make sure it was all well. So I had to fix that quickly. Normally I would have PR’d this, and waited for review but as in one case the systems were broken, and in the other it involved the cross-building I added, I went ahead with it. My apologies if this is felt to break protocol; just trying to do the right thing here. Bes;t Ken PS — any feedback on the success of the cross building, or any failures encountered, would be much appreciated. I believe this is the only setup that currently allows meson cross building on BigSur that is available for macOS.
