-
Notifications
You must be signed in to change notification settings - Fork 31
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
add CI build with clang #23
base: patch-ci-base
Are you sure you want to change the base?
Conversation
This needs more work. If we change something, we need to change it both in the deployment workflow and the PR workflow. We don't want them to go out of sync and test different things. I also don't like the suffix hack. If we do this, the compiler should be properly part of the image name. If we want to do only one run, we can add a fixed |
Making this a draft PR for now. Currently, my main motivation for having a clang build also is to see, if this reports something other than the gcc build. And to get more insight in how the github ci actions work. |
dd17585
to
897d13e
Compare
810af83
to
4118916
Compare
46fd8d8
to
9596452
Compare
c9ac30f
to
667932b
Compare
Signed-off-by: Axel Heider <[email protected]>
3ec8206
to
3b8b973
Compare
Signed-off-by: Axel Heider <[email protected]>
needed unless KernelFWholeProgram is fixed Signed-off-by: Axel Heider <[email protected]>
Signed-off-by: Axel Heider <[email protected]>
This addresses parts of #21 and adds a build with clang. The resulting archive gets the suffix
-clang
. Forgcc
builds no suffix is used to avoid breaking any existing workflows.