It was attached as test~bat.txt (with the original name being test.bat)
I assume that a mail server (probably the apache list server) mangled
the file name as a safety measure.
The contents of the file are very simple though:
call generate.bat /CONFIG:msvc-8.0 /BUILDDIR:%~dp0\build /LOCALES:no
/LOCALETESTS:no
call build\build_msvc-8.0.bat 15d
--Andrew Black
Farid Zaripov wrote:
-----Original Message-----
From: Andrew Black [mailto:[EMAIL PROTECTED]
Sent: Saturday, October 28, 2006 12:57 AM
To: [email protected]
Subject: Windows infrastructure bug
The source directory I am using in this situation is
'C:\build\ablack\stdcxx-test', with the build directory being
'C:\build\ablack\stdcxx-test\build'. At the root of the
source directory, I have a batch file which creates the build
solutions using the generate.bat batch file, then builds one
of the build types using the generated build_%CONFIG%.bat
batch file. A simplified version of this batch file (hard
wired to produce 15d builds with msvc-8.0) is attached as test.bat.
When run, the configuration process fails for unknown reasons
during the sanity check process. The config.log file
generated is attached. To complicate the situation, the
generated solution appears to function correctly when built
from within the devenv GUI, and when the build_msvc-8.0.bat
script is invoked directly from the command line (both from
the build directory and the source directory).
Hmm. I see strange "static" in attached config.log. This source is not
present in command line for compiling and linking,
but linked tries to find static.obj file...
Can I see your batch file (full or simplified) ? I didn't found it in
attachment.
Farid.
