You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Alexei Fedotov <al...@gmail.com> on 2008/02/07 20:33:57 UTC

Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Alexey,

I have noticed the following line in your build:
working_vm/make/vm/common-vm.xml:            <syslibset libs="msvcrtd"
if="is.windows" unless="is.cfg.release"/>

>From the other side I have not noticed that this Microsoft library is
mentioned in working_*/make/depends.properties
How the build system may be able to produce a debug build which would
contain a debugging DLL version for those who don't have MSVC
installed?

Thanks.


On Feb 6, 2008 7:38 PM, Alexey Varlamov <al...@gmail.com> wrote:
> 2008/2/6, Mark Hindess <ma...@googlemail.com>:
>
> >
> > I was hoping Alexey might comment on this given his involvement in the
> > changes but I think it is a good idea to "fix" this now.  Unless anyone
> > complains I will take a look at doing it tomorrow.
> >
> > This will break builds and people will need to "svn switch" their
> > commond_resources tree (or remove it and re-populate it if you have
> > infinite bandwidth).
> >
> > Regards,
> >  Mark.
> >
> > ------- Forwarded Message
> >
> > From: Mark Hindess <ma...@googlemail.com>
> > To: dev@harmony.apache.org
> > Subject: Re: [announce] new DRLVM build system came into force
> > Date: Tue, 05 Feb 2008 09:20:50 +0000
> >
> > Excellent!
> >
> > Before we get too comfortable with the changes we might want to think
> > about whether:
> >
> >  https://svn.apache.org/repos/asf/harmony/enhanced/common_resources
> >
> > should really be moved to:
> >
> >  https://svn.apache.org/repos/asf/harmony/enhanced/common_resources/trunk
> >
> > We are going to want to be able to reproduce build so having the
> > capability to use branches and tags might be useful.  And it would
> > be more consistent with the layout of the other svn-switched
> > sub-directories of the federated build.
> >
> > I'll take a look at moving the dependencies in classlib to common_resources
> > but before I force everyone working on classlib to checkout common_resources
> > I'd like to get this resolved so we don't end up breaking it later.
>
> Sorry, here is somewhat belated recollection: it makes sense to modify
> the federated structure a bit further and make common_resources
> plugged as svn:externals rather than svn-switch it. This way we'd have
> the same versioning abilities plus can benefit reusing same
> properties.xml, svn info utilities, etc in the federated build.xml via
> direct import.
> If you did not yet finish with this, it is a good time to include the
> above change as well.
>
> Thanks,
> Alexey
>
>
> >
> > - -Mark.
> >
> > On 4 February 2008 at 16:51, "Alexey Varlamov" <al...@gmail.com>
> > wrote:
> > > Folks,
> > >
> > > The new build system for DRLVM is now the offical one, our integrity
> > > and snapshot CC systems were switched to it before this weekend.
> > > Currently there is certain duplication of resources between the new
> > > and old systems (property files, etc); I suggest we drop the old
> > > system in a week or two.
> > > Also, the old build directory encloses x-lists and MSVC solutions.
> > > X-lists apparently should be moved closer to test sources, but what
> > > about the solutions - just move them to working_vm/make? AFAIU they
> > > need update to changed deploy dir names, any volunteers?
> > > Meanwhile please be careful to update the right files, those in
> > > <working_vm>/make tree.
> > > I've updated GettingStarted page to reflect build changes, and will
> > > update README.txt soon. Hopefully the transition to unified build
> > > interface will be smooth for DRLVM developers.
> > >
> > > --
> > > Alexey
> > >
> >
> >
> > ------- End of Forwarded Message
> >
> >
> >
> >
> >
> >
>



-- 
With best regards,
Alexei

Re: Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Posted by Alexei Fedotov <al...@gmail.com>.
MSVC 2005 directory structure contains runtime DLLs under redist/
folder with no licenses are supplied. Debug DLLs are contained in
redist/Debug_NonRedist folder. :-)

