Changes between Version 33 and Version 34 of BaseInstall

Timestamp:

Apr 8, 2010, 12:57:25 PM (16 years ago)

Author:

Christoph Mayer

Comment:

--

BaseInstall

@@ -45 +45 @@
 }}} 
 This script will automatically download all necessary libraries and compile them inside a new {{{./libs}}} subdirectory and install them into {{{./build}}}. In the end the ariba library itself is compiled to {{{./build}}}. You can safely delete the  {{{./libs}}} subdirectory after the process. 
+
+Here is the manual way to go: If you install Ariba locally and have the required libraries also installed locally, you can use a {{{config.site}}} script to make it easier. The {{{config.site}}} file must reside in a folder called {{{share}}}. If your install path is {{{/home/foo/local}}} and you do a {{{./configure --prefix=/home/foo/local}}}, ariba headers will be installed in {{{/home/foo/local/include}}}, and the ariba library in {{{/home/foo/local/lib}}}. To use a {{{config.site}}} script, create a folder {{{/home/foo/local/share}}} and create a file {{{config.site}}}. Such a file has paths towards required header files and libraries.
+
+{{{
+with_boost=/home/foo/Libraries/include
+test -z "$CPPFLAGS" && CPPFLAGS='-I/home/foo/Libraries/include'
+test -z "$LDFLAGS" && LDFLAGS='-L/home/foo/Libraries/lib'
+}}}
+
+If you now do a {{{./configure --prefix=/home/foo/local}}}, the {{{config.site}}} will be found and the paths therein used for finding libraries. If you e.g. have multiple libraries distributed in their own include folders, you can also have multiple includes:
+
+{{{
+test -z "$CPPFLAGS" && CPPFLAGS='-I/home/foo/Libraries/include -I/home/foo/otherlibrary/include'
+}}}
 
 == Running the !PingPong Sample ==