Adds support for building earlier releases using docker #37
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.
Description
In response to #36, this PR adds support for building earlier releases of the project using the docker file, and the provided installation script
install-oatpp-modules.sh
. The behaviour on the consumer side, has not changed, meaning that the latest version can still build an run by the following commands:However, if you are to build and run an earlier release of
example-crud
, you can now specify the version number as an build argument, thus preventing the CMake build from failing, due to mismatching version numbers. Thus building version1.3.0-latest
would require the following commands:Details
This behaviour was achieved by changing the installation script
install-oatpp-modules.sh
to accept an extra argument, specifying the version number. If such an argument is provided, the flag--branch
will be specified upon cloning the required dependencies. Furthermore, a new info message has been provided, such that it can be differentiated between cloning the latest release and cloning a specific release.To improve usability on the consumer side, a build argument was added to the docker file, in order to propagate the version number into the installation script.
The
README.md
has been changed to describe how to build earlier releases of the project.