Re: [cdt-dev] Managed Core Build

[Liviu Ionescu <ilg@xxxxxxxxxx>]

On 29 March 2018 at 16:23:51, William Riley (william.riley@xxxxxxxxxxx) wrote:

> stick to supporting 1 toolchain per ‘configuration’. With
> multiple configurations per project automatic configuration
> selection based on toolchain could still be added, though I think
> it would need some form of mapping UI as users could have more than
> 1 applicable configuration.

for my workflow, one toolchain per configuration proved enough, as
long as each configuration can have a different toolchain. this is
particularly useful for running multiplatform/multitoolchain tests.

I'm currently migrating my projects to a separate build system for my
projects (xmake + xpacks); it already suports multiple targets and
multiple toolchains, even multiple versions of the same toolchain.

for the moment, I planned a procedure to export configurations to
Eclipse .cprojects (I did this for mbedOS, so I can do it again), but
for a future version I planned to make Eclipse directly use the JSONs
specific to my build system.

it would be interresting to see how this maps on the new managed core build.


regards,

Liviu