|
From: Ray K. <ray...@my...> - 2004-04-01 08:10:23
|
On 01 Apr 2004, A. Klingenstein wrote: > > Dr Groovenstein wrote: > >> >> Ok, this is helping, thanks for the info. Now, this is definitely a g= cc >> type package, which came in .tgz format. So, I untar it, and everythi= ng >> is in this complex directory structure. The "package" came with a >> configurator script, which I guess generates a makefile depending on t= he >> system the software is compiled on. Anyway, normally under linux, you >> would do a "make configure", "make ode-lib" etc... So, how do you do >> all of this with Dev-C++? Or, should I be using cygwin instead? Is >> there a way to recursively add files to a project, or do I have to pic= k >> them manually out of all those directories? >> > > YOu don't compile them with dev-cpp, instead you use either mingw's MSY= S > or maybe even cygwin. Dev-C++ is for developing new stuff, not for > compiling already written things. After that, you put the resulting > libraries where either windows or dev-cpp or both can find it, dependin= g > what you want to do with them. To expand upon this: The compiler Dev-C++ comes with and uses is the MinG= W port of gcc. It can be found in the dev-cpp/bin directory normally and c= an be used from the command line just like normal. MSYS is a collection of other MinGW ports that might be necessary to run a makefile. It can be=20 found at http://www.mingw.org/msys.shtml One other point, regarding whether or not you need to start a project to compile: if you're just compiling one file (and don't need to call the=20 linker) and if it doesn't take any special command line options, just gcc foo -o=20 bar, you can just create a single file and compile that. If you would need mo= re than one simple command line to compile it, you'll probably to make a=20 project. |