csanchezdll commented on PR #3802:
URL: https://github.com/apache/nuttx-apps/pull/3802#issuecomment-6763902530

   Yes, this required https://github.com/apache/nuttx/pull/20367 which was 
dropped because it required changes which do not fit well with the current 
situation where libboard.a depends on nuttx-apps, for some boards. Explanation 
on https://github.com/apache/nuttx/pull/20367#discussion_r4154462570 and 
followup discussion.
   
   Configuration checks are done at build time, but they require non-app 
libraries to be there (this is why this depended on 
https://github.com/apache/nuttx/pull/20367). The header built from CONFIG_ 
macros is not an acceptable solution to me: I want to leverage jimtcl autoconf 
system (jimtcl maintaners already take care of deciding which configs they need 
depending on system features). Having to create a map from Nuttx-side CONFIG_ 
settings to jimtcl config settings is basically redoing that, and creates a 
need to maintain that map.
   
   I find being able to run the configure script provided with jimtcl (or any 
other autoconf-based package) is an advantage of Nuttx over other 
embeddded-OSes which do not build system libraries separately. I do not see 
value on a static CONFIG_ based map, at least for my use case.
   
   Cmake: you are right. I usually develop build system changes on make first, 
as I am more fluent there, and port to cmake later. But it is true this PR 
cannot go in without https://github.com/apache/nuttx/pull/20367, so I am 
dropping this as well.


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