[Buildroot] [Feature Request] Host cmake built with the --system-curl option

[James Hilliard]

On Wed, Apr 6, 2022 at 5:02 PM Emile Cormier <emile.cormier.jr at gmail.com> wrote:
>
> On Wed, Apr 6, 2022 at 7:27 PM James Hilliard <james.hilliard1 at gmail.com> wrote:
>>
>> Why are you executing cmake in a post-build script?
>>
>> You should probably create a proper cmake package in your BR2_EXTERNAL:
>> https://buildroot.org/downloads/manual/manual.html#_infrastructure_for_cmake_based_packages
>> https://buildroot.org/downloads/manual/manual.html#outside-br-custom
>
>
> I should have clarified that the same CMake-based superbuild project is used to compile desktop versions of the same app for development purposes. All the (permissive-licenced) dependencies are statically linked to avoid headaches where the desktop's dynamic libraries are used instead of the ones intended for the app. As I'm sure you know, the edit/run/debug cycle is much faster when it doesn't have to be uploaded and remotely debugged on an embedded device.
>
> Nonetheless, I'll consider your advice and will check if the CMake superbuild of our app can be hooked into a BR2_EXTERNAL cmake package instead of a post-build script. Thank you.
>
>> So create a separate buildroot package for those dependencies that your main
>> package selects.
>>
>> Use the cmake package infrastructure instead of trying to use cmake to download
>> the dependency.
>
>
> Again, the same CMake superbuild is used for desktop builds and I don't want to duplicate all that effort into equivalent buildroot cmake packages. Sorry for not making clearer the dual purpose of our CMake superbuild.

You might still be able to share it for desktop builds for development
by creating
packages and then overriding them using the OVERRIDE_SRCDIR feature:
https://buildroot.org/downloads/manual/manual.html#_using_buildroot_during_development