[M3devel] Dependency on msvcr80.dll

Jay K jay.krell at cornell.edu
Tue Jul 28 09:28:54 CEST 2009


(and I opened a Trac ticket too)




----------------------------------------
> From: jay.krell at cornell.edu
> To: lists at darko.org
> CC: m3devel at elegosoft.com
> Subject: RE: Dependency on msvcr80.dll
> Date: Tue, 28 Jul 2009 07:28:25 +0000
>
>
> This is a problem I found and reported here last week.
>
>
> Until otherwise figured out, we have to provide a build per supported toolset/runtime.
> It is built into the binaries/libraries, it is their dependencies.
>
>
> I don't fully understand what is going on.
>
>
> Just because m3core.dll uses a particular .dll, does not foist that direct dependency on its users. However if you want to get malloced pointer from it and then free it, or an fopen FILE* from it and fread/fclose it, then you do have to agree.
>
>
> malloc is very easy to do without, and besides, most/all of this stuff is wrapped up -- you know, if you call UntracedHeapAllocate (whatever it is called) you can't then call free, you have to call UntracedHeapFree (whatever it is called)
>
>
> - Jay
>
>
>
> ----------------------------------------
>> From: lists at darko.org
>> To: jay.krell at cornell.edu
>> Subject: Dependency on msvcr80.dll
>> Date: Tue, 28 Jul 2009 09:24:38 +0200
>> CC: m3devel at elegosoft.com
>>
>> After intalling the latest VC++ Express which is 2008 or version 9 and
>> building with your min distribution I found it was dependent on
>> msvcr80.dll. Is this hard coded somewhere - should it use the
>> msvcr90.dll? Is there a correct way to resolve it?
>>
>> Cheers,
>> Darko.
>>


More information about the M3devel mailing list