On Wed, Jul 27, 2011 at 12:55:04AM +0200, Raphael Hertzog wrote: > On Tue, 26 Jul 2011, Raphael Hertzog wrote: > > We evaluated how dpkg-buildflags can be used for this. For most > > autoconf/automake-based build systems there are 2 ways to inject flags: > > 1/ On the ./configure command line: > > ./configure --with-foo CFLAGS="..." LDFLAGS="..." ... > > 2/ In the environment
> > The first form seem to be preferred but both approaches work and should be > > properly supported. However dpkg-buildflags does not easily support the > > former approach. This is something that should be fixed. > Just for reference, in the discussion I mentionned that dpkg would start > providing a makefile snippet that helps retrieving the correct value of > all the build flags, you can see it here: > http://anonscm.debian.org/gitweb/?p=dpkg/dpkg.git;a=commitdiff;h=b858e07bddec28c5b86c39d425a02f08d9bd205a > Maintainers who thus want to follow the approach where build flags are > exported in the environment will thus be able to do: > --- > DPKG_EXPORT_BUILDFLAGS = yes > include /usr/share/dpkg/default.mk > --- For the record, I'll repeat here the view expressed at the meeting (which I recall being shared by Bdale and Ian): I don't think dpkg should be exposing such an interface at all. We don't want to encourage the use of makefile includes for such things. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
