Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
T
trackrdrd
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
trackrdrd
Commits
7f6b4ea2
Commit
7f6b4ea2
authored
Dec 07, 2012
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
document CXXFLAGS and PKG_CONFIG_PATH
parent
c9db526a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
3 deletions
+9
-3
README.rst
trackrdrd/README.rst
+9
-3
No files found.
trackrdrd/README.rst
View file @
7f6b4ea2
...
...
@@ -94,7 +94,7 @@ variable ``VARNISHSRC``::
$ git clone git@repo.org:lhotse-tracking-varnish
$ cd lhotse-tracking-varnish/trackrdrd/
$ ./autogen.sh
$ CFLAGS=-m64 ./configure VARNISHSRC=/path/to/varnish-cache
$ C
XXFLAGS=-m64 C
FLAGS=-m64 ./configure VARNISHSRC=/path/to/varnish-cache
$ make
For self-tests after the build, run::
...
...
@@ -118,12 +118,12 @@ be shown with::
For example, to specify a non-standard installation prefix, add the
``--prefix`` option::
$ CFLAGS=-m64 ./configure VARNISHSRC=/path/to/varnish-cache \\
$ CFLAGS=-m64
CXXFLAGS=-m64
./configure VARNISHSRC=/path/to/varnish-cache \\
--prefix=/path/to/varnish_tracking
Developers can add a number of options as an aid to compiling and debugging::
$ CFLAGS=-m64 ./configure VARNISHSRC=/path/to/varnish-cache \\
$ CFLAGS=-m64
CXXFLAGS=-m64
./configure VARNISHSRC=/path/to/varnish-cache \\
--enable-developer-warnings --enable-debugging-symbols \\
--enable-extra-developer-warnings --enable-werror
...
...
@@ -142,3 +142,9 @@ dumps, in stack traces on assertion failures, for debuggers and so
forth. It is advisable to turn this switch on for production builds
(not just for developer builds), so that runtime errors can more
easily be debugged.
If any of the needed requirements (for instance, the ActiveMQ C++ library)
have been installed into non-default locations, PKG_CONFIG_PATH should
be set to point to the appropriate pkg-config directories, like in this example::
$ PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure #...
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