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.

Sign up for GitHub

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

Jump to bottom

Force the xcode lockfile into CARGO_BUILD_TARGET #13

Closed
wants to merge 18 commits into from
Closed

Force the xcode lockfile into CARGO_BUILD_TARGET #13

wants to merge 18 commits into from

Conversation

MaikKlein
Copy link
Member

@MaikKlein MaikKlein commented Feb 6, 2020 •
edited
Loading

Potentially fixes #12

Instead of using make, we call xcodebuild directly and force the lock file into the target dir.

@MaikKlein MaikKlein changed the title Force the xcode lockfile into CARGO_TARGET_DIR Force the xcode lockfile into CARGO_BUILD_TARGET Feb 6, 2020
@MaikKlein
Copy link
Member Author

Maybe we should also nuke the derived data explicitly before we try to build ashmolten.

@repi repi closed this Jun 12, 2020
@mergify mergify bot deleted the lock-file branch June 12, 2020 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Build failure Could not acquire lock at path
2 participants
@MaikKlein @repi