|
@@ -18,6 +18,7 @@
|
|
|
.\" along with this program. If not, see <https://www.gnu.org/licenses/>.
|
|
|
.
|
|
|
.TH dpkg\-buildflags 1 "%RELEASE_DATE%" "%VERSION%" "dpkg suite"
|
|
|
+.nh
|
|
|
.SH NAME
|
|
|
dpkg\-buildflags \- returns build flags to use during package build
|
|
|
.
|
|
@@ -223,9 +224,9 @@ problems in the source code or build system.
|
|
|
This setting (disabled by default) adds any warning option that reliably
|
|
|
detects problematic source code. The warnings are fatal.
|
|
|
The only currently supported flags are \fBCFLAGS\fP and \fBCXXFLAGS\fP
|
|
|
-with flags set to \fB\-Werror=array\-bounds\fP, \fB\%\-Werror=clobbered\fP,
|
|
|
-\fB\%\-Werror=implicit\-function\-declaration\fP and
|
|
|
-\fB\%\-Werror=volatile\-register\-var\fP.
|
|
|
+with flags set to \fB\-Werror=array\-bounds\fP, \fB\-Werror=clobbered\fP,
|
|
|
+\fB\-Werror=implicit\-function\-declaration\fP and
|
|
|
+\fB\-Werror=volatile\-register\-var\fP.
|
|
|
.
|
|
|
.TP
|
|
|
.B canary
|
|
@@ -407,12 +408,12 @@ This setting (enabled by default) adds
|
|
|
.B \-Wdate\-time
|
|
|
to \fBCPPFLAGS\fP.
|
|
|
This will cause warnings when the \fB__TIME__\fP, \fB__DATE__\fP and
|
|
|
-\fB\%__TIMESTAMP__\fP macros are used.
|
|
|
+\fB__TIMESTAMP__\fP macros are used.
|
|
|
.
|
|
|
.TP
|
|
|
.B fixdebugpath
|
|
|
This setting (enabled by default) adds
|
|
|
-.BI \%\-fdebug\-prefix\-map= BUILDPATH =.
|
|
|
+.BI \-fdebug\-prefix\-map= BUILDPATH =.
|
|
|
to \fBCFLAGS\fP, \fBCXXFLAGS\fP, \fBOBJCFLAGS\fP, \fBOBJCXXFLAGS\fP,
|
|
|
\fBGCJFLAGS\fP, \fBFFLAGS\fP and \fBFCFLAGS\fP where \fBBUILDPATH\fP is
|
|
|
set to the top-level directory of the package being built.
|
|
@@ -464,7 +465,7 @@ See the \fBFEATURE AREAS\fP section for details.
|
|
|
.B DEB_VENDOR
|
|
|
This setting defines the current vendor.
|
|
|
If not set, it will discover the current vendor by reading
|
|
|
-\fB\%%PKGCONFDIR%/origins/default\fP.
|
|
|
+\fB%PKGCONFDIR%/origins/default\fP.
|
|
|
.TP
|
|
|
.B DEB_BUILD_PATH
|
|
|
This variable sets the build path (since dpkg 1.18.8) to use in features
|
|
@@ -530,7 +531,7 @@ options to configure or \fBmake\fP(1) directly, as shown above.
|
|
|
For other build systems, or when you need more fine-grained control
|
|
|
about which flags are passed where, you can use \fB\-\-get\fP. Or you
|
|
|
can include \fBbuildflags.mk\fP instead, which takes care of calling
|
|
|
-\fB\%dpkg\-buildflags\fP and storing the build flags in make variables.
|
|
|
+\fBdpkg\-buildflags\fP and storing the build flags in make variables.
|
|
|
.PP
|
|
|
If you want to export all buildflags into the environment (where they
|
|
|
can be picked up by your build system):
|