[OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Ravi chandra reddy]

Hi Andrea,
               gr8, Thanks for this information. i wasnt' aware someone did
create a libiio in yocto.

anyways, i reached my goal using other means of cross compiling individual
libraries and building libiio finally. it was a pain, but i learnt a lot in
between.

Thanks
RC

On Thu, Apr 6, 2017 at 6:31 PM, Andrea Galbusera <gizero at gmail.com> wrote:

> Hi,
>
> On Thu, Apr 6, 2017 at 10:11 PM, Ravi chandra reddy <vlsireddy at gmail.com>
> wrote:
>
>> Hi,
>>     I am trying to generate LibIIO [open source by Analog Devices],
>> however there is dependancy on Libxml2.
>>
>
> For libiio there is a recipe in meta-openembedded [1]. Are you using that
> one?
>
> [1] http://layers.openembedded.org/layerindex/recipe/57509/
>
>
>> problem with Libxml2, it is dependant on *python*-lib, libdl, libz,
>> libzma, libm
>>
>> for some reason with Yocto built Libxml2.so, i am encountering "undefined
>> references error", which i am unable to solve [inspite of linking possible
>> dependant libraries],
>>
>> if i get could the Libxml2.a, it packages all "REQUIRED ELEMENTS", so i
>> assume, there WONT be any error in linking Libxml2 in Libiio.
>>
>> ======in short=========
>> Libiio ---linking---> Libxml2*.so* [yocto based] ---errors-> undefined
>> referneces to .....
>>
>> ======in short=========
>> Libiio ---linking---> Libxml2.a [yocto based] --> SHOULD solve and
>> install libiio
>>
>> for me to generate Libxml2.a, i need to make/ask yocto build LIbxml2.a
>> for me. i tried putting libxml2-staticdev  in the local.conf file and it
>> gives me build error.
>>
>> all i want is Libxml2.a which is to be used by Libiio.so/Libiio.a to be
>> used by an application [called in user space of AARCH linux]
>>
>>
>> Thanks
>> RC
>>
>> On Thu, Apr 6, 2017 at 3:17 PM, Matthew McClintock <
>> msm-oss at mcclintock.net> wrote:
>>
>>> On Thu, Apr 6, 2017 at 9:20 AM, Ravi chandra reddy <vlsireddy at gmail.com>
>>> wrote:
>>> > Hi,
>>> >      Is there any hidden pointer within these static dev packages. i
>>> > expected the library to be .a format. what can i understand from these
>>> > static dev packages, plz let me know.
>>>
>>> Can you expand on what you're trying to accomplish? Are you trying to
>>> build a static binary? I don't think you actually are trying to
>>> install libxml2.a on the running image are you? Maybe you really want
>>> an SDK with a sysroot populated with static libraries so you can link
>>> against them?
>>>
>>> -M
>>>
>>
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170408/cb889c1b/attachment-0002.html>