ghaerr commented on issue #18566:
URL: https://github.com/apache/nuttx/issues/18566#issuecomment-4384293526

   Hi @ppisa and @Acfboy,
   
   Congratulations on getting this proposed work accepted on GSoC! I look 
forward to helping you should it be needed.
   
   > Then there will be implemented logic to call Microwindows own Makefiles 
   
   > All these changes should be done and cleaned at the end such way that they 
are acceptable for Nano-X mainline. The subdirectory Makefiles should not be 
touched or some minor changes which are acceptable
   
   Agreed that it's probably a good idea not to have to get pulled into the 
over-complicated mainline Microwindows/Nano-X (recursive) Makefile system. 
Instead, I would recommend a much easier approach I used for building Nano-X 
for [ELKS](https://github.com/ghaerr/elks), which uses a top-level 
Makefile.elks for the Nano-X server and single separate 
demos/nanox/Makefile.elks to build the desired applications. These two 
makefiles are very simple in comparison to the existing make system and could 
be named Makefile.nuttx for your project, and thus easily accepted into the 
mainline repo when you've got things working. These work very simply using:
   ```
   $ make -f Makefile.elks clean
   $ make -f Makefile.elks
   ```
   which build all binaries from scratch, in this case, directly into 
microwindows/src/bin. Of course, the binaries could go elsewhere. I think 
you'll find these files easily renamed and made usable for your own environment 
and compiler.
   
   I also agree with the remainder of @ppisa's suggestions.
   
   Thank you!


-- 
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