Hello
Why should you change the experience and make life difficult for
everyone, just to support a pair of specific configuration?
If you need to build twice, build twice, one project for h7, one project
for m4, then one python or other script to combine the images.
All users matter (eg, not just the little comfort of AMP users) This is
in inviolables.txt
Sebastien
Le 24/08/2023 à 21:28, Nathan Hartman a écrit :
PR # 10328 is bringing support for STM32 MCUs that have two different kinds
of cores on chip: Cortex M7 and Cortex M4. In other words, AMP-style
(Asymmetric Multi Processing) chip. This requires building NuttX twice,
once for each core, with two different configs.
In the GitHub comments, it was mentioned that we should not make cmake
mandatory for certain boards, and then mentioned that with make the problem
is that you have to make distclean between the two builds. Copying the
comments here:
slorquet writes:
It would be good to avoid cmake-specific features.
Is make a supported build system or was it deprecated?
If it's supported no feature should work only with cmake. Thanks.
xiaoxiang781216 writes:
The change should work with make too. But make doesn't support out of
tree build, it's very annoying to develop AMP system like this patch
because you have to `make distclean` and `make` every time.
This makes me wonder whether we should consider making out-of-tree builds
the blessed way to build, with both make and cmake.
I realize that this might disrupt many people's builds -- including myself.
I have been building in-tree from the start, so this will require me to
change my workflows.
However, after the dust settles, this could have several advantages:
1. Not polluting the source tree with build artifacts and temporary files.
2. Simplifying the.gitignore rules throughout.
3. Allowing AMP builds and builds for multiple different boards without
make distclean. To switch between boards, just change to a different build
dir.
I am starting this thread here because this kind of proposal really needs a
discussion on the mailing list.
Thoughts?
Cheers
Nathan
