CI (Linux and OS X, HashLink and hxcpp) #33
Merged
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.
Partially addresses #24. There are issues with Windows for both hxcpp and HashLink, so for now I have not enabled it.
For hxcpp, the failure happens at hxcpp link time, where
native.objcannot see methods fromutf8.obj. Unsure why this actually works for hxcpp on OS X and Linux, perhaps a case of dynamically/statically linking the native library differently.For HashLink, the failure happens when trying to build HashLink. Following the Azure pipeline for HashLink almost works, but the
windows-latestCI runner on GitHub seems to not have the Windows 8.1 SDK, which is whathl.slnwants by default. Cursory searches show no way to select the SDK on the command-line.