Conversation
Contributor
|
Great for the Nano X builds. It is needed for release 9. |
This file contains hidden or 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.
This is the first step in automatically building some OpenWatcom applications already in the ELKS applications tree.
When OpenWatcom C has been configured for ELKS by executing the
libc/wcenv.shscript, the WATCOM= environment variable is set and the OWC tools are added to PATH.When WATCOM is defined, an enhanced FAT filesystem checker is built using OWC huge model
fsck-dos.os2, which allows for checking FAT16 HD images without running out of memory, and an experimentalpaint.os2OWC version of Paint is built, for testing graphics using OWC. In addition, when C86 is defined from executingc86env.shin 8086-toolchain, the C86 version of Paintpaint.c86is built, testing the C86 compiler and development library by building a larger application.All these programs are copied directly to /bin in the target image (elkscmd/rootfs_template/bin). The next step will be integrating external Nano-X into the build process.