> I keep two config files, one for debug, one for release. Very similar > except for the kinds of debugging options you mentioned.
This is exactly what I want to avoid. I will have to support 3 different boards, with maybe 3 different build types. Thus 9 configurations. This will be very difficult to maintain. If I want to make a change unrelated to the build or the boards (say for example something in the network system), I will have to manually apply the change to all these configurations! And the worst is that there will be no guarantee that all configurations are in sync (apart from manually checking the diffs between them). Στις Παρ, 24 Ιουλ 2020 στις 9:47 μ.μ., ο/η Nathan Hartman < hartman.nat...@gmail.com> έγραψε: > On Fri, Jul 24, 2020 at 12:26 PM Fotis Panagiotopoulos < > f.j.pa...@gmail.com> > wrote: > > > Hello, > > > > So, I have set up my workspace now, and I have NuttX running properly on > my > > custom board. > > I have another question though, regarding how to set things up for > > development. > > > > Usually I have at least 2 build configurations: one for debugging, one > for > > releases etc. > > > > Debug builds have assertions enabled, optimizations disabled, various > > checks enabled etc etc, while release builds the do the opposite. > > > > How is this best to be handled by NuttX? Should I have various > > configuration files to load each time, or is there a better way? > > > I keep two config files, one for debug, one for release. Very similar > except for the kinds of debugging options you mentioned. > > Nathan >
