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

Fetch remote dylint_driver in dylint_testing by default #15

Merged
merged 1 commit into from
May 20, 2021

Conversation

smoelius
Copy link
Collaborator

The driver builder uses a remote dylint_driver package if building in release mode or if dylint_driver_remote is enabled.

https://github.com/smoelius/dylint/blob/844a3ab339d0dcf69102044368b1bbd907b45787/dylint/src/driver_builder.rs#L112-L113

So when dylint_testing is built in debug mode, it looks for a local dylint_driver package and cannot find one.

A solution is to have dylint_testing enable the dylint_driver_remote feature by default.

I think I would prefer the feature be dylint_driver_local, but this solves the immediate problem.

The driver builder uses a remote `dylint_driver` package if building
in release mode or if `dylint_driver_remote` is enabled.

https://github.com/smoelius/dylint/blob/844a3ab339d0dcf69102044368b1bbd907b45787/dylint/src/driver_builder.rs#L112-L113

So when `dylint_testing` is built in debug mode, it looks for a local
`dylint_driver` package and cannot find one.

A solution is to have `dylint_testing` enable the `dylint_driver_remote`
feature by default.

I think I would prefer the feature be `dylint_driver_local`, but this
solves the immediate problem.
@smoelius smoelius merged commit f3682d3 into trailofbits:master May 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant