forked from p3ck/restraint
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
README explaining how to use third-party
- Loading branch information
Showing
1 changed file
with
16 additions
and
0 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 |
---|---|---|
@@ -0,0 +1,16 @@ | ||
By default, restraint is dynamically linked against system-wide libraries. | ||
However if you are targetting an older operating system which lacks the | ||
necessary libraries, or if you want to reduce runtime dependencies, restraint | ||
can be statically linked against bundled copies of the libraries. | ||
|
||
First, use the Makefile in this third-party directory to compile the needed | ||
static libraries. They will be installed under third-party/tree. | ||
|
||
Then, you can build restraint against these static libraries: | ||
|
||
PKG_CONFIG_PATH=third-party/tree/lib/pkgconfig make STATIC=1 | ||
|
||
When running tests, you should also pass the path to the gtester binary: | ||
|
||
PKG_CONFIG_PATH=third-party/tree/lib/pkgconfig \ | ||
GTESTER=third-party/tree/bin/gtester make check |