Curt,
I sent an email to the MetaKit guys Sunday afternoon requesting help
resolving this problem. I have not received a response yet.
Is anyone willing to email me a copy of their cygwin MetaKit .a's and .h's?
Hoyt
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Curtis L.
Olson
Sent: Tuesday, February 26, 2002 8:03 AM
To: [EMAIL PROTECTED]
Subject: RE: [Flightgear-devel] (Newbee) Problems compiling MetaKit
Hoyt,
It might be worth asking the metakit people if they have any ideas.
It could be something simple, or could be that some cygwin
incompatibility has crept into their code? Another idea would be to
get someone who's already built metakit with cygwin to send you their
.a and .h's.
Regards,
Curt.
Hoyt A. Fleming writes:
> Erik,
>
> Thanks for the help! I configured MetaKit with the --without-tcl option
> and received the following error:
>
> Hoyt A. Fleming@HOYT'S_DESKTOP /usr/local/source/simgear/metakit/builds
> $ ../unix/configure --without-tcl
> checking for Python configuration... not enabled
> checking for Tcl headers... configure: error: no directory doesn't contain
> tcl.h
>
>
> Hoyt A. Fleming@HOYT'S_DESKTOP /usr/local/source/simgear/metakit/builds
> $
>
> Any ideas?
>
> Hoyt
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Erik Hofman
> Sent: Tuesday, February 26, 2002 3:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Flightgear-devel] (Newbee) Problems compiling MetaKit
>
>
> Hoyt A. Fleming wrote:
> > I am attempting to compile (version 2.4.2-32) MetaKit, which is
> > included in (version 0.0.17) Simgear. (I am utilizing cygwin to create
> > binaries on a PC.) The "../unix/configure" command appears to work
fine.
> > However, the "make" command creates the following error message:
> >
> > g++ -c -O2 -I../unix/../include -I/usr/include ../unix/../tcl/mk4tcl.cpp
> > -DDLL_
>
> I have to be carefull abot what I'm saying about metakit here but (;-))
> do you realy wan't the metakit tcl bindings? If not, the easies way is
> to configure it with the following option: --without-tcl
>
> I know it's not a fix, but it could get you going.
>
> Erik
>
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED]
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
