[mapguide-internals] build script confusion

[Jason Birch]

I can't even venture a guess why it's currently different :)

The 2.1 installer looks a bit closer to the postbuild:

  /Server/Bin/mgserver.exe
  /Server/Bin/*.dll
  /Server/FDO/*.dll
  /Server/Repositories
  /Server/Logs
  /Server/Resources
  /Server/Schema
  /Server/Temp
  /Server/Wfs
  /Server/Wms

Keeping the binary files in their own directory makes maintaining the installer a lot easier... but there may be a way of aliasing the /Bin directory to the /Server directory so the files just get installed in /Server/.  I'm not entirely sure I'm in favour of this though.  Do relative paths work with serverconfig.ini?  If so, maybe postbuild be modified to install to Bin?

Jason

-----Original Message-----
From: UV
Sent: April-08-09 5:14 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] build script confusion

One thing I keep on stumbling about is that the postbuild.mak is 
creating a different directory structure than the Installer.

so the VS postbuild makes a structure
    $(config)/mgserver.exe
                 /*.dll
                  /FDO/*.dll
                  /Repositories
                  /Logs
                  /Resources
                  /Schema
                  /Temp
                  /Wfs
                  /Wms

the released installer (MGOS2.0.2) creates a structure like this

                  /Bin/mgserver.exe
                  /Bin/*.dll
                  /Bin/FDO/*.dll
                  /Repositories
                  /Logs
                  /Resources
                  /Schema
                  /Temp
                  /Wfs
                  /Wms

I lost at least a few days because of this difference. It means that the 
serverconfig is not compatible and things dont work together until this 
is figured out.
Why like this?