On 19.11.2010, at 16:17, Paul R wrote: > Demos are super yes, well chuffed, nice to have those examples. > > Regarding command line programming in general i have always thought > it would be a bit of a pain when using lots of files in a project > how does it work there? You type in a big line of them and then > that stays as a saved compile path for the duration of your development? > > Will the compiler still only build files where neccesary when no wholesale > changes are made?
That's what makefiles are for. You have a single command, "make", that read a file name "Makefile". That file contains a list of all other files that belong to your project and how they need to be treated to get the final result. "make" then compares the modification time of the intermediate and final results, and the source files, and rebuilds only those files that require a rebuild. It also has some lines that tell it if files depend on each other. If those dependencies are choosen well, the build process can be shortned a lot. Now that you have built FLTK successfuly, if you enter "make" again, almost no commands will be run - until you change some source code... . _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
