Missing manifest file issue about cross HOT 5 CLOSED

I think this is an issue of us not properly resolving workspaces, so we don't grab the correct paths.

failed to read `/bevy_mod_scripting/Cargo.toml`

looks very wrong.

This was supposed to be fixed with #684 but I think an assumption done there has been broken.

Should be fixed with #939, can you reproduce the issue with cross installed from the main branch?

from cross.

https://github.com/makspll/bevy_mod_scripting/blame/10dcca992a5bdcd172b293e54a3f6dcdbbd848f2/crates/languages/bevy_mod_scripting_lua_derive/Cargo.toml#L26 this is the reason I think. Try using workspace = true here

from cross.

Sorry, linked the wrong line, should be https://github.com/makspll/bevy_mod_scripting/blob/10dcca992a5bdcd172b293e54a3f6dcdbbd848f2/crates/languages/bevy_mod_scripting_lua_derive/Cargo.toml#L43

the problem is basically that you're traversing down to much, if anything it should be path = "../../..", fixing that line makes the project build for me on cross 0.2.5

from cross.

So to summarize, cross 0.2.5 mounts the cargo workspace at /project, the manifest at $workspace/crates/languages/bevy_mod_scripting_lua_derive/Cargo.toml points to a folder that travels one folder outside the workspace, ../../../../bevy_mod_scripting. The fourth .. is / meaning the path becomes /bevy_mod_scripting which is not correct for how the workspace is mounted.

You can reproduce this issue without cross by renaming the repos folder to something else, here's me doing it on windows by renaming bevy_mod_scripting to bevy_mod_scripting_renamed

error: failed to load manifest for workspace member `G:\workspace\bevy_mod_scripting_renamed\crates\bevy_script_api`

Caused by:
  failed to load manifest for dependency `bevy_mod_scripting_lua_derive`

Caused by:
  failed to load manifest for dependency `bevy_mod_scripting`

Caused by:
  failed to read `G:\workspace\bevy_mod_scripting\Cargo.toml`

Caused by:
  The system cannot find the path specified. (os error 3)

from cross.

Oh good catch! I wonder why this doesn't break on a normal build?

from cross.