Specify library destination for install targets.

[mbharatheesha]

No description provided.

[Timple]

You should point to the tier4 remote.

[mbharatheesha]

I thought so as well and I will try doing it. Also, there are a few cosmetic improvements as well. For example,

• instead of adding the LIBRARY DESTINATION per line, everything can be consolidated with one install call
• the registration of the composable target can be improved to follow the standard convention of nebula::ros::<ComposableTarget> instead of just ComposableTarget
• Add example launch to show the use of composable nodes

I was concerned these points might come up once I target this to tier4 main. And that would take longer to merge. Instead, if we merge here and have binaries available, then the upstream PR can take its time while we could continue testing. And once upstream is ready, we can quickly update our binaries.

Of course another way to look at it is we could argue that we can keep minimal delta by introducing this change only for now and propose the additional points as future work.

Thoughts?

[mbharatheesha]

You should point to the tier4 remote.

Here it is:
tier4#261