Re: Yasm r1713 fixed; building and Windows-native

Peter Tanski wrote:
> On Dec 19, 2006, at 7:50 PM, Neil Mitchell wrote:
> 
>>> Have you looked into Bakefile or Interscript?  CMake looks more
>>> powerful than Bakefile, which ends up using nmake on Windows, while
>>> Interscript is really a literate programming language with the
>>> ability to execute scripts.  Interscript works very well for Felix
>>> but it is a bizarre system to work with.
>>
>>
>> No, haven't really looked at others than that. The original Yhc reason
>> for going to Scons was that KDE 4 is going to use it for all
>> platforms, including Windows. Since then, then dropped Scons and moved
>> to CMake - I am just playing follow the leader :)
> 
> 
> I am doing essentially the same thing trying to get a Windows build  
> together--trying to find a build system that:
> (1) makes changes easy;
> (2) encapsulates dependency searches for various operating systems  and 
> compiler settings for various compilers (gcc, CL); and,
> (3) manages different build types, including tests.
> 
> So far, (2) is the main concern for Windows.  My real worry is  Windows 
> Vista: the most recent reports I have seen show that mingw32  requires a 
> special runtime dll and Administrator privileges to run  while cygwin is 
> buggy.

I think you mean MSYS, not mingw.  There shoudn't be any difficulty with mingw 
on Vista, it's just a static library.


> The immediate problem GHC has is the CL  compiler--and, 
> probably, default front-end for the linker, depending  on the link 
> options required.  Unless someone wants to redo the  current Autotools 
> build system to use the CL compiler and promptly  discard it for a 
> Windows-native build, the best thing to do is  convert the build system 
> to one that will use the CL compiler  automatically.

I don't buy into changing the build system wholesale.  In fact, I suspect the 
build system hardly has to change at all: we can compile all .c files using GHC, 
so only GHC has to know how to invoke CL.

Cheers,
	Simon