|
Revision 19450, 251 bytes
(checked in by patrick, 2 years ago)
|
Finish off the transition to using flagpoll by extending the .fpc file for
each of the Juggler modules to identify its dependencies. In this way,
querying a module gives all the paths needed to build against it.
Fortunately for us, Boost is the only dependency we have where neither
pkg-config nor flagpoll support exists. To handle this case, I have written
two short flagpoll files: one for the Boost headers and one for
Boost.Filesystem.
As a result of this change, the following changes to the build are now in
effect:
- One of PKG_CONFIG_PATH, FLAGPOLL_PATH, or (DY)LD_LIBRARY_PATH must
be set when building so that flagpoll can find .pc or .fpc files for
dependencies that are not available in the default search path.
Having things installed in the default flagpoll search path eliminates
the need for this extra step.
- The configure script options —with-gmtl and —with-cppdom are gone.
Instead, flagpoll finds those dependencies on its own (assuming that
its search path is set up correctly).
- It is no longer necessary to have $VJ_BASE_DIR/bin in your path to
build applications. Instead, it is sufficient to include
$VJ_BASE_DIR/lib(64) in (DY)LD_LIBRARY_PATH for flagpoll to be able
to find the .fpc files that it needs. (Strictly speaking, this has
been the case for several months now.)
|
- Property svn:eol-style set to
native
|
| Line | |
|---|
| 1 |
# Private Variables |
|---|
| 2 |
prefix = @BOOST_ROOT@ |
|---|
| 3 |
|
|---|
| 4 |
# Standard Flagpoll Variables |
|---|
| 5 |
Name: Boost Headers |
|---|
| 6 |
Description: The header files for Boost. |
|---|
| 7 |
URL: http://www.boost.org/ |
|---|
| 8 |
Version: @BOOST_VERSION_DOT@ |
|---|
| 9 |
Provides: Boost boost |
|---|
| 10 |
Arch: no_arch |
|---|
| 11 |
Cflags: @BOOST_INCLUDES@ |
|---|
