[Dev] Chandler Windows startup scripts: RunChandler and RunPython

[Mike Taylor]

While trying to get the quick build tinderboxes to run the Functional 
Tests I have located a problem with the RunChandler.bat and 
RunPython.bat startup scripts.

On Windows we have to tell the OS that we have a custom dll search path 
so that Windows will locate our dll's as they are not in any of the 
"normal" places the OS looks for them by default.  This is done for us 
by chandler.exe and chandlerDebug.exe - a small program that sets the 
environment up, calls the OS API to set the search path and then calls 
python(_d).

The problem is that the RunChandler.bat calls the RunPython.bat and 
passes it the parameters to run Chandler.py.  RunPython.bat then calls 
python.exe or python_d.exe and passes along those parameters.

None of the Run*.bat steps involves the Chandler Launcher so that means 
the search path may not be set correctly.

Right now I will be modifying RunChandler.bat to use the launcher as 
that will fix my tinderbox issue.  After that I need to research the 
RunPython issue a bit and then I'll post a proposal here for 
discussion.

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060308/2ba6a51f/PGP.pgp