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

WIP : Improving macos build step docs #3873

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

PicoCreator
Copy link

@PicoCreator PicoCreator commented Apr 7, 2022

While trying to work on : #3792

I find that the build docs to be insufficient for my rather new macOS Monterey build (v12.3)
So tried to pick at it, between the 1 hour+ build time of github actions (my only way of validating my code is somewhat valid).

Generally this was due to missing python modules, which installing pip3 on homebrew only makes it worse. The most progress i had was as what I have modified, but it fails at the spice project build step with the following

Screenshot 2022-04-07 at 10 18 21 PM

On further investigation, this seems like a possibly known issue for spice which is covered and resolved here

So as it seems i might still be stuck depending on github actions to validate builds >_<"

Any feedback on the missing steps would be appreciated


Alternatively, how do I use an .xarchive (built on github) to build and run the .app (on a macbook) : without a paid apple developer account.

@PicoCreator PicoCreator changed the title Improving macos build step docs WIP: Improving macos build step docs Apr 7, 2022
@PicoCreator PicoCreator changed the title WIP: Improving macos build step docs WIP : Improving macos build step docs Apr 7, 2022
@osy
Copy link
Contributor

osy commented Apr 8, 2022

Ah sorry about that. It’s literally only an issue since the last few commits so I’ve never updated the docs. I was hoping to have found a better solution than the hack I put for the GitHub actions build.

@PicoCreator
Copy link
Author

PicoCreator commented Apr 11, 2022

@osy - no worries, im trying to update the docs, for things i find confusing.

Did manage to get a working sysRoot build downloaded from github, so will see into making those steps clearer.

Also i have seen several project branch for out a subproject specifically for just providing releases for dependencies via github releases (and automating it via CLI, without needing the login, etc).

But I understand completely avoiding that route, and keeping everything in one place for now (less worry about keeping things in sync)


### Building Dependencies (Advanced)
- Find the list of [release builds here][1].
- Pick the latest release and download all of the `Sysroot-macos-*` artifacts for the architecture you will need (you will need to be signed in to a github account). If you only intend to run locally, it is alright to just download the sysroot for your traget architecture.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo says "traget"

@osy osy force-pushed the master branch 3 times, most recently from fb33cb2 to 3260ced Compare August 9, 2022 17:08

### Building Dependencies (Advanced)
- Find the list of [release builds here][1].
- Pick the latest release and download all of the `Sysroot-macos-*` artifacts for the architecture you will need (you will need to be signed in to a github account). If you only intend to run locally, it is alright to just download the sysroot for your traget architecture.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Pick the latest release and download all of the `Sysroot-macos-*` artifacts for the architecture you will need (you will need to be signed in to a github account). If you only intend to run locally, it is alright to just download the sysroot for your traget architecture.
- Pick the latest release and download all the `Sysroot-macos-*` artifacts for the architecture of your choice (you will need to be signed in to a GitHub account). If you only intend to run it locally, it is sufficient to download the SysRoot for your target architecture.

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.

5 participants