Hunter builds don't install the downloaded dependencies

[ringerc]

When Jaeger does its default "download it from the Internet" build, the resulting install is unusable:

• there are no opentracing headers installed
• there's no libyaml-cpp header or library installed

etc.

So it should probably either disable "make install" for Hunter builds and document how to do a normal install, or install all the built dependencies too. I'd suggest complaining if you try to use /usr/local as an install target in this case and suggesting another target.

It'd also be nice to document that hunter writes stuff to ~/.hunter not within the jaeger-cpp builddir. The built dependencies seem to have been dropped in .hunter/_Base/7128985/340d525/3420b24/Install, which of course jaeger-cpp knows to add to the CPATH and LIBRARY_PATH ... but tools using jaeger-cpp don't.

A make dependencies-install or something would probably help.

[ringerc]

Likely related:

• https://github.com/ruslo/hunter/issues/274

[ringerc]

Results in failures like

In file included from /usr/local/include/jaegertracing/baggage/RestrictionsConfig.h:21:0,
                 from /usr/local/include/jaegertracing/Config.h:21,
                 from /usr/local/include/jaegertracing/Tracer.h:28,
                 from myapp_file.cpp
/usr/local/include/jaegertracing/utils/YAML.h:24:27: fatal error: yaml-cpp/yaml.h: No such file or directory
 #include <yaml-cpp/yaml.h>
                           ^
compilation terminated.

The app embedding jaeger-cpp isn't using hunter, and cannot use hunter.

[isaachier]

So that is true. Hunter does not to global installs. That is the point, to allow for multiple different versions and builds of the same library. If you want to use the Jaeger C++ client without Hunter, the answer is pretty straightforward: look for the hunter_add_package/find_package calls and install those libs. Yes I should add proper documentation, but in lieu of that, this workaround should suffice.

[isaachier]

Also, don't forget HUNTER_ENABLED=0.

[ringerc]

Yeah, I spent most of yesterday figuring that out, hence the README draft I've submitted. I had to write or integrate a bunch of find_packsge modules too, but got there. I'll expand the README entry on Hunter a smidge. Then I'll add a cmake message on hunter-enabled build completion to tell users that they must use Hunter to link to the resulting jaeger-cpp. Then can probably close this.

[ringerc]

OK, so this is by design. You can't use jaeger-cpp's default Hunter build unless you also use Hunter.

Cool, document and done. I'll deal with this as part of the coming PR for the README.