On Thu, Sep 13, 2012 at 05:12:56AM -0700, Gabor Greif wrote: > > Btw., Ian is working in this area on the master branch so > there will be a bunch of conflicts anyway :-(
Sorry, I hadn't realised you were working on this in a branch. If merging your changes to master is possible (i.e. if they don't break the build, even if what they add isn't actually used yet) then I'd recommend doing that, to avoid conflicts. It's starting to feel like we're close to a full cross-compilation compiler, incidentally. I'm currently working on getting all the platform-specific values into a platformConstants file, which is read by the compiler at run-time. Once that's done, modulo a handful of bits of CPP etc that remain, it ought to be possible to make a single-platform cross-compiler simply by substituting the 'settings' and 'platformConstants' files with those from another platform. In reality, we'll probably find more places where "target = host" assumptions are getting baked in, but we'll have to deal with those when we come to them. The other half of the puzzle (perhaps what you're looking at) is altering the build system to be able to (a) generate 'settings' and 'platformConstants' files for platforms other than host, and (b) build for multiple platforms in a single tree. I suspect that (a) means getting rid of mkDerivedConstants, and using a configure script instead, but I haven't really thought about this half yet. Thanks Ian _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
