To automate the build process you use a makefile, which consists of a series of rules, listing a thing to create and the files needed to create it.
The actual library files would look something like libm.a or libm.so, you ignore the suffix and the 'lib' part of the filename when adding the linker flag. If you need to link in any external libraries you add them to this line, eg -lm for the math library. To link all the modules together requires running g++ hello.o hello-writer.o -o helloĬreating the program hello. The -c flag skips the linking for the moment. G++ -c hello-writer.cpp -o hello-writer.o The *.cpp files are converted to object files by g++, using the commands g++ -c hello.cpp -o hello.o You have 3 files, hello.cpp hello-writer.cpp and hello-writer.h, the contents being // hello-writer.h Let's say you want to write a simple 'hello world' application. (If it makes any difference, I am running Mac OS X, with gcc 4.0.1 and make 3.81) I would really like to know the what, how, and why of building C++. What I am looking for, is either an explanation, or link to a tutorial that explains, the workflow for a C++ project, from first writing the code up to running the produced executable. I know what the linker does, but not how to use it. I know what gcc does, but not how to use it. I know what Makefiles are, but not how to write them. The thing is, although IDEs do all this under the hood, making life very easy, I don't really know what is really happening, and feel that I need to get accustomed to building projects the "old fashioned way": from the command line, using the tool chain explicitly. I also know most projects also use make to streamline the process of compiling and linking multiple source and header files. I understand the process behind building a project: compile source to object code, then link them into an executable that is platform specific (. However, I have only built my projects with IDEs, including VS08 and QtCreator. I have been learning C++ in school to create small command-line programs.
0 kommentar(er)
