> > > Why don't we simply use gcc preprocessor?
> >
> > Because not everybody uses/has gcc to compile wine...
>
> This is certainly NOT a reason:
> (1) who is compiling Wine with anything else? Can it be done?
I do. WineLib works fine with Solaris C.
Wine works for some applications using a gross hack
thunking layer because Solaris C lacks stdcall.
Eventually all application can be made to work I believe.
I haven't had much time working on it lately though.
That said autoconf detects a working (non-GNU) C preprocessor
even if using Solaris C.
It is a little more sensitive than the GNU C preprocessor,
it doesn't like lines ending with "\r\n" for example
but I can fix that it you decide to use it for wrc.
Further more it output a #ident line that wrc chokes on,
but I have a patch that fixes that.
The preprocessor on Solaris doesn't like the -x c option
used in wine/program/notepad however -xc is OK, which
is also supported by the GNU preprocessor (I check).
So using the C preprocesor detected by autoconf is OK for me.
I believe I can fix the problems that will occur on Solaris.
> (2) they may not have a Unix OS to run it for. This does not
> mean that we
> include a Unix like OS with Wine...:)
It will take a long time before we support non-Unix OS:es.
The porting attempt to almost Unix-like BeOS failed,
or are at least put on ice for now.
> cpp is standard. If we need GNU cpp, we just requre it. What
> is the big
> deal? If we want, we may bundle cpp with Wine just like we do
> with wrc. It
> would be silly though.
Using the C preprocessor detected by autoconf is OK IMHO,
requiring installing GNU cpp is not.
