On Wed, May 15, 2019 at 9:33 PM Petr Štetiar wrote:
> Jeffery To [2019-05-15 21:00:28]:
>
> > The buildroot pkg-config (in staging_dir/host/bin) overrides the prefix
> and
> > exec_prefix variables in *.pc files, to supply the correct (buildroot)
> > paths for callers. If other variables are not
Jeffery To [2019-05-15 21:00:28]:
> The buildroot pkg-config (in staging_dir/host/bin) overrides the prefix and
> exec_prefix variables in *.pc files, to supply the correct (buildroot)
> paths for callers. If other variables are not defined relative to prefix
> and exec_prefix, then the returned
On Fri, May 3, 2019 at 5:32 PM Petr Štetiar wrote:
> Jeffery To [2019-05-03 00:47:06]:
>
> > The default zlib.pc file generated by cmake contains absolute paths.
> > This patches the file to use relative paths (relative to ${prefix} and
> > ${exec_prefix}).
>
> I can see that from the diff alrea
Jeffery To [2019-05-03 00:47:06]:
> The default zlib.pc file generated by cmake contains absolute paths.
> This patches the file to use relative paths (relative to ${prefix} and
> ${exec_prefix}).
I can see that from the diff already, but I miss the information, why do you
need this change. Coul
On Thu, May 2, 2019 at 9:47 AM Jeffery To wrote:
>
> The default zlib.pc file generated by cmake contains absolute paths.
> This patches the file to use relative paths (relative to ${prefix} and
> ${exec_prefix}).
git grep with-zlib= | wc -l in the packages repo returns 12. I wonder
if this fixes
The default zlib.pc file generated by cmake contains absolute paths.
This patches the file to use relative paths (relative to ${prefix} and
${exec_prefix}).
Signed-off-by: Jeffery To
---
package/libs/zlib/Makefile | 2 +-
.../patches/004-relative-pkg-config-paths.patch