Jean-Michaël Celerier

Same here. Another workaround is to send a `scan le` command to bluetoothctl and SimpleBLE will start reporting the BLE devices too.

hmmm, ossia is already linking against the CMake target though ? here we do a find_package: https://github.com/ossia/libossia/blob/master/cmake/deps/concurrentqueue.cmake#L2 here we link against it: https://github.com/ossia/libossia/blob/master/src/ossia_setup.cmake#L171 there shouldn't be anything else to do...

could you share the concurrentqueue package's files ? I can check if the paths in the concurrentqueue-Config.cmake make sense

thanks! if you could share these following files too: /usr/local/lib/cmake/concurrentqueue/concurrentqueueConfig.cmake /usr/local/lib/cmake/concurrentqueue/concurrentqueueConfigVersion.cmake /usr/local/lib/cmake/concurrentqueue/concurrentqueueTargets.cmake

ok, so the package looks for ```cmake set_target_properties(concurrentqueue::concurrentqueue PROPERTIES INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include/concurrentqueue/" ) ``` but the package installs them in `${CMAKE_INSTALL_INCLUDEDIR}/${PROJECT_NAME}/moodycamel` ```cmake install( FILES blockingconcurrentqueue.h concurrentqueue.h lightweightsemaphore.h LICENSE.md DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/${PROJECT_NAME}/moodycamel )...

I added a hotfix in the ossia cmake code but ideally the fix would be upstream in concurrentqueue package

@thibaudk is this something you plan to work on during your phd ?

I think we should try to see with the authors of RT-Vamp sdk if they wouldn't want to port their SDK to avendish directly ? I have the impression that...