Create options for specifying projects directory and build/ dir

[GoogleCodeExporter]

There have been many requests for the ability to keep a project outside of the 
source dir.  We have not yet decided how this should work, but I'm currently 
contemplating using a combination of cmake options and command line options.

The main challenge here is that we don't have bash on windows, so we are 
limited in what we can put in the shell scripts.  Perhaps a "setbuilddir" batch 
file or something for specifying where it should go.

For specifying the location to search for projects, we can use a cmake option.  
Something like -DPROJECTS_DIR=/path/to/dir

Original issue reported on code.google.com by taxilian on 18 Aug 2010 at 9:40

[GoogleCodeExporter]

Issue 60 has been merged into this issue.

Original comment by taxilian on 18 Aug 2010 at 9:40

[GoogleCodeExporter]

I have modified the prep* scripts to accept two parameters.  

1. The first parameter is the path to the directory where it should search for 
projects.  note that this is one directory up from where your plugin code 
actually resides. 

2. The second parameter is the path where it should generate the project files 
(the build/ directory).

This change should be backwards compatible; prep2010.cmd examples will use the 
examples/ dir for projects and set the build dir to buildex/.  However, you 
could also do:

prep2010.cmd examples buildex_win/
prep2010.cmd ..\mycompany\plugins build_win
..\..\firebreath\prep2010.cmd myplugins build

etc.

Note that you no longer have to be in the root of the firebreath tree in order 
to build the projects, however the defaults will look for the projects/ dir in 
the current location.

The relevant changesets:
http://code.google.com/p/firebreath/source/detail?r=9bf64e6ee77757ff8be4ee4784a6
144df785d47c
http://code.google.com/p/firebreath/source/detail?r=7ea389c43bd76b7f3e57e12db8ec
6445579454f9

Original comment by taxilian on 1 Sep 2010 at 12:44

• Changed state: Fixed