Andrew, have you guys figured out what the problem was with the IA64
Windows builds?
Martin
Andrew Black wrote:
>
>
> Farid Zaripov wrote:
>
>>> -----Original Message-----
>>> From: Andrew Black [mailto:ablack@roguewave.com] Sent: Monday,
>>> September 25, 2006 10:56 PM
>>> To: stdcxx-dev@incubator.apache.org
>>> Subject: Re: [PATCH] Scripts, generating solution and projects for
>>> MSVC/ICC
>>>
>>> I am experiencing some strange behavior when attempting to run the
>>> generate.bat script on 64 bit windows XP after applying this patch.
>>> The behavior observed is as follows:
>>>
>>> D:\ablack\stdcxx>generate.bat /CONFIG:msvc-8.0
>>> /BUILDDIR:D:\ablack\stdcxx-build Solution generation script Checking
>>> arguments...
>>> Building directory tree created
>>> Checking consistence...
>>> Unable to create VCProjectEngine object: Could not create object
>>> named "VisualStudio.VCProjectEngine.8.0".
>>
>>
>> The place of fail:
>>
>> try
>> {
>> VCProjectEngine =
>> WScript.CreateObject("VisualStudio.VCProjectEngine." + VERSION);
>> }
>> catch (e)
>> {
>> WScript.StdErr.WriteLine("Unable to create VCProjectEngine
>> object: " + e.message);
>> WScript.Quit(3);
>> }
>>
>> Unfortunately, I don't have 64-bit Platform for testing the scripts.
>>
>> Check, please, the presence of the
>> HKEY_CLASSES_ROOT\VisualStudio.VCProjectEngine.8.0 key in the registry.
>>
>> If the MSVC8.0 is installed this key should be present.
>>
>> Farid.
>
>
> Greetings Farid.
>
> Looking at the registry for the machine indicates that the key in
> question is present. A thought I had was that it could be an issue with
> trying to call a 64 bit library from a 32 bit version of cscript, or
> vice versa, but altering the path in an attempt to use what I believe to
> be the 64 bit version of cscript didn't solve anything.
>
> I'm poking around MSDN trying to find any clues to a possible cause, but
> I don't seem to be having much luck.
>
> --Andrew Black
|