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

Forge does not support solidity compiler settings/options #718

Closed
2 tasks done
sambacha opened this issue Feb 11, 2022 · 1 comment
Closed
2 tasks done

Forge does not support solidity compiler settings/options #718

sambacha opened this issue Feb 11, 2022 · 1 comment
Labels
C-forge Command: forge Cmd-forge-build Command: forge build T-bug Type: bug

Comments

@sambacha
Copy link
Contributor

Component

Forge

Have you ensured that all of these are up to date?

  • Foundry
  • Foundryup

What version of Foundry are you on?

forge 0.1.0 (6433961 2022-02-11T04:19:30.593881+00:00)

What command(s) is the bug in?

forge build -o dist --extra-output '*'

Operating System

Linux

Describe the bug

When trying to specify compiler output passing the following options cause issues:

 forge build -o dist --extra-output '*'
compiling...
Compiling 4 files with 0.8.10
Error:
   0: missing field `wast` at line 1 column 20446

Location:
   /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/result.rs:1914

When a valid config.json is found in the root dir:

$ forge build -o dist --extra-output *

> error: Found argument 'config.json' which wasn't expected, or isn't valid in this context

When no config.json file is found in the root dir:

forge build -o dist --extra-output *
error: Found argument 'foundry.toml' which wasn't expected, or isn't valid in this context

USAGE:
    forge build [OPTIONS]

For more information try --help

additional i tried the this for config.json

"outputSelection: { "*": { "*": [ "*" ], "": [ "*" ] } }"

which would ask for every available output and same error.

When passing a value like legacyAssembly

forge build -o dist --extra-output legacyAssembly

compiled output is successful, but its using the default settings

When passing the value like evm.assembly

 forge build -o deploy --force --extra-output evm.assembly

I get correct output

@sambacha sambacha added the T-bug Type: bug label Feb 11, 2022
@onbjerg onbjerg added C-forge Command: forge Cmd-forge-build Command: forge build labels Feb 12, 2022
@sambacha
Copy link
Contributor Author

Think this can be closed per the latest update that provides slither compatibility @onbjerg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-forge Command: forge Cmd-forge-build Command: forge build T-bug Type: bug
Projects
None yet
Development

No branches or pull requests

2 participants