[impdev] Windows build issues

Nicky Perian nickyperian at yahoo.com
Wed Apr 20 15:52:02 PDT 2011

I got past the side by side errors with 1-4 exp  04-19-2011  under vs2010 with 
the below edits.
The key "I think" is having newversion be the newest and oldversion be the just 
past version.
This build goes all the way to a good NSIS installer.
Need additional test of runtime if everything tests ok I will push later this 
evening and post to lists when done. 



?xml version="1.0" ?><!--This file is automatically generated by the build. see 
              <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <assemblyIdentity name="Microsoft.VC100.CRT" processorArchitecture="x86" 
publicKeyToken="1fc8b3b9a1e18e3b" type="win32"/>
        <bindingRedirect newVersion="10.0.40219.1" oldVersion="10.0.30319.1"/>


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <!-- Copyright (c) Microsoft Corporation.  All rights reserved. -->
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
        <file name="msvcr100.dll" /> <file name="msvcp100.dll" /> <file 
name="msvcm100.dll" />

From: Nicky Perian <nickyperian at yahoo.com>
To: Adric R <hakushakukun at gmail.com>; chris-tuchs at hushmail.com
Cc: impdev at lists.imprudenceviewer.org
Sent: Wed, April 20, 2011 2:44:42 PM
Subject: Re: [impdev] Windows build issues

I managed to get 4-02-2011 built and running with vs2010. Still fighting with 
4-19 though.

From: Adric R <hakushakukun at gmail.com>
To: chris-tuchs at hushmail.com
Cc: nickyperian at yahoo.com; impdev at lists.imprudenceviewer.org
Sent: Wed, April 20, 2011 1:22:43 PM
Subject: Re: [impdev] Windows build issues

I just looked and I get the same thing in the official releases, so there's 
probably a library that needs to be updated. The ideal solution would be to just 
rebuild all the libs and target the same version of the CRT (4053 or whatever 
the new version is that was sneak-released a couple of days ago, grr). Several 
of them are fairly old, too.

Did you resolve your issue with getting a build that runs?

msvcr80.dll and
>msvcp80.dll, both have version 8.0.50727.4053.  There is no
>.exe.config file in the directory, or Microsoft.VC80.CRT.manifest

The manifest is supposed to go along with the crt dlls. At least, that's the 
intent. Windows voodoo, there.


If you're still getting a runtime error, my suggestions:

- Check the Event Viewer. That'll have more information on what version of the 
CRT it's trying to find but failing at. 

- Use NickyP's Visual Studio 2010 changes he linked above. This might be more 
difficult, but his branch will be merged in for 1.4 anyway. 
- Uninstall then reinstall .NET. Sometimes this'll fix conflicts with the WinSxS 
- Google the error message. There could be a fix out there none of us on this 
list have a clue about. 

Let us know how it's going. Cheers!

-- MC

On Sun, Apr 17, 2011 at 7:32 PM, <chris-tuchs at hushmail.com> wrote:

