Tc build fixes 01 #125
Merged
Tc build fixes 01 #125
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
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.
I've added Turbo C 2.01 to the CI, but as yet we don't have access to the compiler there. I have in mind to create an encrypted tarball which we can decrypt in the CI using github actions secrets facility, unless someone else wants to host an unencrypted version somewhere?
Notes:
1/ Firstly I've reverted the echolib changes as per the discussion at #117
2/ If you have the Turbo C installed at c:\tc201 in your dosemu C drive, then running the ci_build script will also perform the a TC2 builds.