Windows build from sources documentation is outdated #136

Closed
opened 2022-07-18 15:18:06 +00:00 by arittner · 0 comments
Contributor

I tried to build Plume from the sources under Windows 10/11 64bit and run in a lot of issues, because the installation steps are a little bit outdated. This issue describes the gaps in the documentation. A PR will fix it.

  • wasm-pack installations fails, because of a wrong OpenSSL linkage
  • wasm-pack build is not working, because GNU gettext is needed
  • Documentation mentions OPENSSLDIR instead of OPENSSL_DIR (style error with wrong usage of italic markdown)
  • Usage of Linux commands xargs and stat fails on plain Windows environment
  • Diesel will not build without a PQ_LIB_DIR environment variable which points to the postgress lib folder
  • Maybe for Postgres and OpenSSL a manual update for the environment variable PATH is needed (in this case to run plm and plume)
I tried to build Plume from the sources under Windows 10/11 64bit and run in a lot of issues, because the installation steps are a little bit outdated. This issue describes the gaps in the documentation. A PR will fix it. * wasm-pack installations fails, because of a wrong OpenSSL linkage * wasm-pack build is not working, because GNU gettext is needed * Documentation mentions `OPENSSLDIR` instead of `OPENSSL_DIR` (style error with wrong usage of italic markdown) * Usage of Linux commands `xargs` and `stat` fails on plain Windows environment * Diesel will not build without a `PQ_LIB_DIR` environment variable which points to the postgress lib folder * Maybe for Postgres and OpenSSL a manual update for the environment variable `PATH` is needed (in this case to run `plm` and `plume`)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: plume/documentation#136
No description provided.