On Wed, Nov 23, 2016 at 02:11:27PM +0000, Stuart Henderson wrote: > On 2016/11/23 14:30, Antoine Jacoutot wrote: > > On Wed, Nov 23, 2016 at 02:05:30PM +0100, Dmitrij D. Czarkoff wrote: > > > Antoine Jacoutot <[email protected]> wrote: > > > > > > >> +.if ${FLAVOR:L:Mlite} > > > >> +TOGGLE = disable > > > >> +.else > > > >> +TOGGLE = enable > > > > > > > >Why using a variable for this? > > > >Wouldn't this work? > > > > > > > >.if ${FLAVOR:L:Mlite} > > > >CONFIGURE_ARGS += --disable-foo \ > > > > --disable-bar > > > >... > > > > > > Separate variable is supposed to allow a single list of flags, so that I > > > would > > > not need to sync lists if changes are necessary. > > > > --enable-foo needs to be explicitely set when the dependency is found by > > configure? > > And surely if that's the case for some foo, then --disable wouldn't be > needed for that foo..
--disable-foo is needed because in case a dependency is there at build time, you will pick it up. -- Antoine
