[fdo-internals] FDO env. variables
traian.stanev at autodesk.com
Wed Apr 11 13:42:45 EDT 2007
If you run setenvironment and then run devenv from within that command
window, wouldn't Visual Studio pick up the correct environment vars?
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Mateusz
Sent: Wednesday, April 11, 2007 1:40 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO env. variables
Haris Kurtagic wrote:
> The additional work I have is when compiling FDO and MapGuide itself.
> If I work with different versions ( and I do ) I need to change env,
> variables to compile it.
Yes, that's what I do too.
I use FDO 3.2.0 and current SVN and today I added 3.2.2 Beta.
Sometimes I need to compile my provider using
different versions many times a day.
Some time ago I tried to configure FDO with Visual Studio Property
but I gave up. It would need to re-factor current building system
It's easy to use various versions if you build from command line only,
then setenvironment.bat script should do the job,
but if you use VS projects and it's not easy then.
Summarizing, I have system-wide environment variables defined as
And if I want to change FDO version, I only update FDOCORE variable
My Compyter -> Properties -> Advanced -> Environment Variables
fdo-internals mailing list
fdo-internals at lists.osgeo.org
More information about the fdo-internals