I got the exp branch of the github repository imprudence /
>imprudence (using git://github.com/imprudence/imprudence.git)
>Set my path and ran develop.py like
>python develop.py -G VC80 configure -DPACKAGE:BOOL=OFF
>As expected it dies soon after creating/editing the .sln file.
>Then I used the Microsoft Visual C++ 2005 Express Edition to
>choose "release" and then build > build solution.  Some time
>later it finished.  I looked inside imprudence-bin.exe and found
><assembly xmlns="urn:schemas-microsoft-com:asm.v1"
> <dependency>
>   <dependentAssembly>
>     <assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
>version="8.0.50727.4053" processorArchitecture="x86"
>   </dependentAssembly>
> </dependency>
> <dependency>
>   <dependentAssembly>
>     <assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
>version="8.0.50727.762" processorArchitecture="x86"
>   </dependentAssembly>
> </dependency>
>So either it's a bug common to both forks, or special to my
>machine/setup.  I still am using the edited crtassem.h.  I'm not
>married to the VC I'm using.  If there's another free tool I can
>use that I might have beter results with (win xp pro for the
>'os') I'd be willing to switch.
>Thanks again for all your patience and help!
>On Sun, 17 Apr 2011 15:55:16 -0700 chris-tuchs at hushmail.com wrote:
>>Good-news bad-news.
>>Good:  I was able to make a "zip" of a directory that runs.
>>Bad:  The .exe still claims to need both ...762 and ...4053
>>versions of MSVC.  Haven't tried setting up to "package" yet.
>>I tried changing crtassem.h, was obvious which line to change.
>>Didn't make a difference.  Got a fresh copy from the git repo.
>>Will try again later with a fork/clone from the official 1.4 exp
>>branch.  See if there's some breakage on Onefangs fork, or if it's
>>the real state of things in impy-land.
>>Thanks again for all your help.  Any ideas on why two different
>>version of MSVC are described in the .exe, or how to make it pick
>>one, I'd love to hear it!
>>On Sun, 17 Apr 2011 05:24:54 -0700 Nicky Perian
>><nickyperian at yahoo.com> wrote:
>>>>>name="Microsoft.VC80.CRT" version="8.0.50727.762"
>>>>>name="Microsoft.VC80.CRT" version="8.0.50727.4053"
>>>1. Microsoft issued an windows update to CRT this past week and
>>>now 5592 is also
>>>in the mix.
>>>2.Hold off doing that if you can.
>>>3. C:\<your path>\VC\include\crtassem.h around line 23 change 762
>>>to 4053
>>>4.If you want more adventure move to VS2010. Instructions are
>>>5.This is very much a work in progress and I would like to know
>>>it works on
>>>other than my machine.
>>>From: "chris-tuchs at hushmail.com" <chris-tuchs at hushmail.com>
>>>To: hakushakukun at gmail.com
>>>Cc: impdev at lists.imprudenceviewer.org
>>>Sent: Sun, April 17, 2011 1:04:32 AM
>>>Subject: Re: [impdev] Windows build issues
>>>After a painful day of experiments using the redmond-wimp system
>>>(aka Microsoft Windows), I have been able to make meta-impy-
>>>that in the embeded manifest list dependencies on both
>>>>>1. Microsoft issued an windows update to CRT this past week and
>>>now 5592 is also
>>>>>in the mix.
>>>>>2.Hold off doing that if you can.
>>>>>3. C:\<your path>\VC\include\crtassem.h around line 23 change
>>>762 to 4053
>>>>>4.Maybe you want more adventure moe to VS2010. Instructions are
>>>name="Microsoft.VC80.CRT" version="8.0.50727.762"
>>>name="Microsoft.VC80.CRT" version="8.0.50727.4053"
>>>I naturally tried building with each (a matched set of
>>>Microsoft.VC80.CRT.manifest, and the dll's that go with it
>>>msvcp80.dll, msvcr80.dll).  But the result is the same: after
>>>installing, the binary won't run.
>>>It looks like there are a number of dll's that require .4053, but
>>>(unless it's the wonderful-wimp-compiler Microsoft Visual C++
>>>Express Edition) I can't find how the .exe is getting
>>>on both.  I changed every place I could find to one state or the
>>>other (762 or 4053) but it makes no difference.
>>>ImpDev mailing list
>>>ImpDev at lists.imprudenceviewer.org
>>ImpDev mailing list
>>ImpDev at lists.imprudenceviewer.org

"Work is love made visible." — Kahlil Gibran

"We will not walk in fear, one of another. We will not be driven by fear into an 
age of unreason if we dig deep in our history and doctrine and remember that we 
are not descended from fearful men, not from men who feared to write, to speak, 
to associate and to defend causes which were for the moment unpopular. We can 
deny our heritage and our history, but we cannot escape responsibility for the 
result. There is no way for a citizen of the Republic to abdicate his 
responsibility." -- Edward R. Murrow, March 9, 1954
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.imprudenceviewer.org/pipermail/impdev-imprudenceviewer.org/attachments/20110420/c8172009/attachment-0002.htm>

More information about the ImpDev mailing list