Page History
- 2012-Nov-15 11:33 adesmet
- 2012-Nov-13 15:20 adesmet
- 2011-Jun-01 15:02 johnkn
- 2011-Jun-01 13:18 johnkn
- 2011-Jan-04 16:29 danb
- 2010-Sep-20 14:52 johnkn
- 2010-Sep-03 15:48 johnkn
- 2010-Apr-26 15:29 tannenba
- 2009-Sep-01 12:36 griswold
- 2009-Sep-01 12:26 griswold
- 2009-Sep-01 12:23 griswold
- 2009-Jul-30 17:06 burnett
- 2009-Jul-11 02:09 burnett
- 2009-May-05 16:28 burnett
- 2009-Apr-24 12:01 burnett
- 2009-Apr-24 11:59 burnett
- 2009-Jan-13 14:30 burnett
- 2009-Jan-13 14:26 burnett
Requirements
- Active-State Perl
- Microsoft Visual Studio 2008 Edition + SP1
- Microsoft Windows Server 2003 SP1 Platform SDK
NOTE: The Platform SDK's version is very important. This is the latest version that both supports Windows 2000 and does not play silly tricks with the registry. As for Microsoft Visual Studio Team System 2008, only select the x86 compiler (which is the default); otherwise, some of the environment scripts will not be written correctly (on Vista, anyway; I haven't tested this on other platforms). Not sure why this happens exactly; but if you do select the other options, the Microsoft .NET Platform directory is exported incorrectly to the environment (maybe I'll get around to reporting this to them at some point). The problem is that our command-line build depends on a tool shipped with the Microsoft .NET Platform: msbuild.exe
. It's a glorified version of make
that uses XML as it's input. What's nice about it is that it will build the project directly, rather than manually exporting Makefiles
for consumption, as was previously required.
Installation
- Install all the packages listed above to their default destinations, as some of our scripts are reliant on these locations. We do take great efforts to avoid hard-coded paths; however, some things cannot be fully auto-detected at present (sorry, but that is the state-of-the-art right now).
- The order in which you install them is also important; for instance, a Visual Studio Service Pack should be installed after Visual Studio is installed. Also, for proper integration, the Platform SDKs should be installed after Visual Studio has completed its installation, so that it will integrate gracefully with the software.
- Finally, it is important to run Visual Studio once before installing the Platform SDKs, so that they will integrate with the studio properly.
Microsoft Visual Studio Team System 2008
- Visual C#
- Visual Basic
- Visual Web Developer
- Dotfuscator Community Edition
- Unit Testing Tools
- Microsoft SQL Server 2005 Express Edition (x86)
- Crystal Reports Basic for Visual Studio 2008
Do, however, make sure to keep the Redistributable Merge Modules, as the installer (the MSI) will use these to install the correct runtime libraries in the appropriate location.
Configuration
Visual Studio 2008: Build and Run
- From the Tools menu, select Options...
- In the Options dialog, expand Project and Solutions, and select Build and Run
- On the right hand side, set the maximum number of parallel project builds to 1.
This setting is stored persistently and not in the user configuration files; therefore, you will only need to be done once per user.
Some Background
Environment
Externals
EXTERN_DIR = C:\workspace\externals\externals
This can be set at the command line, or made permanent via the GUI:
- Open the Control Panel
- Double click on the System applet
- In the left pane, under Tasks, click on Advanced system settings
- In System Properties select the Advanced tab
- Click on the Environment Variables...
- Click on New... and enter the path to the externals
NMI
For details on creating the template account Condor, please refer to WindowsUserProfiles.
Command Prompt
- Right-click your Command Prompt shortcut, select Properties > Advanced... > Check Run as administrator
- Click OK
Visual Studio
- Right-click your Visual Studio shortcut, select Properties > Advanced... > Check Run as administrator
- Click OK
gsoap.mak
Eccentricities
gsoap.mak
(i.e. C:\Temp). The presence of this directory is required for Condor to compile. This will be changed for future releases.
Building
C:\workspace\source\msbuild
directory. See GitingTheCode for further details on getting the source.
From the Command-line
- Run make.bat;
- Ignore the compiler warnings, they are mostly innocuous and likely to disappear in upcoming releases;
- If there are any errors, please reffer to the Trouble Shooting sub-section bellow.
From the IDE
- Run run_msdev.bat;
- Ensure the Release "Solution Configuration" is selected (Debug is the default);
- From the Project menu, select Build Solution;
- Ignore the compiler warnings, they are mostly innocuous and likely to disappear in subsequent releases;
- If there are any errors, please refer to the Trouble Shooting sub-section bellow.
Customizing the debugger's variable value view
You need to locate a file called AUTOEXP.DAT
in your Visual C++ installation. By default it will be:
VC++ 6.0:
C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\AUTOEXP.DAT
VC++ 9.0:
C:\Program Files\Microsoft Visual Studio 9.0\Common7\Packages\Debugger\autoexp.dat
After you have made the changes and saved the file, you will need to restart Visual C++ for the changes to take effect.
Trouble Shooting
set_env.bat
. You can remedy this by renaming %ProgramFiles%\Microsoft SDKs to something else while developing or compiling the Condor software. This will not be a problem when Condor drops support for Windows 2000.
Put shortly, if you do not see the following two lines in the build output:
Setting environment for using Microsoft Visual Studio 2008 x86 tools. Targeting Windows 2000 and IE 5.0 RETAIL
Then there is most certainly a problem.
That said, and paradoxical as it may sound, a build can succeed with this directory intact. It all hinges on the order in which you install the software packages. That's why we stressed the order in which you install the software packages above. If, by chance, it happens to work for you in another order, then consider yourself lucky; having tried several, this seems to be the most dependable procedure.