NuttX supports two build system, when a new feature is added, three cases
can happen:
1. Modify Makefile only
2. Modify CMakelist.txt only
3. Modify both Makefile and CMakelist.txt
Since different people use different workflows, tools and have different
priorities. What I suggest it
> Yes, but this project has rules that were set by Greg.
People have limited resources and the NuttX community is not numerous.
The question is what is more valuable for the project - adding
functionality supported
only by cmake, hoping someone will add support for make later, or not
adding any
Hi,
Le 25/08/2023 à 11:48, raiden00pl a écrit :
Forcing people using cmake to support make is the worst thing that can
happen.
Open source is voluntary, any contribution is voluntary, any form of
forcing
others to do anything is unacceptable.
Modifying both systems will be good practice (and an
Hi,
I think that we should prioritize the compatibility and standardization
otherwise the NuttX developer experience may varry (depend on “luck”) for some
platforms
Best regards
Alin
From: raiden00pl
Sent: den 25 augusti 2023 11:49
To: dev@nuttx.apache.org
Subject: Re: [DISCUSS] Out-of-tree
I think this is reinventing the wheel. This seems to not be a trivial
change,
and the ready solution in the form of cmake is already there. If an
individual
or a company wants to devote their time to it, I don't see a problem, but
this
must be backward compatible.
The main voice against cmake was
On Fri, Aug 25, 2023 at 9:38 AM Sebastien Lorquet wrote:
> 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.
Some thoughts on this part :-)
Yes, I agree here, and also proposed that with a several examples.
Others selected parts of inviolables.txt :
All support must apply equally to all supported platforms. At present
this includes Linux, Windows MSYS, Windows Cygwin, Windows Ubuntu,
Windows native, macOS, Solaris, and FreeBSD. No tool/environment
solutions will be considered that limit the
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,
Out-of-tree build is the default for me in various projects. I like to
have git submodules / dependencies untouched.
FreeBSD uses (BSD) make and allows out of tree builds and it is
possible to specify WRKDIRPREFIX for instance in tmpfs located in RAM.
Kernel build also allows passing another
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
10 matches
Mail list logo
