[oe] [RFC][PATCH] binconfig.bbclass: search configs in PKGD instead of S

[Stanislav Brabec]

Andreas Oberritter wrote:
> On 01/27/2011 11:31 PM, Stanislav Brabec wrote:
> > It seems that searching for binconfig in S makes more problems than it
> > brings benefits. It breaks for example ncurses - it populates
> > ncurses-config instead of ncurses5-config and ncursesw5-config).
> 
> Indeed. Installing *-config files which don't get installed by the
> recipe is prone to cause subtle errors. I modified pkgconfig.bbclass in
> a similar way in commit c2c8fe4c5629add94bd0b922f5b3446624a9f4d8.

Yes, it can cause installation of .pc that are not intended to be
installed. It also saves the grep -v -- '-uninstalled.pc$'.

> "find recipes -name "*-config" -type f" shows candidates which may cause
> breakage with this patch applied, in case they need to be installed but
> only get copied to the source directory.

Well, it is possible, especially for packages that don't use "make
install" in any form. But the correct solution for that problem would be
different: Install these -config files in do_install and let binconfig
to mangle and move them automatically. If one depends on the old form of
binconfig, -config files are missing in the target native -devel
packages. (Most users will not see any problems until they try to
compile on the target native system.)

> > Searching in the installed root seems to be more logical.
> > 
> > Most packages don't need to be ported to this change, as they install
> > config file with the same name as it exists in sources. But probably
> > several will need porting.
> 
> Why is this function needed at all? Isn't it possible to do the mangling
> before or after do_install like in pkgconfig.bbclass?

binconfig files are a bit special:
- They have to be in the cross environment PATH. The target sysroot is
not (and cannot) be in the cross environment PATH. They have to be
mangled and moved to another location.

- They have to be different in the target package and in the staging
package. I can imagine a different solution, but the current one works
well for most packages.

In case of .pc files, this logic above is embedded into pkg-config
itself, so one does not need additional magic.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus