-
Notifications
You must be signed in to change notification settings - Fork 840
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
Explicitly link against WSLAY when available #2196
Conversation
I've just had another look, pkg-config is not the right place to add this. It only fixed it because there was a symptom of libh2o-evloop not linking against it which was "fixed" by getting dnsdist to include it in its linker. I'll modify my fix and push out an update to this branch :) |
When other libraries attempt to link against libh2o and libh2o-evloop that was compiled with libwslay available, there are errors from missing symbols associated with code which makes use of the wslay library. To rectify this, explicitly link against libwslay during the build process. Fixes h2o#2105 Signed-off-by: James Taylor <james@jtaylor.id.au>
527fb1a
to
f7d5cb8
Compare
I wasn't sure if putting the link to WSLAY_LIBRARIES into EXTRA_LIBS would break anything so I explicitly added it to the libh2o and libh2o-evloop targets. This compiles fine on my end and I was able to link against the library correctly with dnsdist. |
Thanks the changes looks fine to me. Merged. |
Update wslay link patch with upstream fix from h2o/h2o#2196 Signed-off-by: James Taylor <james@jtaylor.id.au>
Update wslay link patch with upstream fix from h2o/h2o#2196 Signed-off-by: James Taylor <james@jtaylor.id.au>
When other libraries attempt to link against libh2o and libh2o-evloop that was
compiled with libwslay available, there are errors from missing symbols
associated with code which makes use of the wslay library. To rectify this,
explicitly link against libwslay during the build process.
Fixes #2105
Signed-off-by: James Taylor james@jtaylor.id.au