Re: [Chicken-hackers] CMake vs. Autoconf

[Ivan Raikov]

  No, I never tested the library in Windows command prompt or
MSVC. I like my POSIX conveniences too much. But of course, Chicken is
a vastly more complex program, so I am sure yours are perfectly
legitimate grievances. I was just curious to hear what problems people
have encountered, since I don't use Windows, and most likely never
will. 

      -Ivan


"Brandon J. Van Every" <address@hidden> writes:

>> I ported a fairly
>> complex distributed computing toolkit to MinGW last month, and the
>> only GNU-related problem I saw was that libtool somehow gets confused
>> when the source directory includes spaces (like "Documents and
>> Settings"). In fact, I was pleasantly surprised how painless things
>> were.
>>
>
> "The only?"  That kind of whitespace problem consumed a few months of
> our time, and I'm still not certain the beast is slain.  Handling
> different pathname conventions on different shells is a nightmare.
> I'm curious, did your project also handle straight Windows Command
> Prompt?  or MSVC builds?  If you stay in a Unix-insulated universe
> where pathnames are always forward slash, your job is a helluva lot
> easier.
>
> I've also had problems with MSYS's support of Autoconf.  At times,
> that has sucked as well.  Enough that I dumped the standard MSYS
> package and went with mingw-install.
> http://sourceforge.net/projects/mingw-install
>
>
> Cheers,
> Brandon Van Every