[opensource-dev] Is 'STANDALONE' confusing?

[Nicky Perian]

I have tried various configurations and ended with this and the only way I can 
get a build with fmod is coping the stuff to package.

C:\Users\Bill\lindenhg\autobuild\bin\autobuild --debug configure -c 
VC10msbuildRelWithDebInfo -- -DLL_TESTS:BOOL=OFF 
-DMSVC_REDIST_PATH:PATH=C:\Users\Bill\lindenhg\WorkaroundFiles\vcredist_vc100_30319_x86
 -DPACKAGE:BOOL=ON -DFMOD:BOOL=ON 
-DFMOD_INCLUDE_DIR=C:\olibs\trunk\libraries\include 
-DFMOD_LIBRARY=C:\olibs\trunk\libraries\i686-win32\lib\release\fmod.lib 2>&1 
|c:\cygwin\bin\tee config.log



________________________________
From: Jonathan Welch <jhwelch at gmail.com>
To: Philippe (Merov) Bossut <merov at lindenlab.com>
Cc: opensource-dev at lists.secondlife.com
Sent: Thu, March 3, 2011 4:31:19 AM
Subject: Re: [opensource-dev] Is 'STANDALONE' confusing?

> In case where you cannot (or don't want to) use the LL prebuilt binary (e.g.
> fmod) and/or do not have them in some system folder (Find<package>.cmake
> won't find them), you can (or should) specify a path using:
> -D<package>_INCLUDE_DIR=<path> -D<package>_LIBRARY=<path>

I tried many variations of this for Fmod, with "/" and "\" in the path, etc.
in the autobuild configure step but could not get it to work.