harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivanov, Alexey A" <alexey.a.iva...@intel.com>
Subject RE: [build] Downloading dependencies
Date Wed, 20 Dec 2006 11:02:58 GMT
>-----Original Message-----
>From: Geir Magnusson Jr. [mailto:geir@pobox.com]
>Sent: Wednesday, December 20, 2006 1:41 PM
>To: dev@harmony.apache.org
>Subject: Re: [build] Downloading dependencies
>Tim Ellison wrote:
>> Ivanov, Alexey A wrote:
>>> In default installation WinXP does not have this library in
>>> This library is installed by Visual Studio 2003 and may be installed
>>> other software which was compiled with Visual Studio 2003 (which is
>>> v7.1). Visual Studio 2002 (v7.0) has msvc70.dll, if I remember
>>> correctly.
>>> That is it may happen system lacks for this DLL. And Microsoft
>>> recommends avoiding copying DLLs to system32 when installing an
>>> application. Thus we better distribute this DLL in snapshots and
>>> releases because users may not have it.
>>> On the other hand, if a person has Microsoft compiler installed, the
>>> will most likely be in system32.
>>> That's it.
>> Agreed -- we were getting that DLL so we could distribute it to our
>> users who may not have the compiler installed.
>> If we think it is more reliable to grab the DLL from system32/ than
>> download it we can do that.  I guess we look for a env var to figure
>> where windows is installed...
>Ok - so we seem to be agreed that :
>1) We can't count on it being on a user's machine
>2) We don't need to download it because it will be part of the tool
>3) We need to then find it.
>Could we do something like
>    GetModuleFileName(LoadLibrary(....), buffer, size);

I guess it will work. But this should be in an application and the DLL
must be available in PATH so that LoadLibrary is able to load it.

I think it's easier just to copy it from system32 folder right from
build.xml. If a user is going to compile Harmony on Windows, they need
Microsoft compiler installed and thus they will have the DLL in

>to figure it out? 

Alexey A. Ivanov
Intel Enterprise Solutions Software Division

View raw message