At 11:40 on 06/01/2003 +0200, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Yep. Imcc should definitely move out off languages into its own subdir > under the top level (Not in the top level itself). > > > ... Who should do > > this? I'd be willing to help if given direction. > > > Moving directories around in CVS is AFAIK a PITA. The last such > operation was done in the repository directly, IIRC.
Yes, that's certainly the way to go for the actual dir structure change. But first all the other little code changes that this would require need to be figured out.. I started looking at what makefile changes would be needed.. i think the first thing that really needs to be decided is whether we intend to use recursive makefiles or not. Right now, parrot is half and half, and that just isn't going to fly, long term. The problem is, if you're really going to do recursive makefiles without headaches, each makefile needs to be building a fairly self-sufficient module. And at the moment, if we were to build a libimcc or something like that and link it into parrot, it would in turn require libparrot to build. This creates a bit of a chicken/egg problem.. Not insurmountable, but certainly ugly. It would be somewhat less so if the library bits were in a separate directory from the programs, so that imcc and parrot would be able to pull in libparrot and libimcc without disaster. However, that said, I am not a tremendous fan of recursive makefiles (or of make in general, honestly). I would suggest that we may want to move towards either a non-recursive makefile system (see 'recursive make considered harmful', http://aegis.sourceforge.net/auug97.pdf.. i have doubts about how well this can work on a large scale project without something like gnu make though), or something else altogether (cons, for instance). Wow, That was a run-on sentence. I know there was some coding done a while back towards rolling our own make replacement, but I don't know what state it's in.. and rolling our own will slow things down a bit- best to spend our resources on writing parrot, not make, imho.. but i'm willing to go with whatever folks want to do. I'm willing to help out here- i can probably figure out how to link imcc into parrot, but I think we need to resolve these directory structure / build system issues first. Does anyone own this problem? --Josh
