Skip to content

Commit 36ffe6b

Browse files
adolfoapolloniLyle Johnson
authored andcommitted
fixed data-generator and build instructions (#67)
fixed code snippet so it includes instructions to build polysync-data-generator no longer instructs the user to comment out the include directories statement
1 parent 57adc64 commit 36ffe6b

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

PolysyncLidarTranslator/README.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,11 @@ $ cp PolySync-Core-CPP-Examples/PolysyncLidarTranslator/polysync_lidar_translato
3333
Make sure that in the "Build" section of the CMakeLists file for your PolysyncLidarTranslator project are uncommented. All other lines in the "Build" section should be commented.
3434

3535
```bash
36+
## include_directories(include)
37+
include_directories(
38+
${catkin_INCLUDE_DIRS}
39+
)
40+
3641
## Declare a C++ executable
3742
add_executable(polysync_lidar_translator_node src/polysync_lidar_translator_node.cpp)
3843

@@ -73,7 +78,13 @@ $ ./BridgeNode -t ps_lidar_points_msg
7378
Start up PolySync data generator in another terminal.
7479

7580
```bash
76-
$ polysync-data-generator-c
81+
$ git clone [email protected]:PolySync/PolySync-Core-CPP-Examples.git
82+
$ cd PolySync-Core-CPP-Examples/DataGenerator
83+
$ sudo apt-get install libglib2.0-dev # this is required for this example to build, documented in the examples README.md file
84+
$ mkdir build && cd build
85+
$ cmake ..
86+
$ make
87+
$ ./polysync-data-generator-cpp
7788
```
7889

7990
Run the translator project you just built. The executable should be in the devel folder of your catkin workspace.

0 commit comments

Comments
 (0)