Wiki » History » Version 11
J.-C. Seele, 09/28/2010 03:15 PM
| 1 | 1 | S. Wrede | h1. Wiki |
|---|---|---|---|
| 2 | 1 | S. Wrede | |
| 3 | 1 | S. Wrede | h2. Dependencies |
| 4 | 1 | S. Wrede | |
| 5 | 1 | S. Wrede | * RSC, see RSC Project at Code.CoR-Lab |
| 6 | 1 | S. Wrede | * boost::uuid (can be installed from GAR installer, contrib/boost.uuid or is contained in newer boost versions) |
| 7 | 1 | S. Wrede | * boost::threadpool (can be installed from GAR installer, contrib/boost.threadpool, will probably be replaced by RSC threadpool implementation) |
| 8 | 1 | S. Wrede | * spread for spread port (lucid ubuntu package does not work as it is still an old version, can be installed through GAR installer, contrib/spread) |
| 9 | 3 | J. Wienke | * Google protocol buffers (lucid ubuntu package works, can also be installed from GAR installer, contrib/protobuf) |
| 10 | 4 | J. Wienke | * Doxygen for documentation generation (ubuntu package) |
| 11 | 4 | J. Wienke | * lcov for coverage report (ubuntu package) |
| 12 | 6 | J.-C. Seele | |
| 13 | 6 | J.-C. Seele | |
| 14 | 11 | J.-C. Seele | h2. Questions/Annotations concerning the Tutorials (by Jens) |
| 15 | 6 | J.-C. Seele | |
| 16 | 6 | J.-C. Seele | |
| 17 | 6 | J.-C. Seele | h3. Publish Tutorial: |
| 18 | 6 | J.-C. Seele | |
| 19 | 10 | J.-C. Seele | *Class: rsb::Publisher* |
| 20 | 6 | J.-C. Seele | |
| 21 | 11 | J.-C. Seele | * What is the Publisher doing? Seems to be clear, but I have no *real* clue. What does the communication 'pipeline' looks like? |
| 22 | 11 | J.-C. Seele | * I do not understand the typedefs, because I am not into C++ very well. So I have no clue, how to start the tutorial and what is meant by Pointer and Datapointer (in comparison to each other). Maybe the Pointer points to the Publisher and the DataPointer to the data of it?! But afterall, why do I need Pointers? It would be nice, if these two typedefs would be explained. E.g. what they do, where the difference is, what you can use them for. |
| 23 | 11 | J.-C. Seele | * I think I would not have the idea to use the reset() method of boost_shared_ptr to initialize the publisher. Same holds for the event. |