SCons User Guide 0.96.90 | ||
---|---|---|
<<< Previous | Less Simple Things to Do With Builds | Next >>> |
It's common to re-use code by sharing source files between multiple programs. One way to do this is to create a library from the common source files, which can then be linked into resulting programs. (Creating libraries is discussed in the chapter called Building and Linking with Libraries, below.)
A more straightforward, but perhaps less convenient, way to share source files between multiple programs is simply to include the common files in the lists of source files for each program:
Program(Split('foo.c common1.c common2.c')) Program('bar', Split('bar1.c bar2.c common1.c common2.c')) |
SCons recognizes that the object files for the common1.c and common2.c source files each only need to be built once, even though the resulting object files are each linked in to both of the resulting executable programs:
% scons -Q cc -c -o bar1.o bar1.c cc -c -o bar2.o bar2.c cc -c -o common1.o common1.c cc -c -o common2.o common2.c cc -o bar bar1.o bar2.o common1.o common2.o cc -c -o foo.o foo.c cc -o foo foo.o common1.o common2.o |
If two or more programs share a lot of common source files, repeating the common files in the list for each program can be a maintenance problem when you need to change the list of common files. You can simplify this by creating a separate Python list to hold the common file names, and concatenating it with other lists using the Python + operator:
common = ['common1.c', 'common2.c'] foo_files = ['foo.c'] + common bar_files = ['bar1.c', 'bar2.c'] + common Program('foo', foo_files) Program('bar', bar_files) |
This is functionally equivalent to the previous example.
<<< Previous | Home | Next >>> |
Compiling Multiple Programs | Up | Building and Linking with Libraries |