Closed rdegnan closed 6 years ago
Currently yarpl headers are not installed because it is looking in the wrong directory. It was also assuming that a static library was being built with the hard coded ".a" extension, which fails when yarpl is built as a shared library.
Currently yarpl headers are not installed because it is looking in the wrong directory. It was also assuming that a static library was being built with the hard coded ".a" extension, which fails when yarpl is built as a shared library.