Unable to build on macOS #19
Comments
Can you try running this inside of |
I am inside of xray_electron when I execute |
Sorry, of course. I misread a path in the beginning of your error message as your working directory. My bad. Let me look at this... |
I used nvm to install the specified version of node and if I clear out the node_modules directory then execute |
Okay, troubleshooting a bit, what if you run |
When I do both of those suggestions I get the same issue. I agree the Cargo.toml file looks correct and it should be picking it up, but for some reason its not, very weird. |
I have the same issue as @JonnyWalker81 but I as was able to build
|
macOS versions? Cargo versions? In absence of my ability to reproduce this is tricky. |
cargo 0.25.0 (96d8071da 2018-02-26) |
I'm on macOS 10.13.2, but that does seem to be an unlikely culprit. |
I tried it on my other computer as well which has 10.13 and had the same issue. |
|
Even more strange is that xray_code is referenced in the same way and that seems to build and be referenced correctly. I moved the lines in src/lib.rs to have |
I just updated npm to version 5.7.1 (I was on 5.5.1), when I did |
Thanks for hammering on this. I'm really sorry this is such a pain. Anything else I can try for you? |
Can you remove your node_modules folder (inside of xray_electron) and then do |
Sorry for the delay. Ran the build and then got distracted by something else. Hope this gives some clue. |
I am having the same issues on my end. Specs are as follows: Error output is the same as above. I tried different versions as well. |
same error here: `> Xray@0.1.0 start /Users/xxx/xray/xray_electron
npm ERR! A complete log of this run can be found in: |
I’m also unable to build. Is there a GUI for this yet? I know it is early, but I figured no harm in asking. I mainly wanted to build it to see what it looked like currently. Anyone have an screenshots if so? |
I am able to build on my macOS. I am seeing code on the screen but not able to edit anything.
|
I was also able to build successfully on macOS (10.13.3) with these versions: > cargo --version
cargo 0.26.0-beta (41480f5cc 2018-02-26)
> npm --version
5.6.0
> node --version
v8.9.4 I also tried |
I just did a pull and am able to build now, not sure exactly what changed to make it be able to build now. Hopefully, others can also build with the latest changes. |
Still no luck building. Perhaps I am missing something? I am inside of xray_electron, but npm install always returns an error saying: error: Could not compile |
I'm going to close this out because we're going to make a pretty big shift in our architecture that will probably change the build situation. I'll be writing about it today or Monday. If after that change (some time next week) there are new issues building, feel free to reopen. Thanks again for your interest. |
When I execute
npm install
thennpm start
I get the following error:Compiling xray_node v0.1.0 (file:///Users/jrothberg/Repositories/xray/xray_node)
error[E0463]: can't find crate for
napi
--> src/lib.rs:1:1
|
1 | extern crate napi;
| ^^^^^^^^^^^^^^^^^^ can't find crate
error: aborting due to previous error
If you want more information on this error, try using "rustc --explain E0463"
error: Could not compile
xray_node
.To learn more, run the command again with --verbose.
child_process.js:614
throw err;
^
Error: Command failed: cargo rustc --release -- -Clink-args="-undefined dynamic_lookup -export_dynamic"
at checkExecSyncError (child_process.js:574:11)
at Object.execSync (child_process.js:611:13)
at Object. (/Users/jrothberg/Repositories/xray/napi/scripts/napi.js:31:8)
at Module._compile (module.js:660:30)
at Object.Module._extensions..js (module.js:671:10)
at Module.load (module.js:573:32)
at tryModuleLoad (module.js:513:12)
at Function.Module._load (module.js:505:3)
at Function.Module.runMain (module.js:701:10)
at startup (bootstrap_node.js:190:16)
I am building with Rust 1.24.1 (I have also tried building with nightly and get the same result).
The text was updated successfully, but these errors were encountered: