fdo installation & build script confusion

[UV-2]

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.


Index: build.bat
===================================================================
--- build.bat (revision 4260)
+++ build.bat (working copy)
@@ -204,15 +204,19 @@
 goto custom_error_no_help
 :check_fdo
 :check_fdo_bin
-if exist "%MG_OEM%\FDO\Bin\%TYPEBUILD%" goto check_fdo_inc
+
+REM if exist "%MG_OEM%\FDO\Bin" goto check_fdo_inc
+if exist "%MG_OEM%\FDO\Bin" goto check_fdo_inc
 SET ERRORMSG=Unable to find FDO binaries. Copy the FDO binaries %MG_OEM%\FDO\Bin\%TYPEBUILD%
 goto custom_error_no_help
+
 :check_fdo_inc
-if exist "%MG_OEM%\FDO\Bin\%TYPEBUILD%" goto check_fdo_lib
+if exist "%MG_OEM%\FDO\Inc" goto check_fdo_lib
 SET ERRORMSG=Unable to find FDO headers. Copy the FDO headers into %MG_OEM%\Inc
 goto custom_error_no_help
+
 :check_fdo_lib
-if exist "%MG_OEM%\FDO\Bin\%TYPEBUILD%" goto start_build
+if exist "%MG_OEM%\FDO\Lib" goto start_build
 SET ERRORMSG=Unable to find FDO lib files. Copy the FDO lib files into %MG_OEM%\Lib
 goto custom_error_no_help
 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[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: [hidden email] [mailto:[hidden email]] 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.
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[UV-2]

Fair enough!
I think also mapguide debug with fdo release might be a popular
combination....

Looks like it makes more sense that the install script of the fdo
package is updated....

however i had to change the paths in my installations manually a few
times already.
for the build server fixing it in the scripts will be mandatory.

just too bad that  in the current devel process i am writing a  lot more
messages than the code that needs only little tweaks...
I suggest to consider a synchronuous peer review process where small
patches can be instantly accepted in a brief
chat or skype session after at least 3 people looked at it.


Tom Fukushima wrote:

> 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: [hidden email] [mailto:[hidden email]] 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.
> _______________________________________________
> fdo-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>
>  

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals