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

Cargo contract does not obey target-dir setting in Cargo.toml #1411

Open
goastler opened this issue Nov 24, 2023 · 0 comments
Open

Cargo contract does not obey target-dir setting in Cargo.toml #1411

goastler opened this issue Nov 24, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@goastler
Copy link

Describe the bug
Cargo contract does not obey target-dir setting in Cargo.toml. It defaults to the ./target directory relative to the src files

To Reproduce
Steps to reproduce the behavior:

  1. clone flipper contract
  2. add

[build]
target-dir = '/path/to/my/non/default/target/dir'

to the Cargo.toml
3. run `cargo contract build`
4. observe that the build artifacts end up in the default `./target` dir, not the one set in Cargo.toml

**Expected behavior**
The build output to be put in the specified target directory

**Environment (please complete the following information):**
 - OS: Ubuntu 22.04.3 LTS
 - `cargo-contract` version [e.g. 3.0.1] cargo-contract-contract 3.0.1-unknown-x86_64-unknown-linux-gnu
 - ink! version: [e.g. 4.2.0] 4.3.0
 - `substrate-contracts-node` version: [e.g. 0.14.0] 0.30.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant