makefiles: restructure and fix some issues with various make tools #166
Conversation
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
- move TARGET related macros to toolchain related makefiles - move CPU related setup to toolchain related makefiles Notes: not all make utilities behave same that some construct cannot be used only stupid hardcoded names works OK !! environment variables is not created from macros if not exist in environment !! it is wmake and nmake behaviour, if appropriate tool is not configured (env. variables not exist) then you must use command line parameters to work correctly in any situation command line parameters is necessary now it is fixed for INCLUDE/INCLUDEPATH macros that appropriate values are passed by command line other env.vars must be fixed too (LIBPATH, LIB, ...), but it is not issue for gcc and partialy for OW
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notes: not all make utilities behave same that some construct cannot be used only stupid hardcoded names works OK
!! environment variables is not created from macros if not exist in environment !!
it is wmake and nmake behaviour, if appropriate tool is not configured (env. variables not exist) then you must use command line parameters to work correctly
if we want to work in any situation then command line parameters is necessary
now it is fixed for INCLUDE/INCLUDEPATH macros that appropriate values are passed by command line
other macros/env.vars must be fixed too (LIBPATH, LIB, ...), but it is not issue for gcc and mostly for OW