Notes |
|
(0029370)
|
Rolf Eike Beer
|
2012-04-30 09:49
|
|
Can you point to a documentation of how that really works in autoconf, i.e. if one should pass also command line arguments in there and stuff like that? |
|
|
(0029371)
|
Derek Dai
|
2012-04-30 10:26
|
|
Sorry, I am not that familiar with autotools. Currently, the only way I know to pass PKG_CONFIG to autools is environment variable. Just like configure output below
./configure --help
...
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
LIBS libraries to pass to the linker, e.g. -l<library>
CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CPP C preprocessor
CXXCPP C++ preprocessor
CCAS assembler compiler command (defaults to CC)
CCASFLAGS assembler compiler flags (defaults to CFLAGS)
PKG_CONFIG path to pkg-config utility
PKG_CONFIG_PATH
directories to add to pkg-config's search path
PKG_CONFIG_LIBDIR
path overriding pkg-config's built-in search path
BASE_DEPENDENCIES_CFLAGS
C compiler flags for BASE_DEPENDENCIES, overriding pkg-config
BASE_DEPENDENCIES_LIBS
linker flags for BASE_DEPENDENCIES, overriding pkg-config
CAIRO_BACKEND_CFLAGS
C compiler flags for CAIRO_BACKEND, overriding pkg-config
CAIRO_BACKEND_LIBS
linker flags for CAIRO_BACKEND, overriding pkg-config
GMODULE_CFLAGS
C compiler flags for GMODULE, overriding pkg-config
GMODULE_LIBS
linker flags for GMODULE, overriding pkg-config
XMKMF Path to xmkmf, Makefile generator for X Window System
COLORD_CFLAGS
C compiler flags for COLORD, overriding pkg-config
COLORD_LIBS linker flags for COLORD, overriding pkg-config
GTKDOC_DEPS_CFLAGS
C compiler flags for GTKDOC_DEPS, overriding pkg-config
GTKDOC_DEPS_LIBS
linker flags for GTKDOC_DEPS, overriding pkg-config |
|
|
(0030414)
|
David Cole
|
2012-08-11 21:35
|
|
Sending old, never assigned issues to the backlog.
(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)
If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]
It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
|
|
|
(0035218)
|
Brad King
|
2014-02-27 10:34
|
|
|
|
(0036921)
|
Robert Maynard
|
2014-10-06 10:32
|
|
Closing resolved issues that have not been updated in more than 4 months. |
|