Re: [dpdk-dev] [RFC] avoid libfdt checks adding full paths to pkg-config

2020-09-02 Thread Christian Ehrhardt
On Tue, Sep 1, 2020 at 6:16 PM Luca Boccassi wrote: > > On Tue, 2020-09-01 at 17:58 +0200, Christian Ehrhardt wrote: > > The checks for libfdt try dependency() first which would only work if > > a pkg-config would be present but libfdt has none. > > Then it probes for the lib path itself via cc.fi

Re: [dpdk-dev] [RFC] avoid libfdt checks adding full paths to pkg-config

2020-09-01 Thread Luca Boccassi
On Tue, 2020-09-01 at 17:58 +0200, Christian Ehrhardt wrote: > The checks for libfdt try dependency() first which would only work if > a pkg-config would be present but libfdt has none. > Then it probes for the lib path itself via cc.find_library. > > But later it adds the result of either probe t

Re: [dpdk-dev] [RFC] avoid libfdt checks adding full paths to pkg-config

2020-09-01 Thread Christian Ehrhardt
On Tue, Sep 1, 2020 at 5:58 PM Christian Ehrhardt wrote: > > The checks for libfdt try dependency() first which would only work if > a pkg-config would be present but libfdt has none. > Then it probes for the lib path itself via cc.find_library. > > But later it adds the result of either probe to

[dpdk-dev] [RFC] avoid libfdt checks adding full paths to pkg-config

2020-09-01 Thread Christian Ehrhardt
The checks for libfdt try dependency() first which would only work if a pkg-config would be present but libfdt has none. Then it probes for the lib path itself via cc.find_library. But later it adds the result of either probe to ext_deps which ends up in build and also the resulting pkg-config to