WIP : Improving macos build step docs #3873
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…learer with a screenshot
|
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. |
|
@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) |
pointum
reviewed
Jun 7, 2022
|
|
||
| ### 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. |
fb33cb2 to
3260ced
Compare
spatecon
approved these changes
Dec 29, 2022
HarryVasanth
suggested changes
Dec 31, 2022
|
|
||
| ### 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. |
There was a problem hiding this comment.
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. |
cde503b to
c3e08c3
Compare
3fdf38c to
5c29a52
Compare
3c98442 to
a0978bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
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.