-
Notifications
You must be signed in to change notification settings - Fork 443
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for dual returns in sample ROS driver
Data from the second return will be published as separate point cloud and image topics when configured. The launch file now takes an additional `udp_profile_lidar` parameter to set the packet profile on startup. Other changes: * The supported vcpkg version has been updated to 2021.05.12 * Windows Python extensions are now built with VS 2017, per the packaging guidelines * Improved heuristics for detecting lidar data in pcap files in the Python sdk
- Loading branch information
Showing
109 changed files
with
2,796 additions
and
2,266 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,50 @@ | ||
# Attempt to deal with gtest cmake differences across platforms | ||
|
||
function(find_gtest) | ||
# use system find module in this scope | ||
set(CMAKE_MODULE_PATH "") | ||
|
||
find_package(GTest QUIET) | ||
# using the cmake-provided find module succeeds, but the resulting GTest::GTest and | ||
# GTest::Maintargets cause link errors with vcpkg 2021.05.12 on macos. Try CONFIG-only first | ||
find_package(GTest CONFIG QUIET) | ||
|
||
if(GTEST_FOUND) | ||
find_package_handle_standard_args(GTest DEFAULT_MSG GTEST_LIBRARY) | ||
else() | ||
message(STATUS "Looking for GTest source in /usr/src/gtest") | ||
add_subdirectory("/usr/src/gtest" gtest) | ||
add_library(GTest::GTest ALIAS gtest) | ||
add_library(GTest::Main ALIAS gtest_main) | ||
message(STATUS "Found GTest source") | ||
if (GTest_CONFIG AND TARGET GTest::gtest AND TARGET GTest::gtest_main) | ||
find_package_handle_standard_args(GTest DEFAULT_MSG GTest_CONFIG) | ||
return() | ||
endif() | ||
|
||
# next, try using a find module. Requires temporarily turning off REQUIRED to avoid failing at the | ||
# call to find_package() | ||
set(GTest_FIND_REQUIRED_SAVED ${GTest_FIND_REQUIRED}) | ||
set(GTest_FIND_REQUIRED 0) | ||
find_package(GTest MODULE QUIET) | ||
set(GTest_FIND_REQUIRED ${GTest_FIND_REQUIRED_SAVED}) | ||
|
||
if (GTEST_FOUND) | ||
find_package_handle_standard_args(GTest DEFAULT_MSG GTEST_LIBRARY GTEST_MAIN_LIBRARY) | ||
|
||
# aliases to cmake >= 3.20 targets. More portable than IMPORTED_GLOBAL | ||
# https://cmake.org/cmake/help/v3.22/module/FindGTest.html#imported-targets | ||
if(NOT TARGET GTest::gtest) | ||
add_library(GTest::gtest INTERFACE IMPORTED) | ||
target_link_libraries(GTest::gtest INTERFACE GTest::GTest) | ||
endif() | ||
if(NOT TARGET GTest::gtest_main) | ||
add_library(GTest::gtest_main INTERFACE IMPORTED) | ||
target_link_libraries(GTest::gtest_main INTERFACE GTest::Main) | ||
endif() | ||
|
||
return() | ||
endif() | ||
|
||
# finally, try src location for libgtest-dev for debian-based distros where | ||
# the find module appears to be broken (xenial, bionic) | ||
find_path(GTEST_ROOT CMakeLists.txt "/usr/src/gtest") | ||
find_package_handle_standard_args(GTest DEFAULT_MSG GTEST_ROOT) | ||
add_subdirectory(${GTEST_ROOT} gtest) | ||
add_library(GTest::gtest ALIAS gtest) | ||
add_library(GTest::gtest_main ALIAS gtest_main) | ||
|
||
endfunction() | ||
|
||
find_gtest() |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,7 @@ | |
|
||
#pragma once | ||
|
||
#include <Eigen/Dense> | ||
#include <Eigen/Core> | ||
#include <vector> | ||
|
||
#include "ouster/types.h" | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.