Open BananaRama203 opened 4 years ago
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.
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.