On Jul 31, 2013, at 5:52 PM, Brad Litterell <[email protected]> wrote:
> Hi,
>
> I tried
>
>> FILES_${PN} =+ "${libdir}/libuci.so"
>
> but under package-split, the .so file is still only listed in the -dev
> package.
>
> Is it possible that the lib*.so files are always forcibly removed from
> FILES_${PN}?
what is name of your recipe ?
>
> I was able to hack the CMakeList.txt file as follows. If I set SOVERSION on
> the shared library the expected libuci.so.1 file appears with the libuci.so
> link which solves the problem. I'm a little concerned I might have problems
> with other packages that I haven't ported yet that depend on UCI, but I will
> see.
>
thats intact correct way to fix it in view of OE's eyes.
>> may be you should file an enhancement bug for it in Yocto bugzilla
>
> I probably should have mentioned this earlier, but I'm using the 1.3 version
> of Yocto that's embedded in TI's Arago SDK. Can I safely pull poky on top of
> that and see if it fixes the problem or might I have conflicts between Arago
> BSP layers and the 1.4 Poky recipes?
Doubt that
>
> Thanks,
> Brad
>
>
>
> On Jul 31, 2013, at 3:58 PM, Khem Raj <[email protected]> wrote:
>
>>
>> On Jul 31, 2013, at 3:39 PM, Brad Litterell <[email protected]> wrote:
>>
>>> └── lib
>>> ├── libuci.a
>>> └── libuci.so
>>>
>>> So, I added this:
>>>
>>> FILES_${PN} +="/usr/lib/*"
>>
>> Try something like
>>
>> FILES_${PN} =+ "${libdir}/libuci.so"
>>
>>
>>>
>>> However that doesn't remove the message. Did I do it right?
>>>
>>
>>
>> usually .so are symlinks which then go into -dev packages via the default
>> package sieve engine
>> but I am thinking if we find out that file is not a symlink but a normal
>> shared object then probably
>> we could stop shoving it into -dev package and instead put it into ${PN}
>>
>> may be you should file an enhancement bug for it in Yocto bugzilla
>>
>
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
