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

macOS requirements are not actual #157

Open
YellingOilbird opened this issue Jun 25, 2022 · 7 comments
Open

macOS requirements are not actual #157

YellingOilbird opened this issue Jun 25, 2022 · 7 comments

Comments

@YellingOilbird
Copy link

YellingOilbird commented Jun 25, 2022

Ok, there is little surprise for me, in requirements you say that all I need - macOS x86, but I have version of this older than 11.0 and I cannot use sandbox utils. Mark this with macOS ^11.0 in requirements, I spent a lot of time for coding for nothing

@itegulov
Copy link
Contributor

Could you share which version of macOS you are using and what exactly was not working for you? workspaces not working on macOS below 11.0 was not intentional, so I will look into this to see if this is something we can address.

@YellingOilbird
Copy link
Author

YellingOilbird commented Jul 19, 2022

I got this
High Sierra 10.13
Снимок экрана 2022-07-19 в 15 45 30

@YellingOilbird
Copy link
Author

Could you share which version of macOS you are using and what exactly was not working for you? workspaces not working on macOS below 11.0 was not intentional, so I will look into this to see if this is something we can address.

@itegulov So, maybe I can build for a while without some components? Cause I really need this tests for my contracts and cannot build this because of provided errors. Maybe I can setup build environments?

@ChaoticTempest
Copy link
Member

@YellingOilbird you can get the sandbox binary by cloning nearcore and running make sandbox-release. Then the binary will be located in sandbox/release/neard once it's done building.

In workspaces-rs, you can point to this binary via the NEAR_SANDBOX_BIN_PATH env var, just note that when running cargo test, this has to be an absolute path so something like the following should work:

NEAR_SANDBOX_BIN_PATH=/home/user/nearcore/sandbox/release/neard cargo test

I'll see why this is failing for macos High Sierra. Definitely unexpected that it's failing like that

@YellingOilbird
Copy link
Author

@ChaoticTempest thanks for response! Try this instructions and write feedback
Also, with this preparations should I use earlier versions? I checked and my cargo print about something workspaces-rs versions able to build on >10.5 instead of >11.0 (like on screenshot)

@ChaoticTempest
Copy link
Member

As long as nearcore is able to be built with 10.5, then it'll work with workspaces-rs regardless

@YellingOilbird
Copy link
Author

@ChaoticTempest hey, thanks for your help, but actually this one (nearcore + sandbox) not built correctly cause librocksdb-sys issues which usually happen with 10.13 macOS. And even if ill solve them with customization after cloning librocksdb-sys it costs more then 10Gb which I don't have on my hardware for now for safety work. Will be waiting for updates or trying to work for more money to buy the newest hardware! :)

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

No branches or pull requests

3 participants