-
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Move generic code from ?
build.sh
to ?Macros.sh
?`Macros.sh`: +`SUSUWU_BUILD_SOURCES()`, +`SUSUWU_REBUILD_CTAGS()`, +`SUSUWU_SETUP_CXX_PROCESS_MINGW()`, +`SUSUWU_PROCESS_RELEASE_DEBUG()`, +`SUSUWU_SETUP_BUILD_FLAGS()`, +`SUSUWU_SETUP_OUTPIT_DIRS()`, +`SUSUWU_CLEAN_OUTPUT()`, +`SUSUWU_PROCESS_CLEAN_REBUILD()`, +`SUSUWU_TEST_OUTPUTS()` (from `./build.sh`.) This allows to use `Macros.sh` as a simple `make` substitute. ?`build.sh`: Now that most of the reusable code was used to produce functions in `Macros.sh`, replace `build.sh`'s copy of that code with calls to `Macros.sh`; This allows simple replacement of most of our build logic with `make` (or `CMake`) in the future, which assists with issue #18 (support more tools). Is followup to: 2a6e624 (?`build.sh`: incremental builds (reuse objects)) TODO: `OBJDIR="./obj/"`, `BINDIR="./bin/"`, `for SOURCE in ${CXX_SOURCE_PATH}Class*.hxx ${CXX_SOURCE_PATH}Macros.hxx; do` are somewhat project-specific (just for local use); Remove our project-specific (local) values from the new `Macros.sh` functions, have new functions more close to `make` protocols, have `build.sh` call those functions with our project-specific (local) values.
- Loading branch information
1 parent
f2cf644
commit d025402
Showing
2 changed files
with
163 additions
and
118 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters