.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "DH_MAKESHLIBS 1" .TH DH_MAKESHLIBS 1 "2019-09-14" "12.6" "Debhelper" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" dh_makeshlibs \- automatically create shlibs file and call dpkg\-gensymbols .SH "SYNOPSIS" .IX Header "SYNOPSIS" \&\fBdh_makeshlibs\fR [\fIdebhelper options\fR] [\fB\-m\fR\fImajor\fR] [\fB\-V\fR\fI[dependencies]\fR] [\fB\-n\fR] [\fB\-X\fR\fIitem\fR] [\fB\-\-\fR \fIparams\fR] .SH "DESCRIPTION" .IX Header "DESCRIPTION" \&\fBdh_makeshlibs\fR is a debhelper program that automatically scans for shared libraries, and generates a shlibs file for the libraries it finds. .PP It will also ensure that ldconfig is invoked during install and removal when it finds shared libraries. Since debhelper 9.20151004, this is done via a dpkg trigger. In older versions of debhelper, \fBdh_makeshlibs\fR would generate a maintainer script for this purpose. .PP Since debhelper 12.3, \fBdh_makeshlibs\fR will by default add an additional \&\fIudeb\fR line for udebs in the shlibs file, when the udeb has the same name as the deb followed by a \*(L"\-udeb\*(R" suffix (e.g. if the deb is called \&\*(L"libfoo1\*(R", then debhelper will auto-detect the udeb if it is named \&\*(L"libfoo1\-udeb\*(R"). Please use the \fB\-\-add\-udeb\fR and \fB\-\-no\-add\-udeb\fR options below when this auto-detection is insufficient. .PP If you previously used \fB\-\-add\-udeb\fR and is considering to migrate to using the auto-detection new auto-detection feature in 12.3, then please remember to test that the resulting \fIDEBIAN/shlibs\fR files are as expected. There are some known corner cases, where the auto-detection is insufficient. These include when the udeb contains library files from multiple regular deb packages or when the packages do not follow the expected naming convention. .SH "FILES" .IX Header "FILES" .IP "debian/\fIpackage\fR.shlibs" 4 .IX Item "debian/package.shlibs" Installs this file, if present, into the package as DEBIAN/shlibs. If omitted, debhelper will generate a shlibs file automatically if it detects any libraries. .Sp Note in compat levels 9 and earlier, this file was installed by \&\fBdh_installdeb\fR\|(1) rather than \fBdh_makeshlibs\fR. .IP "debian/\fIpackage\fR.symbols" 4 .IX Item "debian/package.symbols" .PD 0 .IP "debian/\fIpackage\fR.symbols.\fIarch\fR" 4 .IX Item "debian/package.symbols.arch" .PD These symbols files, if present, are passed to \fBdpkg\-gensymbols\fR\|(1) to be processed and installed. Use the \fIarch\fR specific names if you need to provide different symbols files for different architectures. .SH "OPTIONS" .IX Header "OPTIONS" .IP "\fB\-m\fR\fImajor\fR, \fB\-\-major=\fR\fImajor\fR" 4 .IX Item "-mmajor, --major=major" Instead of trying to guess the major number of the library with objdump, use the major number specified after the \-m parameter. This is much less useful than it used to be, back in the bad old days when this program looked at library filenames rather than using objdump. .IP "\fB\-V\fR, \fB\-V\fR\fIdependencies\fR" 4 .IX Item "-V, -Vdependencies" .PD 0 .IP "\fB\-\-version\-info\fR, \fB\-\-version\-info=\fR\fIdependencies\fR" 4 .IX Item "--version-info, --version-info=dependencies" .PD If a shlibs file is generated by this program, this option controls what version will be used in the dependency relation. .Sp In compat 12 and later, \fBdh_makeshlibs\fR defaults to \fB\-VUpstream\-Version\fR. In compat 11 and earlier the default behaved like \fB\-VNone\fR.. .Sp The \fBdh_makeshlibs\fR tool can generate dependencies in three variants: .RS 4 .IP "\fB\-VUpstream\-Version\fR" 4 .IX Item "-VUpstream-Version" The dependency will be "\fIpackagename\fR \fB(>\fR= \fIpackageversion\fR\fB)\fR". Note that \fIUpstream-Version\fR is case-sensitive and must be written exactly as shown here. .Sp This is a conservative setting that always ensures that other packages' shared library dependencies are at least as tight as they need to be (unless the library is prone to changing \s-1ABI\s0 without updating the upstream version number). .Sp The flip side is that packages might end up with dependencies that are too tight in some cases (note a symbols file can mitigate this issue). This is often of minor temporary inconvenience and usually a lot better than the fall out caused by forgetting to bump the dependency information. .Sp This explicit form was added in debhelper/11.3. In previous versions, a \fB\-V\fR without any dependency information was used instead (and that form still works) .IP "\fB\-VNone\fR" 4 .IX Item "-VNone" The dependency will be "\fIpackagename\fR". Note that \fINone\fR is case-sensitive and must be written exactly as shown here. .Sp This form is generally unsafe with the only exception being if upstream does not extend the \s-1ABI\s0 in any way. However, most upstreams improve their interfaces over time and packagers are recommended to use \&\fB\-VUpstream\-Version\fR (or one of the other forms of \fB\-V\fR\fIdependencies\fR). .Sp Alternatively, this may be sufficient if (and only if) the package uses symbol versioning (see \fBdpkg\-gensymbols\fR\|(1)) and does \fInot\fR build any udeb packages. Note that symbols are not supported for udeb packages, which solely relies on shlibs for dependency handling. .IP "\fB\-V\fR\fIpackage-relation\fR" 4 .IX Item "-Vpackage-relation" In this case, the value passed to \fB\-V\fR will be used as a dependency relation. The \fIpackage-relation\fR should generally be of the form "\fIsome-package-name\fR \fB(>\fR= \fIsome-package-version\fR\fB)\fR". Remember to include the package name. .Sp Note that debhelper will use the value \fIas it is\fR with no sanity checking or modification. In \fIrare special\fR cases, this is needed to generate a dependency on a different package than the one containing the library. .RE .RS 4 .Sp When choosing a value for this option, please keep mind that if the package provides a symbols file, then that it generally preferred over the shlibs file for regular .deb packages. See \fBdpkg\-shlibdeps\fR\|(1) for more information on this topic. .RE .IP "\fB\-n\fR, \fB\-\-no\-scripts\fR" 4 .IX Item "-n, --no-scripts" Do not add the \*(L"ldconfig\*(R" trigger even if it seems like the package might need it. The option is called \fB\-\-no\-scripts\fR for historical reasons as \fBdh_makeshlibs\fR would previously generate maintainer scripts that called \fBldconfig\fR. .IP "\fB\-X\fR\fIitem\fR, \fB\-\-exclude=\fR\fIitem\fR" 4 .IX Item "-Xitem, --exclude=item" Exclude files that contain \fIitem\fR anywhere in their filename or directory from being treated as shared libraries. .IP "\fB\-\-add\-udeb=\fR\fIudeb\fR" 4 .IX Item "--add-udeb=udeb" Create an additional line for udebs in the shlibs file and use \fIudeb\fR as the package name for udebs to depend on instead of the regular library package. .Sp This is option is only useful for special cases such as when debhelper cannot auto-detect package name of the udeb package, when the udeb will contain libraries from multiple deb packages, or when the udeb contains libraries \fBnot\fR present in the deb package. .IP "\fB\-\-no\-add\-udeb\fR" 4 .IX Item "--no-add-udeb" Do not add any udeb lines to the shlibs file. This can be used to disable the default auto-detection of udebs. .IP "\fB\-\-\fR \fIparams\fR" 4 .IX Item "-- params" Pass \fIparams\fR to \fBdpkg\-gensymbols\fR\|(1). .SH "EXAMPLES" .IX Header "EXAMPLES" .IP "\fBdh_makeshlibs \-VNone\fR" 4 .IX Item "dh_makeshlibs -VNone" Assuming this is a package named \fIlibfoobar1\fR, generates a shlibs file that looks something like: libfoobar 1 libfoobar1 .IP "\fBdh_makeshlibs \-VUpstream\-Version\fR" 4 .IX Item "dh_makeshlibs -VUpstream-Version" Assuming the current version of the package is 1.1\-3, generates a shlibs file that looks something like: libfoobar 1 libfoobar1 (>= 1.1) .IP "\fBdh_makeshlibs \-V 'libfoobar1 (>= 1.0)'\fR" 4 .IX Item "dh_makeshlibs -V 'libfoobar1 (>= 1.0)'" Generates a shlibs file that looks something like: libfoobar 1 libfoobar1 (>= 1.0) .SH "SEE ALSO" .IX Header "SEE ALSO" \&\fBdebhelper\fR\|(7) .PP This program is a part of debhelper. .SH "AUTHOR" .IX Header "AUTHOR" Joey Hess