Skip to content
New issue

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

CI (Linux) #36

Merged
merged 6 commits into from
Jun 20, 2022
Merged

CI (Linux) #36

merged 6 commits into from
Jun 20, 2022

Conversation

revmischa
Copy link
Contributor

Build on linux

Should add one for macOS

@revmischa revmischa requested a review from kblaschke June 12, 2022 15:46
@kblaschke
Copy link
Member

Should also add a build for Windows as well. Due to the large platform differences regarding dependency installation, one YAML file per platform might be a good idea instead of using a matrix. We can then use the build matrix to test different "build styles", e.g. shared and static linking of libprojectM.

On Windows, this will take a long time, as vcpkg compiles all dependencies on each CI run, which will take ~20mins or so at least for POCO and SDL2. I still have to come up with a better solution to use some pre-built binary artifacts of the dependencies. GitHubActions isn't a great artifact store. The best solution I've came up with is to have a repo for the deps, build them (manually) via Actions and create a release archive via vcpklg's export functionality, then download the latest release ZIP here, unpack and use it.

@revmischa
Copy link
Contributor Author

Should also add a build for Windows as well. Due to the large platform differences regarding dependency installation, one YAML file per platform might be a good idea instead of using a matrix. We can then use the build matrix to test different "build styles", e.g. shared and static linking of libprojectM.

On Windows, this will take a long time, as vcpkg compiles all dependencies on each CI run, which will take ~20mins or so at least for POCO and SDL2. I still have to come up with a better solution to use some pre-built binary artifacts of the dependencies. GitHubActions isn't a great artifact store. The best solution I've came up with is to have a repo for the deps, build them (manually) via Actions and create a release archive via vcpklg's export functionality, then download the latest release ZIP here, unpack and use it.

Let's start with whatever's easiest IMO

@revmischa revmischa changed the title CI CI (Linux) Jun 20, 2022
@revmischa revmischa merged commit b69ee16 into master Jun 20, 2022
@kblaschke
Copy link
Member

Sure, somethin's better than nothin'!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants