If your host platform (the one you're compiling on) can use ebuild it can also use pkgconfig, regardless of which platform is being targeted. Makes sense?
Steps to Reproduce:
1, Emerge openjpeg-1.5.2 targeting x86_64-w64-mingw32
pc file is missing and the library will not get found by dependent builds
A pc file is generated in lib/pkgconfig of the crossdev environment.
Created attachment 396218 [details, diff]
Comments-out if(UNIX) in CMakeLists.txt
This patch is applied by the modified ebuild.
Created attachment 396220 [details, diff]
Changes done to the ebuild itself
CC to apparent ebuild maintainer
- The generated pc file for 1.5.2 still lacks information for static linking
- Currently both versions do not generate the pc file for non-UNIX and both should
So my patch is incomplete - it's straight out of my local overlay and the version 1 DLL worked for me.
Could you stop CC'ing random people, please?
Are they sooo random?
I added people whose names can be found frequently in <dir-of-ebuild>/Changelog in conjunction with major changes. Is it a crime?
You added the same person back to the CC list after removing on another case. Yet another issue was just fixed by the very person I CC'ed...
While we're at it: Could you please CC this case to the appropriate maintainer, please?
The bug has been referenced in the following commit(s):
Author: Andreas Sturmlechner <email@example.com>
AuthorDate: 2018-11-03 21:07:11 +0000
Commit: Andreas Sturmlechner <firstname.lastname@example.org>
CommitDate: 2018-11-03 21:30:52 +0000
media-libs/openjpeg: Always install pkgconfig
Signed-off-by: Andreas Sturmlechner <email@example.com>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
media-libs/openjpeg/openjpeg-2.3.0-r1.ebuild | 1 +
1 file changed, 1 insertion(+)