forked from ossrs/srs
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
cae3232
commit 27b2049
Showing
2 changed files
with
12 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,23 @@ | ||
# We can only build Debian packages, if the Debian build tools are installed | ||
if [ \! -x /usr/bin/debuild ]; then | ||
echo "Cannot find /usr/bin/debuild. Not building Debian packages." 1>&2 | ||
exit 0 | ||
echo "Cannot find /usr/bin/debuild. Not building Debian packages." 1>&2 | ||
exit 0 | ||
fi | ||
|
||
# Double-check we're in the packages directory, just under rootdir | ||
if [ \! -x ./configure ]; then | ||
echo "Must run $0 in the 'trunk' directory, under the root directory." 1>&2 | ||
exit 0 | ||
fi | ||
|
||
trap 'rm -rf '`pwd`/debian'; exit $?' EXIT SIGHUP SIGINT SIGTERM | ||
|
||
rm -rf debian | ||
|
||
# Debian has very specific requirements about the naming of build | ||
# directories, and tar archives. It also wants to write all generated | ||
# packages to the parent of the source directory. We accommodate these | ||
# requirements by building directly from the tar file. | ||
|
||
# This is one of those 'specific requirements': where the deb control files live | ||
# Debian has very specific requirements about the naming of build directories | ||
cp -a "packaging/deb" "debian" | ||
|
||
# Now, we can call Debian's standard build tool | ||
debuild -uc -us -tc -b | ||
|
||
echo | ||
echo "The Debian package build finished." |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters