g++ -o ./bin/executable -lLibrary1 -lLibrary2 `ls ./src/*.cpp`Quote:Original post by ChaosenemyThat command will recompile everything every time you run it no matter what. make checks the dependencies and only rebuilds things that are out of date.
In pretty much any source package I've downloaded, there is a Makefile. I've looked at a few and they're big, bloated, and ugly to look at. I couldn't imagine writing one. Is there some advantage to them over compiling straight from the command line? The way I do it is this:
My project directory has a "bin" and "src" folder and a compile script for each operating system the source code supports. The compile script for Linux, for instance, would be something like this:g++ -o ./bin/executable -lLibrary1 -lLibrary2 `ls ./src/*.cpp`
That simple 1-line script will compile every .cpp in the src folder with the specified libraries and spit out the executable into the bin folder. I don't really understand how a Makefile would be needed.
Any insight?
Quote:Original post by Chaosenemy
Thanks for the quick answer. I suppose I understand somewhat, but for the time being I guess I'm going to stick with my method. As it is, my current project only takes about 10 seconds to compile anyways.
Quote:Original post by Sirisian
One thing I tend to do (which might not be normal) is to place my unit tests directly into the makefiles so that they run after make is ran. They spit out errors if a change between builds breaks a test. Makes things more automatic.