On Feb 8, 2008 1:25 PM, Tim Ellison <t....@gmail.com> wrote:
> Gregory Shimansky wrote:
> > On 8 February 2008 Alexei Fedotov wrote:
> >> Gregory, thanks!
> >> Now I understand.
> >
> > Actually now that I think about it what I wrote is not true :(
> >
> > The free Express version available from MS is MSVC 2005. MSVC 2003 is not
> > available for free for quite a long time by now, so getting msvcr71d.dll is
> > possible only from internet mirrors that allow you to download any kind of
> > dll files but probably violate MS distribution policy.
> >
> > Harmony can be built using MSVC 2005 on win32 but it requires some hacking of
> > native code and build files. I used to "turn off" awt, swing, imageio, print
> > and some other class library modules that use API marked as "deprecated" by
> > MS.
> >
> > As for using debug versions of binaries, the only way is to install commercial
> > version of MSVC 2003.
>
> It's been a while since I read the MSVC redist text, but I'm not
> convinced we are allowed to redistribute the debug versions.
>
> In addition, each new artifact we redistribute must be called out in our
> notices file.
>
> Regards,
> Tim
>
>
> >> On Feb 8, 2008 12:10 AM, Gregory Shimansky <gs...@apache.org> wrote:
> >>> On 7 February 2008 Alexei Fedotov wrote:
> >>>> During NCAI discussion Vasily Levchenko mentioned possible open source
> >>>> (?) integration with MS debugging tools. This hardly can be done
> >>>> without the basic debugging library.
> >>> Sure, you can install free MSVC.NET Express and then you'll have debug
> >>> runtime installed.
> >>>
> >>>> On Feb 7, 2008 11:30 PM, Gregory Shimansky <gs...@apache.org>
> > wrote:
> >>>>> On 7 February 2008 Alexei Fedotov wrote:
> >>>>>> Alexey,
> >>>>>>
> >>>>>> I have noticed the following line in your build:
> >>>>>> working_vm/make/vm/common-vm.xml:            <syslibset
> >>>>>> libs="msvcrtd" if="is.windows" unless="is.cfg.release"/>
> >>>>>>
> >>>>>> From the other side I have not noticed that this Microsoft library
> >>>>>> is mentioned in working_*/make/depends.properties
> >>>>>> How the build system may be able to produce a debug build which
> >>>>>> would contain a debugging DLL version for those who don't have MSVC
> >>>>>> installed?
> >>>>> AFAIK this library is not distributed separately from MSVC.NET
> >>>>> (Microsoft distributes only non-debug version of its runtime), so
> >>>>> MSVC presence is required.
> >
>



-- 
With best regards,
Alexei

Re: Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Posted by Tim Ellison <t....@gmail.com>.
Gregory Shimansky wrote:
> On 8 February 2008 Alexei Fedotov wrote:
>> Gregory, thanks!
>> Now I understand.
> 
> Actually now that I think about it what I wrote is not true :(
> 
> The free Express version available from MS is MSVC 2005. MSVC 2003 is not 
> available for free for quite a long time by now, so getting msvcr71d.dll is 
> possible only from internet mirrors that allow you to download any kind of 
> dll files but probably violate MS distribution policy.
> 
> Harmony can be built using MSVC 2005 on win32 but it requires some hacking of 
> native code and build files. I used to "turn off" awt, swing, imageio, print 
> and some other class library modules that use API marked as "deprecated" by 
> MS.
> 
> As for using debug versions of binaries, the only way is to install commercial 
> version of MSVC 2003.

It's been a while since I read the MSVC redist text, but I'm not 
convinced we are allowed to redistribute the debug versions.

In addition, each new artifact we redistribute must be called out in our 
notices file.

Regards,
Tim

>> On Feb 8, 2008 12:10 AM, Gregory Shimansky <gs...@apache.org> wrote:
>>> On 7 February 2008 Alexei Fedotov wrote:
>>>> During NCAI discussion Vasily Levchenko mentioned possible open source
>>>> (?) integration with MS debugging tools. This hardly can be done
>>>> without the basic debugging library.
>>> Sure, you can install free MSVC.NET Express and then you'll have debug
>>> runtime installed.
>>>
>>>> On Feb 7, 2008 11:30 PM, Gregory Shimansky <gs...@apache.org> 
> wrote:
>>>>> On 7 February 2008 Alexei Fedotov wrote:
>>>>>> Alexey,
>>>>>>
>>>>>> I have noticed the following line in your build:
>>>>>> working_vm/make/vm/common-vm.xml:            <syslibset
>>>>>> libs="msvcrtd" if="is.windows" unless="is.cfg.release"/>
>>>>>>
>>>>>> From the other side I have not noticed that this Microsoft library
>>>>>> is mentioned in working_*/make/depends.properties
>>>>>> How the build system may be able to produce a debug build which
>>>>>> would contain a debugging DLL version for those who don't have MSVC
>>>>>> installed?
>>>>> AFAIK this library is not distributed separately from MSVC.NET
>>>>> (Microsoft distributes only non-debug version of its runtime), so
>>>>> MSVC presence is required.
> 

Re: Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Posted by Gregory Shimansky <gs...@apache.org>.
On 8 February 2008 Alexei Fedotov wrote:
> Gregory, thanks!
> Now I understand.

Actually now that I think about it what I wrote is not true :(

The free Express version available from MS is MSVC 2005. MSVC 2003 is not 
available for free for quite a long time by now, so getting msvcr71d.dll is 
possible only from internet mirrors that allow you to download any kind of 
dll files but probably violate MS distribution policy.

Harmony can be built using MSVC 2005 on win32 but it requires some hacking of 
native code and build files. I used to "turn off" awt, swing, imageio, print 
and some other class library modules that use API marked as "deprecated" by 
MS.

As for using debug versions of binaries, the only way is to install commercial 
version of MSVC 2003.

> On Feb 8, 2008 12:10 AM, Gregory Shimansky <gs...@apache.org> wrote:
> > On 7 February 2008 Alexei Fedotov wrote:
> > > During NCAI discussion Vasily Levchenko mentioned possible open source
> > > (?) integration with MS debugging tools. This hardly can be done
> > > without the basic debugging library.
> >
> > Sure, you can install free MSVC.NET Express and then you'll have debug
> > runtime installed.
> >
> > > On Feb 7, 2008 11:30 PM, Gregory Shimansky <gs...@apache.org> 
wrote:
> > > > On 7 February 2008 Alexei Fedotov wrote:
> > > > > Alexey,
> > > > >
> > > > > I have noticed the following line in your build:
> > > > > working_vm/make/vm/common-vm.xml:            <syslibset
> > > > > libs="msvcrtd" if="is.windows" unless="is.cfg.release"/>
> > > > >
> > > > > From the other side I have not noticed that this Microsoft library
> > > > > is mentioned in working_*/make/depends.properties
> > > > > How the build system may be able to produce a debug build which
> > > > > would contain a debugging DLL version for those who don't have MSVC
> > > > > installed?
> > > >
> > > > AFAIK this library is not distributed separately from MSVC.NET
> > > > (Microsoft distributes only non-debug version of its runtime), so
> > > > MSVC presence is required.

-- 
Gregory

Re: Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Posted by Alexei Fedotov <al...@gmail.com>.
Gregory, thanks!
Now I understand.

On Feb 8, 2008 12:10 AM, Gregory Shimansky <gs...@apache.org> wrote:
> On 7 February 2008 Alexei Fedotov wrote:
> > During NCAI discussion Vasily Levchenko mentioned possible open source
> > (?) integration with MS debugging tools. This hardly can be done
> > without the basic debugging library.
>
> Sure, you can install free MSVC.NET Express and then you'll have debug runtime
> installed.
>
> > On Feb 7, 2008 11:30 PM, Gregory Shimansky <gs...@apache.org> wrote:
>
> > > On 7 February 2008 Alexei Fedotov wrote:
> > > > Alexey,
> > > >
> > > > I have noticed the following line in your build:
> > > > working_vm/make/vm/common-vm.xml:            <syslibset libs="msvcrtd"
> > > > if="is.windows" unless="is.cfg.release"/>
> > > >
> > > > From the other side I have not noticed that this Microsoft library is
> > > > mentioned in working_*/make/depends.properties
> > > > How the build system may be able to produce a debug build which would
> > > > contain a debugging DLL version for those who don't have MSVC
> > > > installed?
> > >
> > > AFAIK this library is not distributed separately from MSVC.NET (Microsoft
> > > distributes only non-debug version of its runtime), so MSVC presence is
> > > required.
>
> --
> Gregory
>



-- 
With best regards,
Alexei

Re: Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Posted by Gregory Shimansky <gs...@apache.org>.
On 7 February 2008 Alexei Fedotov wrote:
> During NCAI discussion Vasily Levchenko mentioned possible open source
> (?) integration with MS debugging tools. This hardly can be done
> without the basic debugging library.

Sure, you can install free MSVC.NET Express and then you'll have debug runtime 
installed.

> On Feb 7, 2008 11:30 PM, Gregory Shimansky <gs...@apache.org> wrote:
> > On 7 February 2008 Alexei Fedotov wrote:
> > > Alexey,
> > >
> > > I have noticed the following line in your build:
> > > working_vm/make/vm/common-vm.xml:            <syslibset libs="msvcrtd"
> > > if="is.windows" unless="is.cfg.release"/>
> > >
> > > From the other side I have not noticed that this Microsoft library is
> > > mentioned in working_*/make/depends.properties
> > > How the build system may be able to produce a debug build which would
> > > contain a debugging DLL version for those who don't have MSVC
> > > installed?
> >
> > AFAIK this library is not distributed separately from MSVC.NET (Microsoft
> > distributes only non-debug version of its runtime), so MSVC presence is
> > required.

-- 
Gregory

Re: Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Posted by Alexei Fedotov <al...@gmail.com>.
During NCAI discussion Vasily Levchenko mentioned possible open source
(?) integration with MS debugging tools. This hardly can be done
without the basic debugging library.


On Feb 7, 2008 11:30 PM, Gregory Shimansky <gs...@apache.org> wrote:
> On 7 февраля 2008 Alexei Fedotov wrote:
> > Alexey,
> >
> > I have noticed the following line in your build:
> > working_vm/make/vm/common-vm.xml:            <syslibset libs="msvcrtd"
> > if="is.windows" unless="is.cfg.release"/>
> >
> > From the other side I have not noticed that this Microsoft library is
> > mentioned in working_*/make/depends.properties
> > How the build system may be able to produce a debug build which would
> > contain a debugging DLL version for those who don't have MSVC
> > installed?
>
> AFAIK this library is not distributed separately from MSVC.NET (Microsoft
> distributes only non-debug version of its runtime), so MSVC presence is
> required.
>
> --
> Gregory
>



-- 
With best regards,
Alexei

Re: Where could msvcr71d.dll appear from? Was: Breaking the build again (was Re: [announce] new DRLVM build system came into force)

Posted by Gregory Shimansky <gs...@apache.org>.
On 7 февраля 2008 Alexei Fedotov wrote:
> Alexey,
>
> I have noticed the following line in your build:
> working_vm/make/vm/common-vm.xml:            <syslibset libs="msvcrtd"
> if="is.windows" unless="is.cfg.release"/>
>
> From the other side I have not noticed that this Microsoft library is
> mentioned in working_*/make/depends.properties
> How the build system may be able to produce a debug build which would
> contain a debugging DLL version for those who don't have MSVC
> installed?

AFAIK this library is not distributed separately from MSVC.NET (Microsoft 
distributes only non-debug version of its runtime), so MSVC presence is 
required.

-- 
Gregory