skaller wrote:
The key thing for the building portability is that the C and C++
compilers are represented by Python classes. There is a pre-programmed
class for gcc, and another for MSVC++.
I suggest (for GHC) a Haskell class with instances for the different
combinations of
compilers and
each sub-project...have a...Haskell program...building that sub-project
I was trying to build something like this recently but hit a roadblock.
Rather than execute the script in each directory, I wanted to import it as a
module instead. This way you can, for example, pass functions, like a
On Fri, 2007-06-22 at 02:06 +0100, Brian Hulley wrote:
skaller wrote:
(a) Pick a portable scripting language which is readily available
on all platforms. I chose Python. Perl would also do.
If I had time to look into improving the GHC build system I'd definitely
use Haskell as the
Brian Hulley wrote:
To port GHC to a completely new platform, you'd of course need a
Haskell
compiler or interpreter already. However to bootstrap the process
only a
slow interpreter would be needed so as long as a portable pre-built
bytecode version was available for download the only thing
