Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.
Package: debian-policy
Severity: wishlist
With dpkg 1.15.7 just uploaded to sid, there's now a dpkg-buildflags
command that should be used to initialize CFLAGS, LDFLAGS, CPPFLAGS,
FFLAGS, CXXFLAGS. It offers some flexibility for the local admin and for
the user to override/extend the default flags used during a package
compilation.
dpkg-buildpackage continues to export them to not break packages but it
exports the value returned by dpkg-buildflags.
The desired outcome is that all package grab the values directly from
dpkg-buildflags and that we can stop exporting the variables from
dpkg-buildpackage. That way calling debian/rules directly and via
dpkg-buildpackage should give the same result.
Please modify the policy to recommend the usage of dpkg-buildflags (I would
suggest to push that policy change just at the start of squeeze+1).
CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
Note: by using this tool you automatically implement the "noopt" feature
of DEB_BUILD_OPTIONS.
Cheers,
--
Raphaël Hertzog
Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/
My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/
Reply to: