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

Windows build doesn't work with default cpprestsdk build #4

Open
garethsb opened this issue Oct 4, 2024 · 0 comments
Open

Windows build doesn't work with default cpprestsdk build #4

garethsb opened this issue Oct 4, 2024 · 0 comments

Comments

@garethsb
Copy link
Collaborator

garethsb commented Oct 4, 2024

The example app builds and starts but the HTTP endpoints are inaccessible.

Where the instructions have this:

conan install src `
  -g CMakeToolchain `
  --settings:all build_type=<Release-or-Debug> `
  --build=missing `
  --output-folder=src/conan

The workaround is adding the following extra options for cpprestsdk and forcing nmos-cpp to rebuild:

conan install src `
  -g CMakeToolchain `
  --settings:all build_type=<Release-or-Debug> `
  --options:all cpprestsdk/*:http_client_impl=asio `
  --options:all cpprestsdk/*:http_listener_impl=asio `
  --build=nmos-cpp/* `
  --build=missing `
  --output-folder=src/conan

This needs to be repeated for both build_type=Debug and build_type=Release.
Then rebuild NvNmos.
If you run nvnmos-example with final command line arg -40 (most verbose logging level) you’ll see "Build settings" are output as one of the first log messages which confirm which HTTP implementation is being used.

However, nmos-cpp certainly used to work with the default WinHTTP/HTTP.SYS implementation, just possibly requiring running as administrator so that listening on the wildcard address is permitted, so it'd be good to understand what's changed.

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

No branches or pull requests

1 participant