1aef5c06a3
automatic. The point is that now a subdirectory can be added to the build process just by creating a SConscript file in it. The process has two passes. On the first pass, all subdirs of the root of the tree are searched for SConsopts files. These files contain any command line options that ought to be added for a particular subdirectory. On the second pass, all subdirs of the src directory are searched for SConscript files. These files describe how to build any given subdirectory. I have added a Source() function. Any file (relative to the directory in which the SConscript resides) passed to that function is added to the build. Clean up everything to take advantage of Source(). function is added to the list of files to be built. --HG-- extra : convert_revision : 103f6b490d2eb224436688c89cdc015211c4fd30 |
||
|---|---|---|
| .. | ||
| arch | ||
| base | ||
| cpu | ||
| dev | ||
| doxygen | ||
| kern | ||
| mem | ||
| python | ||
| sim | ||
| unittest | ||
| Doxyfile | ||
| SConscript | ||