Ok, I think you just put the "missing line" on a plate for me.....
I have done a bit of C++, but find that for my causal use I forget more in
between sessions than I remember. That's why I stick to VB, the opposite is
true, I remember more than I forget and so can make forward progress.
Hence I don't think I would be a very productive developer unless I spent
every spare moment developing ( do I need to spell out what my partner would
say about that!!!) :-)
Still, I can find my way through C++ code and might be able to provide more
vaulable input to those that can develop solutions. But,as you say unless
I'm prepared to fork out for VS C++ i'm left with learning a new compiler...
and I gather there are windows based open source alternatives to VS C++
thanks for your time
Dene
From: [EMAIL PROTECTED]
Reply-To: FlightGear user discussions <flightgear-users@flightgear.org>
To: "FlightGear user discussions" <flightgear-users@flightgear.org>
Subject: Re: [Flightgear-users] Windows FGv9.9 and FGTools - CVS
-WIN32 Compiling
Date: Fri, 25 Nov 2005 05:13:01 +0000
> I'm quite familiar with the concept of compling having a history of
writing
> programs and compiling in Fortran (Portran), Turbo Pascal and most
recently
> Visual Basic 6.
>
> In particular, I like Visual Studios IDE (Integrated Development
> Environment) having used it for VB6.
>
> The missing link seems to be from CVS to C++ source code.
CVS is not a programming language; you don't convert CVS anything to
C++ source code. CVS is a software application, used in a client-server
fashion (i.e. there's a CVS server, and users interact with the CVS
server by running their own CVS client programs . . .sorta like how
you use a web browser (the client) to interact with webservers).
What CVS is used for is to archive/store source code, and in particular
keep track of all the changes that have been made to that source code.
Developers use CVS to manage all the source code for a particular
project: people can "check out" a copy of the source code, build
executables from it, run it, make changes, build it, run it, make
changes, etc., and when they're done, submit their changes back to
the server. CVS makes managing the code and its versions/changes
easy (well, easier, anyway); it also helps handle situations such
as when two people are working on the same chunk of code at the
same time, and want to submit changes to a file that don't
necessarily mesh well.
When people talk about building FlightGear from CVS, what that means
is using a CVS client (for example, if you're on Windows, you can
use WinCVS) to check out a copy of the FlightGear project from the
FlightGear CVS server. Once you've done that, you have a source
tree for FlightGear -- a bunch of directories/folders, subdirectories,
etc., all full of the C++ source code files that FlightGear is built
from. You can then proceed to build the FlightGear executable
from that CVS version of the source code using whatever C++ compiler
you have; the actual details of building FGFS depends upon OS/setup,
and I'm not a Windows person so I'd have to stop here.
-c
_______________________________________________
Flightgear-users mailing list
Flightgear-users@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
_________________________________________________________________
Find the coolest online games @ http://xtramsn.co.nz/gaming
_______________________________________________
Flightgear-users mailing list
Flightgear-users@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
