Strictly my personal opinion: if you don't have those variables unders some sort of control, i.e. they are swimming around somewhere in your build system (that's why you need to work via .VARIABLES) then you are asking for trouble. You may produce a month-long chain of versions with a certain variable at a certain value that you totally didn't want to be at this value. All the work and testing during those months may be rendered useless or at least of strongly degraded value due to this variable being invisible to the configuration process. Talking from an embedded software perspective.
Am So., 11. Apr. 2021 um 20:39 Uhr schrieb Britton Kerin < britton.ke...@gmail.com>: > I've got vars like DEBUG_ENABLE only a big hairy pile of them at this > point, and I want make to rebuild everything when I give a different > set of them (including via command line) with my having > to remember to do clean first. > > I can see how it might be done using .VARIABLES and a cache of some > sort but I wonder if anyone has already done this? > > Britton > >
