We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Technically Travis CI/CD kinda sucks on it's own due to lack of Artifacts without paid for Amazon S3 filestorage)
But it would be good to add master based .travis.yml to mainstream for all targets (standalone and packaged builds)
To achieve this though. The custom PSC toolchain has issues when ran from a containerised environemnt which needs to be worked out.)
Easiest way to test this is to pull down debian docker container, bash to it, git pull the PSC toolchain and AB git and try a cmake build.
It will faill some basic GCC build test.
I ran out of time to test and resolve this issue personally.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Technically Travis CI/CD kinda sucks on it's own due to lack of Artifacts without paid for Amazon S3 filestorage)
But it would be good to add master based .travis.yml to mainstream for all targets (standalone and packaged builds)
To achieve this though. The custom PSC toolchain has issues when ran from a containerised environemnt which needs to be worked out.)
Easiest way to test this is to pull down debian docker container, bash to it, git pull the PSC toolchain and AB git and try a cmake build.
It will faill some basic GCC build test.
I ran out of time to test and resolve this issue personally.
The text was updated successfully, but these errors were encountered: