On Wed, Nov 23, 2016 at 04:11:10PM +0100, Dmitrij D. Czarkoff wrote: > Antoine Jacoutot wrote: > > >>> --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. > > With waf all these settings have some default value, so that build > system may or may not pick a dependency. Also, there is no guarantee > that defaults won't change between releases. So having explicit
Sure, that's what MAINTAINER is for :-) And that won't prevent new switches in a new release anyway. > --(en|dis)able-* flags (together with "make port-lib-depends-check") > help detecting dependency issues during updates. Alright, I was just asking since that's the only port where I ever saw something like this. I don't mind it, I just found it weird and was just wondering. -- Antoine
