On 2023/09/07 14:32:40 "Alan C. Assis" wrote:
I think GPL code shouldn't be included directly, but I think it is
fair to allow GPL code be downloaded using the building system case
user selected it.
That's pretty close to what ASF policy is, so that's a great start. As
a reminder, in terms of
I'm very confused as to the issue here. This is not GPL code, this is code
that is dual licensed. I think two totally different topics are being
conflated here.
I have code that was part of the dual licensing of the CAN code being
discussed here (outside of NuttX) and the whole point of dual licen
@Brennan Ashton
we have a release scheduled for this month which is now blocked due to
concerns.
@Shane
from my knowledge the GPL code is disabled by default and users MUST
manually enable it
It would be nice to know if we can continue with the release (since the
interface change was reverted) o
Hi,
Is there any way to do custom apps outside the tree without "pooping" in
the apps directory? The docs show 3 ways to do custom apps, but they
all require modifying the apps directory in some way, either by putting
your custom apps in the apps directory, or making a symlink there. I'd
pr
There is an inexistent, ignored entry in apps called external. By creating
a symlink called external you should end up with no, as you called "poop".
I assume that you mean no extra files or modifications in NuttX
repositories.
On Tue, 12 Sep 2023, 19:58 Mike Moretti, wrote:
> Hi,
>
> Is there a
Thanks!
However, this "external" symlink still requires a person to do a manual
symlink step after cloning our repo (that uses nuttx+apps as
submodules). It would be great if that could be avoided.
I'm surprised there is no way to configure multiple apps dirs via
tools/configure.sh, i.e. so
