1 Sep 2005 01:13
RE: The Quest for the (More) Perfect Build Tool
Mark Wayland <Mwayland <at> torus.com.au>
2005-08-31 23:13:40 GMT
2005-08-31 23:13:40 GMT
> Our typical projects compile all of the files in specified > directories, so you can just create a new .cpp file in the > appropriate directory and the file will get compiled > automatically (no messing with .dsps or adding files to a > makefile). How did you set this up with JAM? As far as I could tell using my in-depth 1 day look at it (tongue in cheek) it doesn't do this out of the box - our makefile solution does exactly that using S_FILES := $(wildcard $(SRC_DIR)*.s) $(wildcard $(SRC_DIR)$(PLATFORM)/*.s) C_FILES := $(wildcard $(SRC_DIR)*.c) $(wildcard $(SRC_DIR)$(PLATFORM)/*.c) CPP_FILES := $(wildcard $(SRC_DIR)*.cpp) $(wildcard $(SRC_DIR)$(PLATFORM)/*.cpp) I also found that if I was to move over to JAM, I'd have to pretty much rewrite the jambase to support cross compiling for our multiple platforms and build targets. I've set up our makefile stuff to be modular to the point where a new project only requires a small, simple makefile which in turn includes our common build makefile stuff. I had to write my own dependency generator, as every single one on the web was broken in one form or another, but that wasn't too difficult. Regards,(Continue reading)
RSS Feed