Date: Mon, 25 Jul 2022 15:56:12 +0200 From: Andrea Pappacoda <andrea@pappacoda.it> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: Alex Dupre <sysadmin@alexdupre.com>, freebsd-hackers@FreeBSD.org Subject: Re: pkg-config and share/ Message-ID: <ODXKFR.TMQ5KIOXE4A31@pappacoda.it> In-Reply-To: <20220725111046.7sr7yyvsm5f3hyhj@aniel.nours.eu> References: <50B3D276-5E68-4F87-97FB-71D75D3D9602@pappacoda.it> <20220725081535.vuxy74odqt2cxdnw@aniel.nours.eu> <be19c9ab-c762-a0b4-a3d2-8ffbc45dd5ac@alexdupre.com> <20220725090824.qfeypgyugx6f7i6q@aniel.nours.eu> <CNMKFR.31V3MUTROVR7@pappacoda.it> <20220725111046.7sr7yyvsm5f3hyhj@aniel.nours.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Il giorno lun 25 lug 2022 alle 13:10:46 +02:00:00, Baptiste Daroussin <bapt@FreeBSD.org> ha scritto: > how do I lose that? there is something that I am missing here. what is > fundamentally different from share/pkgconfig and libdata/pkgconfig > beside the > name of the directory? I guess the difference is in the meaning of the two locations. If a .pc file is in share/ you can be sure it can be used for cross compilation, as share/ only contains arch-independent stuff. And if it is in libdata/? Maybe, I can't know, it could be either arch-specific or arch-independent. For example, if I'm cross compiling to a riscv target and I find the toml++ library in share/pkgconfig/, I can use the library for the build as it is arch-independent (header-only lib, in this case). If I instead find the .pc file in libdata/pkgconfig/, I can't use it anymore, as it could either be arch-independent (header-only version), or arch-specific (toml++ can also be compiled as a proper shared library). That's how I see things, but I might be missing something. Hope I made this a bit cleaner :) -- OpenPGP key: 66DE F152 8299 0C21 99EF A801 A8A1 28A8 AB1C EE49
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ODXKFR.TMQ5KIOXE4A31>