digiexchris opened a new issue, #15770:
URL: https://github.com/apache/nuttx/issues/15770

   ### Is your feature request related to a problem? Please describe.
   
   I have a cmake project that is using nuttx as a library (make export). It 
would be more convenient for me if I could do out of tree building like the 
wiki suggests. 
https://nuttx.apache.org/docs/latest/quickstart/compiling_cmake.html#out-of-tree-building
 . 
   
   This works fine with the board stated in the example, but as there are 
CMakeLists.txt files missing from the rp2040 and rp2040/<boardname> 
directories, CMake cannot generate a configuration for any RP2040 boards.
   
   I use nuttx-base as a submodule in order to ensure I keep it clean and are 
able to sync with main quickly so an out of tree build is ideal.
   
   ### Describe the solution you'd like
   
   With the RP2040 boards becoming popular, and CMake use increasing, please 
consider providing cmake out-of-tree support for the RP2040 (or at least the 
basic rp2040/raspberrypi-pico) to enable the CMake out of tree example to work:
   
   cmake -B build -DBOARD_CONFIG=raspberrypi-pico:usbnsh -GNinja
   
   ### Describe alternatives you've considered
   
   For a reason I don't quite understand, the exported tarball contains target 
and toolchain cmake files that when I reference them directly in my 
cmakelists.txt files, I can compile for an RP2040 successfully. This suggests 
to me that there may already be some measure of CMake generation for those 
boards in place already, and maybe just need to create matching CMakeLists.txt 
files from that. This is currently my workaround, but exporting a new export 
every time I change config options is tiresome during the initial phase where 
I'm working through config options during the early phases of a project. I'd 
prefer if I can just build against a normal nuttx dir out of tree like is 
possible with the stm32f4-disco.
   
   ### Verification
   
   - [x] I have verified before submitting the report.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to