Re: Building: w or w/o Stripping, w or w/o debugging symbols
Florian Hinzmann <fh@bigfoot.de> wrote:
>On 25-Jan-2001 Colin Watson wrote:
>> Most of the example code I showed was just setting Makefile variables,
>> so it should go outside any targets (normally near the top of
>> debian/rules). Depending on the structure of the upstream Makefile, you
>> might need to arrange for those parameters to be passed to it in some
>> other way. It varies from package to package.
>
>I have placed the example code from Debian Policy inside debian/rules
>near the top of the file. I changed the packages' configure.in and some
>instances of Makefile.in so the program is built with the proper
>CFLAGS finally. This way I did my first steps with autoconf, automake
>and it was worth its hours. ;)
If you can avoid changing configure.in and Makefile.in (actually, I hope
that's Makefile.am?), then please do. Otherwise you can end up with huge
diffs to the generated configure and Makefile.
>While doing all that I just wondered if it is okay to have
>DEB_BUILD_OPTIONS have its effect in configure target. I was unsure if
>i.e. some build daemons want to have DEB_BUILD_OPTIONS take effect
>while calling debian/rules with target "build".
'configure' is an optional target, and the autobuilders pay no attention
to it. If you want it to be used, the build target must depend on
configure anyway, so your problem's solved. In other words, you can
assume that DEB_BUILD_OPTIONS, if needed, will be defined whenever
debian/rules is called.
(As far as I know, incidentally, the build daemons typically don't use
DEB_BUILD_OPTIONS. It's mainly intended for the convenience of users.)
--
Colin Watson [cjw44@flatline.org.uk]
Reply to: