I should look more through before starting to say stuff.
So most of the stuff I mentioned is moot because it was
moved to a different place that I was not aware of.
So Matt as Xiang mentioned the ARCHCXXFLAGS line should be
enough. Importend is the define of __NuttX__ because it enables
the neces
Hi,
i did a curiosity check on this.
No Make.defs for STM32 boards on master from some what yesterday evening
(my localtime) has any include
definitions for c++.
So to help Matt. the following is from my current config add this to
your Make.defs in your /nuttx/nuttx folder:
ARCHINCLUDESXX += ${s
Do you have this in your boards/Make.defs:
ARCHCXXFLAGS += -D__NuttX__ -nostdinc++
Since there are many complex setting to make C++ library work on NuttX, but
this setting spread in different Make.defs, I plan to enhance the experience in
the next couple weeks(actually, all is done in our interna
Hi devs! I'm getting started on NuttX and love the project. Looking to
port my cpp project to NuttX.
I'm having trouble compiling the CPP version of the hello world using the
existing documentation. I'm able to build nuttx just fine and flash my
device using the C version of Hello World.
The e
You can try
https://github.com/apache/incubator-nuttx/tree/master/boards/arm/cxd56xx and
compare the difference with yours.
> -Original Message-
> From: Nathan Hartman
> Sent: Wednesday, August 12, 2020 5:34 AM
> To: dev@nuttx.apache.org
> Subject: Re: Board-specific drivers in NuttX 9.
On Tue, Aug 11, 2020 at 1:14 PM Fotis Panagiotopoulos
wrote:
The structure proposed by Xiang Xiao is not working for me.
>
> By looking in the Makefiles, I did understand that the structure has
> changed a bit.
> Now my structure is:
>
> ├── CustomBoard
> │ ├── defconfig
> │ ├── include
> │
Hi Everyone,
I want to let you know that our event Speakers Line-up with
information of each Presentation is done.
Please access this link to see it:
https://nuttx.events/
BR,
Alan
The structure has not changed, Xiang patch made it possible to omit
the "drivers" folder when it's not needed, in that case a dummy folder
is linked.
What's not working? The folder isn't linked?
I have a structure similar to what I showed before, that should work
for you too.
Check your CONFIG_ARC
The structure proposed by Xiang Xiao is not working for me.
By looking in the Makefiles, I did understand that the structure has
changed a bit.
Now my structure is:
├── CustomBoard
│ ├── defconfig
│ ├── include
│ ├── Kconfig
│ ├── Make.defs
│ ├── scripts
│ └── src
└── drivers
├──
> In NuttX 9.1.0, how can I add my own board-specific drivers?
You do that by providing a driver folder in your board.
nuttx/drivers/platform always points to nuttx/drivers/dummy because
you don't have a driver folder.
Note that "common" and "drivers" were added at about the same time and
the or
"drivers" folder still support, but it's optional now to avoid the empty folder
spread under "boards" directory.
Here is the patch for your reference:
commit 8b20b97d26e78c47d4c083a4c99490fb87c588d7
Author: Xiang Xiao
Date: Sat May 23 02:22:49 2020 +0800
build: Remove the dummy drivers fol
Hello,
I am working on a custom board that I have defined out of tree with
CONFIG_ARCH_BOARD_CUSTOM.
I started development with NuttX v9.0.0, and as I saw there was a
requirement for a directory named "drivers" inside my custom board, but I
left this dir empty with a dummy Kconfig file.
Later on
12 matches
Mail list logo
