Skip to content

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

@garethsb

Description

@garethsb

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions