Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make odom child frame parameterizable + some CMake #69

Merged
merged 3 commits into from
Apr 9, 2020
Merged

Make odom child frame parameterizable + some CMake #69

merged 3 commits into from
Apr 9, 2020

Conversation

jmirabel
Copy link
Contributor

@jmirabel jmirabel commented Apr 6, 2020

The install path change is related to 576bf36#r38313060

@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 6, 2020

Please, don't merge as this is WIP.

@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 6, 2020

This is not WIP anymore.

@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 6, 2020

On packages that depends on this one, I now have

CMake Error at /home/jmirabel/devel/agimus/install/lib/cmake/dynamic_graph_bridge/dynamic_graph_bridgeTargets.cmake:132 (message):
  The imported target "dynamic_graph_bridge::geometric_simu" references the
  file

     "/home/jmirabel/devel/agimus/install/bin/geometric_simu"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

     "/home/jmirabel/devel/agimus/install/lib/cmake/dynamic_graph_bridge/dynamic_graph_bridgeTargets.cmake"

  but not all the files it references.

@nim65s Do you know how to fix that ?

@nim65s
Copy link
Contributor

nim65s commented Apr 6, 2020

In dynamic_graph_bridgeTargets.cmake I have:

# Create imported target dynamic_graph_bridge::geometric_simu
add_executable(dynamic_graph_bridge::geometric_simu IMPORTED)

Looking at the doc, I guess we have to specify the IMPORTED_LOCATION for this target.

But do you know why ROS wants the binaries to go to share instead of bin ?

@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 6, 2020

Looking at the doc, I guess we have to specify the IMPORTED_LOCATION for this target.

I tried but couldn't get this to work.

But do you know why ROS wants the binaries to go to share instead of bin ?

I think by default, the binaries are installed in lib/package/... but it is also possible to install them in share. I think they do this because they want users to launch them using rosrun. In our case, launch geometric_simu outside ROS does not make much sense. I don't even know if it works.

@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 6, 2020

@nim65s At the moment, the target geometric_simu isn't used outside of the project. Do you mind if I remove the export and leave it to you to make the export work ? i can open an issue to leave a reminder.

@nim65s
Copy link
Contributor

nim65s commented Apr 6, 2020

Sure, go ahead :)

@nim65s
Copy link
Contributor

nim65s commented Apr 6, 2020

You will just have to provide a way to reproduce your issue :)

@olivier-stasse
Copy link
Member

olivier-stasse commented Apr 7, 2020

In ROS a binary executable_name is suppose to go in :

${CMAKE_INSTALL_PREFIX}/lib/package_name/extecutable_name

To make it available outside the ROS real, I either copy or create a link to binary in:

${CMAKE_INSTALL_PREFIX}/bin

@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 7, 2020

To make it available outside the ROS real, I either copy or create a link to binary in:

${CMAKE_INSTALL_PREFIX}/bin

This does not make sense for geometric_simu

@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 7, 2020

I updated the PR accordingly and opened #70, though I don't think we should care about exporting executables.

@nim65s
Copy link
Contributor

nim65s commented Apr 7, 2020

I don't think we should care about anything as long as it's not required. And here, the export is not required for anything (yet).

But for the sport, I'd like to understand how to solve #70 :)

@olivier-stasse
Copy link
Member

Out of curiosity: was the export creating a bug ?

@olivier-stasse olivier-stasse merged commit 46f6d30 into stack-of-tasks:devel Apr 9, 2020
@jmirabel
Copy link
Contributor Author

jmirabel commented Apr 9, 2020

Out of curiosity: was the export creating a bug ?

Have a look at #70.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants