macOS build fails with strange permissions issue

[virtualritz]

MoI? Is that the NURBS modeler?

  ...
  Downloaded 20 crates (2.6 MB) in 2.88s
error: failed to determine package fingerprint for build script for mesh-ripper v0.4.0 (/Users/moritz/code/crates/mesh-ripper)

Caused by:
  failed to determine the most recently modified file in /Users/moritz/code/crates/mesh-ripper

Caused by:
  failed to determine list of files in /Users/moritz/code/crates/mesh-ripper

Caused by:
  cannot read "/Users/moritz/code/crates/mesh-ripper/build/macos/src/Applications/MoI v3.2 trial.app/Contents/Resources/dosdevices/z:/.fseventsd"

Caused by:
  Permission denied (os error 13)

P.S.: I started working on an OpenNURBs wrapper for Rust. But I didn't have time in the last two months. Needs a mesher though – to be useful in the context of this crate, eventually.

[rezural]

@virtualritz , Sorry about the delay, only just noticed this... first issue 👍

I'm not sure about this to be honest. I haven't actually built this on mac, it has only been built via the github actions. Have you tried the release download from there?

Definately no dependencies on MoI v3.2 trial.app, very strange.

Can you try this (perhaps remove target/ before doing this so it will give a full build output):

cargo build --verbose --release --features native

And paste the output here

[rezural]

This may be a problem with fsevents, the z:/.fseventsd seems a little weird, like it thinks it's on windows.

That file on the 3rd last line definately (probably, maybe) won't exist on mac.

[virtualritz]

Have you tried the release download from there?

I'm interested in hacking/contributing so the release d/l is not useful to me. :)

This may be a problem with fsevents, the z:/.fseventsd seems a little weird, like it thinks it's on windows.

This is MoI likely using some weird framework to make what is essentially a Windows app work on macOS.

Why/how is MoI required? I mean you say you build this on Linux but there is no MoI on Linux, afaik.

Can you try this (perhaps remove target/ before doing this so it will give a full build output):

Doing a

cargo build --verbose --release --features native

results in exactly the same build failure.

[nhemsley]

Mesh riper doesnt depend on MoI at all, Is it installed on your system?

Edit: this is my other github

[nhemsley]

Can you paste the full output of

cargo build --verbose --release --features native

[rezural]

@virtualritz I just had a thought about this,

There is a symlink to /Applications in the build dir (I started mesh-ripper off using bevy-template), perhaps run this before trying to build:

rm  build/macos/src/Applications

then try building.

[rezural]

I also found this issue,

NiklasEi/bevy_game_template#13

Which would seem to indicate this is the cause.