Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
ApplicationCore
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ChimeraTK Mirror
ApplicationCore
Commits
69ed1262
Commit
69ed1262
authored
8 years ago
by
Martin Christoph Hierholzer
Browse files
Options
Downloads
Patches
Plain Diff
properly pass the build version to the cmake building the library inside the Debian packaging tools
parent
99a9f1c0
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
cmake/make_debian_package.sh.in
+5
-4
5 additions, 4 deletions
cmake/make_debian_package.sh.in
with
5 additions
and
4 deletions
cmake/make_debian_package.sh.in
+
5
−
4
View file @
69ed1262
...
...
@@ -17,9 +17,9 @@
# This cmake.in file requires the following variables to be set:
# PACKAGE_BASE_NAME This is the debian package name, not the project name (e.g. libraries must start with lib,
# all lower case, no underscore)
# PACKAGE_FULL_LIBRARY_VERSION The full version, incl. build version and patch version
# PACKAGE_TAG_VERSION The tag for which the package is build
# PACKAGE_MAJORMINOR_VERSION The library version without the patch level (i.e. just "MAJOR.MINOR")
# PACKAGE_PATCH_VERSION The patch level
# PACKAGE_MESSAGE The message for the debian package log
# PACKAGE_DEPENDENCY_VERSIONS A space-separated list of dependency names and versions, each connected by a dash, e.g.:
# "DeviceAccess-0.15 ControlSystemAdapter-0.1"
...
...
@@ -53,17 +53,18 @@ tar -czf ${BUILD_DIR_NAME}.orig.tar.gz ${BUILD_DIR_NAME}
cp
-r
../debian_from_template
${
BUILD_DIR_NAME
}
/debian
cd
${
BUILD_DIR_NAME
}
#The package versions for doocs / Ubuntu contain the codename of the distribution. Get it from the system.
#The package versions for doocs / Ubuntu contain the codename
PROJECT_BUILDVERSION
of the distribution. Get it from the system.
CODENAME
=
`
lsb_release
-c
|
sed
"{s/Codename:
\s
*//}"
`
#Obtain build version
BUILD_VERSION
=
`
"@CMAKE_SOURCE_DIR@/cmake/getDebianBuildVersion"
@PROJECT_NAME@ @PACKAGE_MAJORMINOR_VERSION@
${
CODENAME
}
@PACKAGE_DEPENDENCY_VERSIONS@
`
||
exit
1
BUILD_NUMBER
=
`
"@CMAKE_SOURCE_DIR@/cmake/getDebianBuildVersion"
@PROJECT_NAME@ @PACKAGE_MAJORMINOR_VERSION@
${
CODENAME
}
@PACKAGE_DEPENDENCY_VERSIONS@
`
||
exit
1
export
PROJECT_BUILDVERSION
=
"
${
CODENAME
}${
BUILD_NUMBER
}
"
#Before building the package we will update the changelog. This is easier from a shell script
#because debchange does the right format and the current date, user name and email automatically for us.
#Use the NAME and EMAIL environment variables to get correct values if needed (usually the email is
# user@host instead of first.last@institute, for instance killenb@mskpcx18571.desy.de instead of martin.killenberg@desy.de).
debchange
--create
--package
@PACKAGE_BASE_NAME@
-v
@PACKAGE_
FULL_LIBRARY_VERSION@-
${
BUILD
_VERSION
}
--distribution
${
CODENAME
}
@PACKAGE_MESSAGE@
debchange
--create
--package
@PACKAGE_BASE_NAME@
-v
@PACKAGE_
MAJORMINOR_VERSION@-
${
PROJECT_BUILDVERSION
}
-@PACKAGE_PATCH
_VERSION
@
--distribution
${
CODENAME
}
@PACKAGE_MESSAGE@
#Now everything is prepared and we can actually build the package.
#If you have a gpg signature you can remove the -us and -uc flags and sign the package.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment