Windows: cargo install diesel-cli works but...

[tensor-programming]

I am on windows 10, and using the MSVC toolchain with latest nightly/beta and stable release.
For a while I had the Postgres from BigSQL installed and then I removed it in favor of the official installation. After doing this, I was able to compile the Diesel CLI fine, but now when I run it I get a dialogue box that opens up and says:

diesel.exe - System Error The code execution cannot proceed because LIBPQ.dll was not found. Reinstalling the program may fix this problem.

I have tried uninstalling and reinstalling Diesel as well as PostgreSQL multiple times to no effect. The PGSQL installation seems to work; I've used it with elixir ecto multiple times already. I was considering removing rust entirely to remove any files from the old failed diesel-cli installations but this would be an extreme step. Anyone have any ideas?

BTW I am only installing the PG backend using cargo install diesel_cli --no-default-features --features postgres. I haven't tried SQLite or MySQL.

[sgrif]

You need to make sure that libpq.dll is on your %PATH%.

[tensor-programming]

It is on my path. that's is the problem; I'm not sure why you closed this issue when it hasn't been resolved at all.
I did resolve this however by using vcpkg to install a new pqlib file and then pointed cargo towards it.

I understand that you probably are sick of listening to windows users complain about their terrible ecosystem but seriously...

[weiznich]

I'm not sure why you closed this issue when it hasn't been resolved

This issue was closed because diesels policy for open issues is the following:

Open issues in this repo should represent something that is actionable, and that you could reasonably open a pull request to fix.

This is clearly a issue with your current setup. We will happily help you there to figure these things out, but this discussion does not belong to the issue tracker. Use our gitter room for such questions.

[sgrif]

There's nothing wrong with discussing on the issue tracker, but as mentioned the action we can take is answering your question. Typically we close issues at that point, as more often than not people don't come back and say "this fully answered my question, thanks". I'm glad to hear that you got it sorted out.