[M3devel] Dependency on msvcr80.dll

[Darko Volaric]

I think the latestest will suffice, since it sounds pretty easy to  
derive any other version from that one, and the latest VC version is  
freely available. The other compilers I wouldn't worry about since  
users probably don't exist, and if they do then they can use those  
products pretty easily with the VC command line tools. I use  
Metrowerks for instance (on the Mac) and have hacked a plugin that  
does most of what I want.

Anyway, I'd hate to keep you from the much more interesting  
ARM_DARWIN :-)


On 29/07/2009, at 5:16 AM, Jay K wrote:

>
> The compiler isn't relevant.
> The libraries are.
> You might as well consider them as one indivisable unit, but they  
> aren't quite.
> I don't yet fully understand the situation.
> Until/unless I/we do, we'll build a distribution per VC version. I  
> should have renamed the below
> cm3-min-NT386-d5.8.2-vc90.zip or such but I was lazy and took  
> advantage of there being no other 5.8.2 currently.
>
>
> Stay tuned (but don't hold your breath) for
> cm3-min-NT386-d5.8.2-vc80.zip
>
>
> and speak up as to which, IF ANY, of these is desired:
>
> cm3-min-NT386-d5.8.2-vc71.zip
> cm3-min-NT386-d5.8.2-vc70.zip
> cm3-min-NT386-d5.8.2-vc60.zip
> cm3-min-NT386-d5.8.2-vc50.zip
> cm3-min-NT386-d5.8.2-vc42.zip
> cm3-min-NT386-d5.8.2-vc41.zip
> cm3-min-NT386-d5.8.2-vc40.zip
> cm3-min-NT386-d5.8.2-vc20.zip
> (I haven't yet acquired the 32bit 1.0 version, but all the others  
> have been tested surprisingly recently.)
>
>
> For that matter, among:
>  Borland 5.5 (free "beer")
>  Metrowerks 6, 7, 8
>  Digital Mars (free "beer")
>  Open Watcom (free and open source)
>
> speak up as to which, IF ANY, are desired, and what to call the  
> target.
> My experiment to call everything NT386 I've decided was a failure.
> I'll fix that in the next release.
> I386_NT_DIGITALMARS, I386_NT_WATCOM, I386_NT_CODEWARRIOR,  
> I386_NT_BORLAND ?
> I386_NT_DMARS, I386_NT_WAT, I386_CW I386_NT_MWCW, I386_NT_BOR???
> Borland seems to still be under development but current versions are  
> expensive.
>
> I guess I should learn the jmpbuf size of all of those and see if  
> everyone is close and if so use the largest of them. Then it's  
> simply a matter of ensuring we use C wrappers enough (probably  
> already do), and getting the compiler/linker switches reasonable on  
> the config files.
>
>
> - Jay
>
>
>
> ----------------------------------------
>> From: lists at darko.org
>> To: jay.krell at cornell.edu
>> Date: Wed, 29 Jul 2009 04:33:03 +0200
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] Dependency on msvcr80.dll
>>
>> Yep, they work. Can you only use the version of VC that the compiler
>> was built with?
>>
>>
>> On 28/07/2009, at 2:07 PM, Jay K wrote:
>>
>>>
>>> Try these that I just made?
>>>
>>> They were built with VC 9.0:
>>>
>>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-NT386-d5.8.2.zip
>>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-NT386-d5.8.2.zip
>>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-NT386-d5.8.2.msi
>>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-NT386-d5.8.2.msi
>>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-min-NT386-d5.8.2-symbols.zip
>>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-std-NT386-d5.8.2-symbols.zip
>>>
>>> I didn't test them (too much combinatorial explosion -- four things
>>> to test!)
>>>
>>> and the readme from before:
>>>
>>> http://modula3.elegosoft.com/cm3/uploaded-archives/cm3-NT386-msi.txt
>>>
>>> Olaf, there is a LOT more in the snaps directory than the snapshot-
>>> index lists.
>>> A lot. Also my archives contain more of the licenses, so many that I
>>> put them in a subdirectory.
>>>
>>>
>>> - Jay
>>