On 6/24/06, Andrey Chernyshev <[EMAIL PROTECTED]> wrote:
> > I wanted to add that patching ant with cpptasks as it is done today should
not
> > be allowed since system wide installations are usually write protected.
>
> :)
>
> Note that when we're finished, DRLVM shouldn't do anything to the
> filesystem outside of harmony/enhanced/drlvm/trunk
I guess it currently doesn't, cpptasks were patched in the
drlvm\trunk\build\make\tmp\cpptasks directory so far and then
prepended to the Ant classpath.
Anyways, the command line length limitation for dev studio compiler
seems to be resolved in the latest cpptasks package (was cctask bug
#1402730), I've checked the Windows build works with cpptasks-1.0b4
without patching.
If anyone interested, I can work out a patch which removes the
cpptasks patching from the build.
I've added a patch in HARMONY-697 which removes the cpptasks patching
from the drlvm build.
Thanks,
Andrey.
Thanks,
Andrey.
On 6/23/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
>
>
> Gregory Shimansky wrote:
> > On Friday 23 June 2006 02:18 Geir Magnusson Jr wrote:
> >>>> We would be able to do it if really necessary, but I'd rather avoid if
> >>>> we can. I do think that the current DRLVM shows that it can be avoided
> >>>> (so we have a way for people to get started) as well as the
> >>>> flexibility for people who want the control.
> >>>>
> >>> >From the Gentoo user standpoint who can just type
> >>>
> >>> emerge ant cpptasks eclipse log4cxx apr icu icu4j
> >>>
> >>> and get all the dependencies installed in the system I wholeheartedly
> >>> support the way for build just to point to locations of already installed
> >>> binaries.
> >> Exactly.
> >
> > I wanted to add that patching ant with cpptasks as it is done today should
not
> > be allowed since system wide installations are usually write protected.
>
> :)
>
> Note that when we're finished, DRLVM shouldn't do anything to the
> filesystem outside of harmony/enhanced/drlvm/trunk
>
> >
> >>> After all it is the way all other software actually installs on Linux.
> >>> Yes for windows maybe we'll need binaries kept somewhere in a shed.
> >> Nah :)
> >
> > Ok a set of URLs probably should be enough. Since there is no package
manager
> > in windows every library has to be downloaded somehow. But I just don't know
> > off top of my head where to get log4cxx or apr libraries for windows and
> > googling doesn't give any easy answer.
>
> We'll provide that in our developer docs. There are no APR binaries for
> windows (or anything else for that matter).
>
> The assumption is that if you are going to build harmony, you'll have
> the tools installed to build the deps if need be. If not, we offer
> build snapshots.
>
> geir
>
> >
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Andrey Chernyshev
Intel Middleware Products Division
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
