On 2024/05/27 10:09, Vitaly Zaitsev via devel wrote:
On 27/05/2024 02:46, Kan-Ru Chen wrote:
It is documented that FIND_PACKAGE_ARGS argument in
FetchContent_Declare should instruct it to find system packages first.
This only works as expected in very rare cases. The library name in
On 27/05/2024 02:22, Byoungchan Lee via devel wrote:
In well-maintained Fedora packages, the use of the FetchContent module is
generally discouraged because dependencies are already available in the Fedora
repositories.
FetchContent never worked on Fedora because the builders have no network
On 27/05/2024 02:46, Kan-Ru Chen wrote:
It is documented that FIND_PACKAGE_ARGS argument in FetchContent_Declare should
instruct it to find system packages first.
This only works as expected in very rare cases. The library name in
FetchContent() must match the name in find_package().
This
On Sun, May 26, 2024 at 8:47 PM Kan-Ru Chen wrote:
>
> On Mon, May 27, 2024, at 9:22 AM, Byoungchan Lee via devel wrote:
> > In well-maintained Fedora packages, the use of the FetchContent module
> > is generally discouraged because dependencies are already available in
> > the Fedora
On Mon, May 27, 2024, at 9:22 AM, Byoungchan Lee via devel wrote:
> In well-maintained Fedora packages, the use of the FetchContent module
> is generally discouraged because dependencies are already available in
> the Fedora repositories.
>
> While it's uncertain if build workers in Fedora have
In well-maintained Fedora packages, the use of the FetchContent module is
generally discouraged because dependencies are already available in the Fedora
repositories.
While it's uncertain if build workers in Fedora have internet access, to
improve security, I believe it is recommended to
