Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Kea
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
Operations
Operations
Incidents
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Adam Osuchowski
Kea
Commits
413cb59e
Commit
413cb59e
authored
Sep 26, 2018
by
Francis Dupont
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[137-improve-kea-compilation-time-2] Second try
parent
3d0ecb95
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
1 deletion
+4
-1
configure.ac
configure.ac
+3
-1
kea_version.h.in
kea_version.h.in
+1
-0
No files found.
configure.ac
View file @
413cb59e
...
...
@@ -47,7 +47,8 @@ fi
# horribly. When building different branches, the commit-id is different
# and since the config.h is included in most files *and* has a different
# content, ccache can't use cached content and thus has to do full compilation.
echo "#define EXTENDED_VERSION \"${KEA_SRCID}\"" > kea_version.h
# Now it is in kea_version.h and config.status substitutes it.
AC_SUBST(KEA_SRCID)
# Find a separator for path_replacer
for sep in "+" "," ";" "&" "__NONE__"; do
...
...
@@ -1463,6 +1464,7 @@ AC_CONFIG_FILES([Makefile
doc/version.ent
ext/Makefile
ext/gtest/Makefile
kea_version.h
m4macros/Makefile
src/Makefile
src/bin/Makefile
...
...
kea_version.h.in
0 → 100644
View file @
413cb59e
#define EXTENDED_VERSION "@KEA_SRCID@"
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment