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 <[EMAIL PROTECTED]> 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
