You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
localok, err=fs.copy(dir.path(cwd, from), to, "exec")
ifnotokthen
returnnil, "Failed copying " ..from.." in " ..to..": " ..err
end
end
because you just search output in target/release
error will produce when user type CARGO_BUILD_TARGET=aarch64-unknown-linux-gnu luarock build --pack-binary-rock --no-install ....
this command will produce output into target/aarch64-unknown-linux-gnu/release, so.. it will fails at line 105
The text was updated successfully, but these errors were encountered:
(Not the maintainer here, just another user that has run into similar issues.)
Cargo is actively resistant to providing a discovery mechanism that a build wrapper can use to discover where Cargo is putting stuff. They really want to be the highest level build system and not be integrated into higher level ones like this. There are several long running issues/PRs/RFCs related to this. There is a little bit of progress lately, but there still isn't a good mechanism for this.
In the mean time you can set the location manually by changing the --target-dir option at build time, or even target_path in your Rockspec. This can be used to substitute the default project relative ./target for another path. For the cross-compile use case set it to target/<target_tripple>.
The mechanisms I know of to parse this manually would require adding a dependency to read JSON or parsing logs, neither of which appeal to my sensibilities.
error at here:
luarocks-build-rust-mlua/src/luarocks/build/rust-mlua.lua
Lines 84 to 107 in 3350f60
because you just search output in
target/release
error will produce when user type
CARGO_BUILD_TARGET=aarch64-unknown-linux-gnu luarock build --pack-binary-rock --no-install ....
this command will produce output into
target/aarch64-unknown-linux-gnu/release
, so.. it will fails at line 105The text was updated successfully, but these errors were encountered: