X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/3527f29c8769e09d796c547c0c309f8b86407012..c567d635a2487fc6422d6b58bc13c7bc87518766:/wx-config.in?ds=sidebyside diff --git a/wx-config.in b/wx-config.in index 5a9593fde0..00633b7992 100755 --- a/wx-config.in +++ b/wx-config.in @@ -29,6 +29,7 @@ update_prefixes CC="@CC@" GCC="@GCC@" +GCC_SEARCHES_USR_LOCAL_INCLUDE="@GCC_SEARCHES_USR_LOCAL_INCLUDE@" CXX="@CXX@" LD="@SHARED_LD@" srcdir="@top_srcdir@" @@ -66,6 +67,7 @@ ldlibs_core="@EXTRALIBS_GUI@" ldlibs_xml="@EXTRALIBS_XML@" ldlibs_html="@EXTRALIBS_HTML@" ldlibs_odbc="@EXTRALIBS_ODBC@" +ldlibs_adv="@EXTRALIBS_SDL@" ldflags_gl="@LDFLAGS_GL@" ldlibs_gl="@OPENGL_LIBS@" @@ -167,14 +169,14 @@ Usage: wx-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--release] [--cc] [--cxx] [--ld] wx-config returns configuration information about the installed -version of wxWindows. It may be used to query its version and +version of wxWidgets. It may be used to query its version and installation directories and also retrieve the C and C++ compilers and linker which were used for its building and the corresponding flags. Ordinarily it should be installed to the appropriate system location along with the headers and library files, but it is also possible to -use it to enable builds with an uninstalled wxWindows version for +use it to enable builds with an uninstalled wxWidgets version for package building and bleeding edge developers. To do so, use it like this: @@ -183,10 +185,11 @@ this: Note that any other options supplied must come *after* the prefix specification for it to take effect. ---static must come before --libs and --gl-libs. +--static must come before --cppflags, --cflags, --cxxflags, +--libs and --gl-libs. --libs can take optional argument that contains comma-separated list of -wxWindows libraries to link against. This list can include both core +wxWidgets libraries to link against. This list can include both core and contrib libraries. --gl-libs option is deprecated, used --libs=gl instead. @@ -204,10 +207,13 @@ cppflags() # the ANSI-fied versions of them in its private directory which is searched # after all the directories on the cmd line. # - # the situation is a bit more complicated with -I/usr/local/include: again, - # it shouldn't be specified with gcc which looks there by default anyhow - # and gives warnings (at least 3.1 does) if it is specified explicitly -- - # but this -I switch *is* needed for the other compilers + # the situation is a bit more complicated with -I/usr/local/include: + # it shouldn't be specified with some gcc installations which look there + # by default anyhow and give warnings (at least 3.1 does) if it is + # specified explicitly -- + # but this -I switch *is* needed for other gcc installation and for + # the other compilers. + # So I put a suitable test into configure.in and reuse the result here. # # note that we assume that if we use GNU cc we also use GNU c++ and vice # versa, i.e. this won't work (either for --cflags or --cxxflags) if GNU C @@ -215,7 +221,7 @@ cppflags() # this when/if anybody complains about it if test "${includedir}" != "/usr/include" \ -a "${includedir}" != "/usr/include/c++" \ - -a \( "${GCC}" != "yes" \ + -a \( "${GCC_SEARCHES_USR_LOCAL_INCLUDE}" != "yes" \ -o "${includedir}" != "/usr/local/include" \) \ -a \( "${cross_compiling}" != "yes" \ -o "${includedir}" != "/usr/${target}/include" \) ; @@ -292,7 +298,7 @@ while test $# -gt 0; do echo ${LDFLAGS_EXE} ;; --rezflags) - echo ${MACRESWXCONFIG} + echo `eval echo ${MACRESWXCONFIG}` ;; --libs*)