Makefile.include: remove functionality to build with another version.#10543
Conversation
Makefile.include contained logic to clone a different RIOT version and build the application against it. This can be easily achieved by making a git worktree and overriding RIOTBASE, without adding any complexity to our makefiles. Therefore, the feature is being removed.
|
I also planned to remove it for some time, it introduces a specific branch in the main Makefile.include for something I would not want included in there. Removing it will also simplify cleaning other things. Maybe we should put a deprecation error for one full release to see if somebody complains. |
|
We do not maintain compatibility with previous versions, even build with docker cannot work, so I do not like having something making think it is the case. If |
There was a problem hiding this comment.
ACK, I wanted to remove it too as it confused me a lot when setting RIOT_VERSION instead of RIOT_VERSION_OVERRIDE.
There was no objections until now. Also it can easily be reverted/proposed differently if someone complains.
We can merge when murdock is happy.
aabadie
left a comment
There was a problem hiding this comment.
Looks good and would be great to have this for the release.
ACK and go
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. When building with `RIOT_CI_BUILD=1` this also now prevents calling `git describe` and `git rev-parse` which saves around 0.1 seconds per execution on my machine.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. When building with `RIOT_CI_BUILD=1` this also now prevents calling `git describe` and `git rev-parse` which saves around 0.1 seconds per execution on my machine.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. When building with `RIOT_CI_BUILD=1` this also now prevents calling `git describe` and `git rev-parse` which saves around 0.1 seconds per execution on my machine.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. When building with `RIOT_CI_BUILD=1` this also now prevents calling `git describe` and `git rev-parse` which saves around 0.1 seconds per execution on my machine.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. When building with `RIOT_CI_BUILD=1` this also now prevents calling `git describe` and `git rev-parse` which saves around 0.1 seconds per execution on my machine.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. When building with `RIOT_CI_BUILD=1` this also now prevents calling `git describe` and `git rev-parse` which saves around 0.1 seconds per execution on my machine.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. When building with `RIOT_CI_BUILD=1` this also now prevents calling `git describe` and `git rev-parse` which saves around 0.1 seconds per execution on my machine.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly.
RIOT_VERSION is not used for building a specific RIOT version anymore since RIOT-OS#10543. The variable can now be used directly. Add deprecation warning.
Contribution description
Makefile.include contained logic to clone a different RIOT version and build the application against it. This can be easily achieved by making a git worktree and overriding RIOTBASE, without adding any complexity to our makefiles. Therefore, the feature is being removed.
Testing procedure
CI will test that nothing got broken.