GNOME Bugzilla – Bug 695628
assigns to VALAFLAGS which is reserved for the user
Last modified: 2013-03-12 19:32:12 UTC
Created attachment 238575 [details] [review] Do not assign to VALAFLAGS Users should be able to do "make VALAFLAGS=--enable-experimental-non-null" without overriding necessary flags like --target-glib=2.24. The variable for use by package maintainers is AM_VALAFLAGS.
Review of attachment 238575 [details] [review]: Looks good. Again, this would all benefit from factoring out the common stuff in the build system into a couple of macros.
(In reply to comment #0) > Users should be able to do "make VALAFLAGS=--enable-experimental-non-null" Oh, also, would you mind briefly documenting this use case in HACKING? e.g. Something along the lines of “folks aims to compile with --enable-experimental-non-null in the future, so please try to reduce the number of warnings when compiling with that flag; do so by setting VALAFLAGS=--enable-experimental-non-null”.
(In reply to comment #2) > Oh, also, would you mind briefly documenting this use case in HACKING? Never mind, I just did it myself. Sorry for the noise.
Created attachment 238694 [details] [review] Always append to AM_VALAFLAGS, don't replace This avoids losing --target-glib=2.24 (from configure.ac) in certain test modules. --- Follow-up for Attachment #238575 [details].
Review of attachment 238694 [details] [review]: Please commit.
Fixed in git for 0.9.2, NEWS also updated.