From: mert0407 AT sable DOT ox DOT ac DOT uk (George Foot) Newsgroups: comp.os.msdos.djgpp Subject: Re: Projects in RHIDE Date: 12 Mar 1997 20:16:38 GMT Organization: Oxford University, England Lines: 33 Message-ID: <5g72v6$ek7@news.ox.ac.uk> References: <01bc2eb4$85634e00$bcae71a5 AT mod DOT exo DOT com> NNTP-Posting-Host: sable.ox.ac.uk To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp MoD (mod AT exo DOT com) wrote: : can sumone please explain the "PROJECTS" idea to me for djgpp.. i mean.. i : want to save my options but it opens up a project thingie and wont let me : run =) im trying to get a hang of the "C" jive... just taking it one setp : at a time ;) When you're developing anything other than quick, small utilities there are many benefits in having the source code in a number of separate files. A project in RHIDE is in a way a group of files which should be compiled and linked together to form the final executable - much like a makefile, if you know what that is. All you really need to know is this: when you're starting a new project, make a directory for it, cd into it and type 'rhide ' where is the name of the executable you want, without the '.exe' extension. You then create new .c or .cc files using File/New, and add them to the project using Project/Add File. To make the executable, you press F9 - this will only recompile files which have been modified. This is the main benefit of splitting a large project into many smaller files. If for some reason you need to ensure that everything is recompiled, selecting 'Build all' from the Compile menu will do this. I'm not sure where you'd find this sort of information in more detail; Gordon Dodrill's C tutorials mention it I think... check out: http://www.swcp.com/~dodrill/ (there's also a C++ tutorial which definitely mentions it in connection with distributing classes). -- George Foot Merton College, Oxford