Thanks for pointing that part of the documentation that I went through without understanding correctly that it would be the case of my issue. This paragraph is doing the jog of explaining THAT library clearly.
But my issue as a user when I read all that was the lack of a "build system" architecture description that would propose the different use case:
- link to libs and rebuild all each time => adviced for most users
- request the user to create a lib that link to libs as "private", link also to the xxx_header and pico_standard_link libs but as public and link your exe to your lib => advanced used reserved to people that compile a lot of different exe and knows what they do with compilation flags.
And the CMakeLists proposed above as an example would be very handy to have.
But my issue as a user when I read all that was the lack of a "build system" architecture description that would propose the different use case:
- link to libs and rebuild all each time => adviced for most users
- request the user to create a lib that link to libs as "private", link also to the xxx_header and pico_standard_link libs but as public and link your exe to your lib => advanced used reserved to people that compile a lot of different exe and knows what they do with compilation flags.
And the CMakeLists proposed above as an example would be very handy to have.
Statistics: Posted by wixiw — Sat Feb 15, 2025 11:17 am