Creating separate make file fro gc_gec

[Senaka Fernando <se...@gmail.com>]

Hi all,

Currently, the makefile for gc_gen is located inside the drlvm/trunk/make/vm
folder. However, in the process of making gc_gen an independent entity,
isn't it better that we move this to drlvm/trunk/vm/gc_gen/make and refer it
from, drlvm/trunk/make/vm/gc_gen.xml? Thoughts?

Regards,
Senaka

Re: Creating separate make file fro gc_gec

[Alexei Fedotov <al...@gmail.com>]

Hello Senaka,

This is a natural approach to start thinking of an automatic build at
the beginning of the big project. You might notice a patch of your
predecessor to the Parrot build system which was originated from the
same activity. The only problem is that infrastructure would take
several weeks of your precious time and won't give you anything for
task completion.

I suggest reusing current build system and avoid moving any files. The
main problem of this build system is that it compiles a lot of stuff
you don't need, and this should be just deleted from build files and
your repository. The only infrastructure thing I would recommend you
to set up is a control version system because I do not see a natural
way of incremental development of your project using Harmony svn.

Just reduce a build time to 15 seconds and continue with Parrot / GC
bridge. You will face a real challenge there.

Thanks.


On Wed, Apr 2, 2008 at 9:41 PM, Senaka Fernando <se...@gmail.com> wrote:
> Hi all,
>
>  Currently, the makefile for gc_gen is located inside the drlvm/trunk/make/vm
>  folder. However, in the process of making gc_gen an independent entity,
>  isn't it better that we move this to drlvm/trunk/vm/gc_gen/make and refer it
>  from, drlvm/trunk/make/vm/gc_gen.xml? Thoughts?
>
>  Regards,
>  Senaka
>



-- 
With best regards,
Alexei

Re: Creating separate make file fro gc_gec

[Senaka Fernando <se...@gmail.com>]

Hi Alexey,

The interest is in making gc_gen an independent entity. The separate build
is simply a starting point. Yes, I'm aware of the VM <> GC interface. These
need to be better abstracted I guess.

Regards,
Senaka

On Thu, Apr 3, 2008 at 9:09 AM, Alexey Varlamov <al...@gmail.com>
wrote:

> 2008/4/3, Senaka Fernando <se...@gmail.com>:
> > Hi all,
> >
> > Currently, the makefile for gc_gen is located inside the
> drlvm/trunk/make/vm
> > folder. However, in the process of making gc_gen an independent entity,
> > isn't it better that we move this to drlvm/trunk/vm/gc_gen/make and
> refer it
> > from, drlvm/trunk/make/vm/gc_gen.xml? Thoughts?
>
> This would not make the gc_gen src tree truly self-sufficient, as the
> build still needs common properties/macros etc. Besides gc_gen
> includes few general headers of GC<>VM interface which you will need
> in some form anyway.
> However the build allows you independent making of gc_gen only (given
> you provided needed link dependencies), does it suites your needs?
> drlvm/trunk$ ant -f make/vm/gc_gen.xml
>
> --
> Alexey
> >
> > Regards,
> > Senaka
> >
>

Re: Creating separate make file fro gc_gec

[Alexey Varlamov <al...@gmail.com>]

2008/4/3, Senaka Fernando <se...@gmail.com>:
> Hi all,
>
> Currently, the makefile for gc_gen is located inside the drlvm/trunk/make/vm
> folder. However, in the process of making gc_gen an independent entity,
> isn't it better that we move this to drlvm/trunk/vm/gc_gen/make and refer it
> from, drlvm/trunk/make/vm/gc_gen.xml? Thoughts?

This would not make the gc_gen src tree truly self-sufficient, as the
build still needs common properties/macros etc. Besides gc_gen
includes few general headers of GC<>VM interface which you will need
in some form anyway.
However the build allows you independent making of gc_gen only (given
you provided needed link dependencies), does it suites your needs?
drlvm/trunk$ ant -f make/vm/gc_gen.xml

--
Alexey
>
> Regards,
> Senaka
>