Add openssl to the macOS build instructions - #5209
Conversation
|
Thanks for the PR @karpovantonme |
740fdb2 to
f37081d
Compare
|
rebased onto master. 2 red windows jobs were Checks are sitting on approval to start |
|
spoke too soon, the rebased run fails the same way. the line above the crate error is the real one: so the windows runner image has moved past the vcpkg checkout pinned here, and libxml never gets its library. nothing a PR can do about that, and since windows only runs on pull requests, master will not show it either fine by me if you would rather close this one |
|
/rebase |
|
🕗 /rebase is running, please wait for completion. |
A fresh macOS has no OpenSSL where openssl-sys looks for it, so cargo build stops before it starts. The Linux section already lists the native libraries per distribution; this says the same for macOS. Closes Orange-OpenSource#5096
|
🔨 Auto rebase from |
f37081d to
508ac2b
Compare
|
Replaced by #5234 |
Closes #5096
The macOS section installs
pkg-configbut not OpenSSL, so on a clean machinecargo buildstops inopenssl-sysbefore anything is compiled. The Linux section right above already names the native libraries and lists them per distribution, so this says the same thing for macOS and addsopensslto the brew lineWording of the first sentence is taken from the Linux section so the two read the same way
Three files, because README.md and packages/hurl/README.md are generated: I edited
docs/installation.mdand regenerated both withbin/docs/build_readme.py githuband... crates, the waybin/docs/update_all.shcalls them