From 7b1f599dd60456eb84684105569a9290d9af3638 Mon Sep 17 00:00:00 2001 From: Jonas Kulla Date: Tue, 27 May 2014 07:35:06 +0200 Subject: [PATCH] mkxp.pro: Add 'BOOST_LIB_SUFFIX' Boost being boost. --- README.md | 2 +- mkxp.pro | 6 +++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3904257..7a3db06 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ mkxp employs Qt's qmake build system, so you'll need to install that beforehand. qmake will use pkg-config to locate the respective include/library paths. If you installed any dependencies into non-standard prefixes, make sure to adjust your `PKG_CONFIG_PATH` variable accordingly. -The exception is boost, which is weird in that it still hasn't managed to pull off pkg-config support (seriously?). *If you installed boost in a non-standard prefix*, you will need to pass its include path via `BOOST_I` and library path via `BOOST_L`, either as direct arguments to qmake (`qmake BOOST_I="/usr/include" ...`) or via environment variables. +The exception is boost, which is weird in that it still hasn't managed to pull off pkg-config support (seriously?). *If you installed boost in a non-standard prefix*, you will need to pass its include path via `BOOST_I` and library path via `BOOST_L`, either as direct arguments to qmake (`qmake BOOST_I="/usr/include" ...`) or via environment variables. You can specify a library suffix (eg. "-mt") via `BOOST_LIB_SUFFIX` if needed. **MRI-Binding**: pkg-config will look for `ruby-2.1.pc`, but you can modify mkxp.pro to use 2.0 instead. This is the default binding, so no arguments to qmake needed (`BINDING=MRI` to be explicit). diff --git a/mkxp.pro b/mkxp.pro index 824c9c5..f994e47 100644 --- a/mkxp.pro +++ b/mkxp.pro @@ -74,7 +74,11 @@ unix { LIBS += -L$$BOOST_L } - LIBS += -lboost_program_options + isEmpty(BOOST_LIB_SUFFIX) { + BOOST_LIB_SUFFIX = $$(BOOST_LIB_SUFFIX) + } + + LIBS += -lboost_program_options$$BOOST_LIB_SUFFIX } # Input