On Monday 24 Feb 03, David A. Desrosiers writes:
> Stick with what works.. Do we really have users building Plucker in
> Cygwin? Or do they just convert it over to CodeWarrior and build there?
Once you decide what version of autoconf you need, just add
AC_PREREQ(?.??) accordingly. Platforms with multiple versions of
autoconf installed can (potentially) use the right one for the job.
Cygwin happens to be able to do this.
(Someone on the plucker-list thought Cygwin couldn't be used to build
Plucker because of autoconf bugs. Adding AC_PREREQ as I suggested
solves this problem.)
Now that prc-tools on Cygwin works "pretty well", I thought you guys
would welcome the (potentially) increased developer base.
To be honest, I am very surprised that there aren't more Cygwin folks
building Plucker. A lot of work has been done recently on prc-tools
and Cygwin that makes this viable.
Unfortunately, I just found a possible "showstopper" with a Cygwin
build. Because Windows is case-insensitive with filenames, gcc finds
plucker/viewer/font.h to satisfy
#include <Font.h>
instead of Core/System/Font.h from the SDK. This breaks the viewer
build, of course.
It should be straightforward to rename viewer/font.h to something like
viewer/pluckerfont.h and modify source accordingly. But who knows
what other naming (and other?) problems would yet remain for Cygwin.
Presumably this would also bite people who use CodeWarrior? Perhaps
there is nobody using that to build Plucker, either.
Kind regards,
David
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
