> > > > 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.
Whatever -- the point is that rewriting and reinvention of the wheel for the
single purpose that it is more convenient to have it included in wine is a
bit silly. We require a C compiler (for now we require gcc with is OK IMO),
we require a make program (don't know if gmake is required though), perl,
yacc, lex, etc. It would be simply silly to reimplement all this programs
simply because some systems don't have them. They are free on the net,
download them.
Also, whether requiring GNU cpp is reasonable or not is another rather
artificial question. It is just a tool. It is similar but not identical to
the standard cpp. So, if we require one of its particular features, than we
require a different tool from the standard cpp. Call it a different name if
that helps you. Just as we require perl. So, you are not going to suggest
that we do the perl stuff in cpp (I hope). In other words, I don't see what
your problem is, if we were to require GNU cpp. Fortunately, standard cpp
seems to be enough, but if we were to require GNU cpp, what would be the
(real) problem???
Dimi.
