Hello Karel, Thank you very much for sharing your configuration with us.
I would like to ask you two questions: 1. I'm also interested to use Nix for the development environment, and I was initially leaning on using the devenv.sh tool instead of doing straight with Nix. My rational was that it will help non-initiated to Nix to learn about it and be more at ease with its concepts and functionalities. So, I'm wondering why did you decide to go with Nix directly? Is your team already using Nix elsewhere and doesn't need to ramp up from the learning curve? And I was thinking of maybe upstreaming that to the NuttX community or at least sharing that it was something we've been using and might prove useful for others. 2. I'm wondering why not use the custom board and custom application folders structure that's provided by the NuttX build system? I'm wondering what do you gain from doing that? I'm asking because I'm starting a NuttX project at my workplace and I decided to simply follow what the documentation was offering, and I'm also not very much expose to Meson, so some benefits might not be directly obvious to me. Thank you again for sharing this, it is very much appreciated. Best regards, Ludovic Vanasse ludovicvana...@gmail.com On Mon, Jul 28, 2025 at 9:02 AM Karel Kočí <cyn...@email.cz> wrote: > Hi all, > > I want to share with the whole community a setup we are using at > Elektroline to > develop firmwares with NuttX. The setup is pretty complex but provides us > with > ability to maintain project's applications under Meson build system, > compile > them for testing on other Unix-like platforms, and perform automated > testing in > CI (not included in the template). The repository with demonstration is in > here: > > https://gitlab.com/Cynerd/nuttx-meson-template/ > > Conceptually the root matches the Meson project structure and everything > that is > NuttX related is in `nuttx` directory. The directory `nuttx/board` matches > the > board support directory just like in NuttX repository. > > One speciality is Kconfig configuration that is generated by > `nuttx/tools/nuttx-config.sh` and thus `nuttx/board/configs/defconfig` > rather > contains only hand written rules. This is a different approach compared to > the > NuttX suggested one where we hand write configuration we want instead of > creating one and minifying it. > > Meson project in the root is included by `nuttx/project-apps/meson-apps`. > That > is NuttX application that configures Meson build to use the same compiler > and > flags as NuttX and includes Meson compiled object files in the NuttX build. > > Feel free to inspire yourself, comment our setup, or share your own. > > With regards, > Karel Kočí >
