I see.
Now, I can tell that you can add manually curl-staticdev to the target. Or
it also gets deployed with the SDKIMAGE_FEATURES. But not for libgcc,
because libgcc-staticdev package does not exist, and that's why
SDKIMAGE_FEATURES couldn't deploy it. I know this now.
The way meta-mingw manage this is adding them, through files
meta-mingw/recipes-devtools/gcc/libgcc_%.bbappend, like this:
FILES_${PN}-dev_append_mingw32 = " ${base_libdir}/libgcc*.a"
However, it makes no sense to me to add static libraries to a dynamic
package. Wouldn't better just to make the package!?
This is my questions:
1. Is this recipe-append intended to be used by nativesdk-libgcc-dev or
libgcc-dev?
2. What would be a use case of adding a nativesdk-libgcc/nativesdk-libgcc-dev
to the host? Is this handle automatically anytime you append to target?
Thank you.
El mar., 16 jun. 2020 a las 17:44, Edgar Chaves (<edgarchv...@gmail.com>)
escribió:
> I see.
>
> Now, I can tell that you can add manually curl-staticdev to the target. Or
> it also gets deployed with the SDKIMAGE_FEATURES. But not for libgcc,
> because libgcc-staticdev package does not exist, and that's why
> SDKIMAGE_FEATURES couldn't deploy it. I know this now.
>
> The way meta-mingw manage this is adding them, through files
> meta-mingw/recipes-devtools/gcc/libgcc_%.bbappend, like this:
>
> FILES_${PN}-dev_append_mingw32 = " ${base_libdir}/libgcc*.a"
>
> However, it makes no sense to me to add static libraries to a dynamic
> package. Wouldn't better just to make the package!?
>
> This are my questions:
> 1. Is this recipe-append intended to be used by nativesdk-libgcc-dev or
> libgcc-dev?
> 2. What would be a use case of adding a
> nativesdk-libgcc/nativesdk-libgcc-dev to the host? Is this handle
> automatically anytime you append to target?
>
> Thank you.
>
> El mar., 16 jun. 2020 a las 13:59, Joshua Watt (<jpewhac...@gmail.com>)
> escribió:
>
>> Please "Reply-All" to keep the discussion on the mailing list
>> On 6/16/20 1:05 PM, Edgar Chaves wrote:
>>
>> Hi, do you have thoughts about this?
>>
>> My concern is that *-staticdev part of nativesdk-* providers is not
>> deployed correctly.
>>
>>
>> nativesdk-*-staticdev packages shouldn't be included in the SDK.
>> nativesdk- recipes are intended to run on the host where the SDK is
>> extracted, and that SDK will be used to compile software for some target.
>> The SDK isn't intended to be able to compile more software for running on
>> the SDK host itself, so none of the development files for nativesdk recipes
>> are included in SDK iteself.
>>
>> Practically speaking, this means that the SDK will not include a package
>> like nativesdk-curl-staticdev (which is used to build SDK host software),
>> but it could include curl-staticdev (which is used by the SDK to build
>> target software).
>>
>>
>>
>> El mié., 3 jun. 2020 a las 19:37, Edgar Chaves (<edgarchv...@gmail.com>)
>> escribió:
>>
>>> OK. Let me correct it.
>>>
>>> I believe the layer and recipes are missing some packaging, therefore
>>> I'm missing *some* .a libraries in the SDK.
>>>
>>> Something like this: FILES_${PN} += " ${baselib_dir}"
>>>
>>> El mar., 2 jun. 2020 a las 7:37, Joshua Watt (<jpewhac...@gmail.com>)
>>> escribió:
>>>
>>>> CC'in the mailing list.
>>>> On 6/1/20 10:39 PM, Edgar Chaves wrote:
>>>>
>>>> Hi
>>>>
>>>> I want to ask about meta-mingw static libraries for Windows. The thing
>>>> is that I don't get ".lib" in the SDK. Do you have any information about
>>>> that?
>>>>
>>>> meta-mingw is primarily intended to build and SDK that allows you to
>>>> cross compile for a Linux target from a Windows host, so including the
>>>> static libraries for the Windows portions doesn't really make sense. I
>>>> think there has been a little discussions about making and SDK that cross
>>>> compiles for Windows, but I don't recall where that went.
>>>>
>>>> Perhaps you can clarify what your use case is?
>>>>
>>>>
>>>>
>>>> Thank you, I'd appreciate your answer.
>>>>
>>>> —Edgar
>>>>
>>>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49655): https://lists.yoctoproject.org/g/yocto/message/49655
Mute This Topic: https://lists.yoctoproject.org/mt/74924298/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
