[oe] [PATCH 01/12] libnl: rename libnl2 to libnl as used in openembedded-core

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23-03-11 12:24, Martin Jansa wrote:
> On Wed, Mar 23, 2011 at 11:47:55AM +0100, Stefan Schmidt wrote:
>> Hello.
>>
>> On Fri, 2011-03-18 at 15:00, Martin Jansa wrote:
>>> * libnl1/libnl2 still conflicts even when using separate includedir so
>>>   it will be easier for distro maintainers to use only libnl1 or libnl2
>>>   by PREFERRED_VERSION
>>
>> For distros that want to support network-manager that still means that
>> both versions are being build and may clash as we have seen before.
> 
> How do you build 2 versions of same package? Whole point of this patch
> series is to force distromaintainers to use only libnl_2.0.0 or
> libnl_1.1.0 based on PREFERRED_VERSION_libnl and this way keep them away
> from shooting own foot by accident.

I don't think that's an acceptable solution just yet since angstrom
needs both iw and nm. I think the best way forward is:

1) configure libnl1 to only build a .a
2) rename that .a to libnl-old.a before installing it
3) patch nm to use -l:libnl-old.a

or

1) configure libnl1 to only build a .a
2) move that .a to ${libdir}/libnl1/
3) patch nm to use -L${STAGING_LIBDIR}/libnl1 -l:libnl.a

A lot like
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=71e69ad8b551aa06f63160232d1bd87b8d801a1d
but a bit cleaner.

>> Just a remark. Personally I would like to go this route and maybe get
>> rid of libnl1 at all.
> 
> Yes this is step in direction to get rid of libnl1 :). I'm using
> libnl_2.0.0 from oe-core in meta-shr, so this change is making diff
> between recipes in oe.dev and meta-shr smaller.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNidyDMkyGM64RGpERAtrBAJ9j+q1b4dFMXW7C0T9g55y22GO/PACfeH1O
3NU5PzIAzmtbZy5rdk7ojhs=
=Vgfx
-----END PGP SIGNATURE-----