[fdo-internals] RE: [mapguide-internals] fdo installation & build script confusion

[Tom Fukushima]

Let's see if I understand this...Does this work if I need to do both a 32-bit and 64-bit build using the a single version of the source?  This is what the build machine will need to do.  If the answer is no then I think that the change should be made in the FDO build scripts to put the binaries into the correct bin subfolder {bin\release, bin\release64, bin\debug, bin\debug64}.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of UV
Sent: Wednesday, September 23, 2009 6:17 PM
To: MapGuide Internals Mail List; FDO Internals Mail List
Subject: [mapguide-internals] fdo installation & build script confusion

In order to test my sandbox branched from trunk I needed to compile FDO 
from trunk as there are no build server is creating HEAD builds for this 
yet.

this cannot work out of the box because of path issues.

the mapguide buildscript checks for

MgDev\Oem\FDO\Bin\%TYPEBUILD%

whereas the FDO build.bat installs into

MgDev\Oem\FDO\Bin
MgDev\Oem\FDO\Inc
MgDev\Oem\FDO\Lib

I included a patch for mapguide MgDev\build.bat to make this work more 
intuitively as those build scripts still are a lot easier to use  than  
many separate VS solutions

now you can build FDO & mapguide
using:
 >cd %PATH_TO_FDO%
 >build -a=buildinstall -o=%PATH_TO_MGDEV%\Oem 
 >cd %PATH_TO_MGDEV%
 >build

I know this is between to separate OsGeo projects but not being 
responsible does not make it go away.