Closed mfilippov closed 2 years ago
They can be found on the AppVeyor outputs, however recently they have stopped working for me on macOS, I think it's because they are built for M1 only, I have to build locally today.
Yes I suppose I should be including the Mac artifacts when publishing a Release. Ideally we'd build both Intel and M1 bits.
It looks like both are being built, however the last one wins because they will both output to the same path.
I've looked at building a universal app, but I don't think it's simple today with .NET, I've tried using lipo manually to combine the two outputs, but it's not just the hostapp process that needs to change between architectures, for now we might just need 2 separate artifacts.
Hmm, do I need to build on Mac? I built on Windows and didn’t see any zip files. How do I obtain a zip file to publish to Releases?
If you run the cake build script it will produce the macOS builds and zip them up, you don't need a mac to do it as the sdk will generate the apphost mac process that will bootstrap the app, the rest is all typical dotnet artifacts.
What do you think about switching to GitHub Actions? I need to update how versioning works and select the appropriate artifacts: https://github.com/slang25/MSBuildStructuredLog/pull/1
In that PR I'm building both architectures for mac
Ah, OK, I haven't looked into the Cake bit at all yet. Yeah I suppose it's time to move to GitHub Actions.
@slang25 @KirillOsenkov Does a new release need to be triggered somehow? I am interested in the Mac artifacts as well, and see the PR above was merged.
I'm not sure what I should do locally to produce the artifacts to publish to the release
You can grab the macOS per-architecture builds from the CI artifacts here: https://ci.appveyor.com/project/KirillOsenkov/msbuildstructuredlog/builds/42050519/artifacts
I'm still interested in adding GitHub Actions as I think it would be easier to build on macOS/linux for the mac build, that way the user won't need to chmod +x
the executable before it's usable.
There are a few outstanding things I'd need to solve/understand
OK cool, I have uploaded both zips to the latest Release.
We should rename both zips to not have spaces, since GitHub Release replaces them with dots.
I found a guide about macOS builds: https://github.com/KirillOsenkov/MSBuildStructuredLog#building--running-the-avalonia-version-on-mac, but I can't find zip artefact on Releases.