Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-09 Thread Ross Golder
.cvspass is for remembering pserver passwords (SourceForge anonymous access). As John needs developer access he is using the ext method, which is designed to use rsh/ssh. John, list the contents of one of your CVS/Root files. This will show what repository the working directory is set up to. --

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-08 Thread Curtis L. Olson
CVS remembers your passwords after the first time you enter it. Look for ~/.cvspass and you'll see what it does. Curt. John Wojnaroski writes: > > You need to check out the your copy from the SF repository as your SF > > user ID, not anonymously. It sounds like that is what you did. > > > > >

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-08 Thread John Wojnaroski
> You need to check out the your copy from the SF repository as your SF > user ID, not anonymously. It sounds like that is what you did. > > > > > $ export CVS_RSH=ssh > > $ cvs -z3:ext:[EMAIL PROTECTED]:/cvs/opengc/ co opengc > > > > cvs server: Updat

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-08 Thread Ross Golder
On Sat, 2001-12-08 at 23:42, Curtis L. Olson wrote: > > Ross: quick question > > using the makefile.am in opengc you created I get the following > > > > make[1] *** no rule to make target 'opengc_LDFLAGS', needed by 'opengc". > > Stop. > > > > Is something missing in configure.in? Looks very si

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-08 Thread Curtis L. Olson
John, You need to check out the your copy from the SF repository as your SF user ID, not anonymously. It sounds like that is what you did. Regards, Curt. John Wojnaroski writes: > > > > > The source tree on opengc.org currently only builds on windows. We've > had > > > > some problems convi

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-08 Thread John Wojnaroski
> > > The source tree on opengc.org currently only builds on windows. We've had > > > some problems convincing John W's CVS to talk to SourceForge, which is why > > > there are currently two versions of the code (kingmont and sourceforge). > > So John W's CVS problem caused this? We probably ough

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-08 Thread Ross Golder
On Sat, 2001-12-08 at 01:49, John Wojnaroski wrote: > > > > The source tree on opengc.org currently only builds on windows. We've had > > some problems convincing John W's CVS to talk to SourceForge, which is why > > there are currently two versions of the code (kingmont and sourceforge). So Jo

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-07 Thread John Wojnaroski
> Hehe, you are just discovering that this open-source project > management stuff isn't as easy as it looks. :-) it really is kind of addictive, though and sometimes frustrating. like pushing on rope. but then the pay is great :-) Thank you for your interest and counsel Regards John W. _

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-07 Thread Curtis L. Olson
John Wojnaroski writes: > Just to add a little more confusion > > Boy, this is turning into a real bad mess. > > The unix source on kingmont builds with the freetype 1.3 and gltt and should > work with the latest version of FG from the CVS, but the displays are > minimal, just the PFD stuf

Re: [Flightgear-devel] Starting up flightgear with Opengc

2001-12-07 Thread John Check
You guys do what you gotta do. I have plenty to keep me occupied On Friday 07 December 2001 8:49 pm, you wrote: > > The source tree on opengc.org currently only builds on windows. We've had > > some problems convincing John W's CVS to talk to SourceForge, which is > > why there are currently two

[Flightgear-devel] Starting up flightgear with Opengc

2001-12-07 Thread John Wojnaroski
> The source tree on opengc.org currently only builds on windows. We've had > some problems convincing John W's CVS to talk to SourceForge, which is why > there are currently two versions of the code (kingmont and sourceforge). The > autoconf scripts included in the SourceForge version are out-o