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

resolve path of message file and include dirs in installspace at runtime (ros/catkin#490) #32

Merged
merged 1 commit into from
Aug 3, 2013

Conversation

dirk-thomas
Copy link
Member

No description provided.

@tfoote
Copy link
Member

tfoote commented Aug 3, 2013

+1

dirk-thomas added a commit that referenced this pull request Aug 3, 2013
resolve path of message file and include dirs in installspace at runtime (ros/catkin#490)
@dirk-thomas dirk-thomas merged commit a5d9faa into groovy-devel Aug 3, 2013
@dirk-thomas dirk-thomas deleted the relocatable branch August 3, 2013 17:00
@jbohren
Copy link
Member

jbohren commented Sep 13, 2013

Now that the paths in ${${package}_MESSAGE_FILES} are relative, what is the proper way to actually get the absolute path to the file?

Is there a better way than the following?:

set(MSG_FILES)                                            
foreach(FILE_REL ${${package}_MESSAGE_FILES})             
  list(APPEND MSG_FILES ${${package}_DIR}/../${FILE_REL}) 
endforeach()                                              

@jbohren
Copy link
Member

jbohren commented Sep 13, 2013

Also, it looks like ${${package}_SERVICE_FILES} is still an absolute path in genmsg 4.22.

@dirk-thomas
Copy link
Member Author

Yes, that would be the right way to construct the absolute paths.

Good catch regarding the service files. I have fixed them in the recent commit.

severin-lemaignan referenced this pull request in severin-lemaignan/robotpkg Aug 18, 2014
Changes since 0.4.20:

0.5.3 (2014-07-10)
------------------
* escape messages to avoid CMake warning (`#49
<https://github.com/ros/genmsg/issues/49>`_)

0.5.2 (2014-05-07)
------------------
* refactor to generate pkg-msg-paths.cmake via configure_file() instead of empy
(`#43 <https://github.com/ros/genmsg/issues/43>`_)
* fix python 3 compatibility (`#45 <https://github.com/ros/genmsg/issues/45>`_)
* remove debug message introduced in 0.5.1 (`#42
<https://github.com/ros/genmsg/issues/42>`_)

0.5.1 (2014-03-04)
------------------
* add check for changed message dependencies (`#41
<https://github.com/ros/genmsg/issues/41>`_)

0.5.0 (2014-02-25)
------------------
* remove usage of debug_message() (`#40
<https://github.com/ros/genmsg/issues/40>`_)

0.4.24 (2014-01-07)
-------------------
* python 3 compatibility (`#36 <https://github.com/ros/genmsg/issues/36>`_,
`#37 <https://github.com/ros/genmsg/issues/37>`_)
* add support for ROS_LANG_DISABLE env variable (`ros/ros#39
<https://github.com/ros/ros/issues/39>`_)
* fix installation of __init__.py from devel space (`#38
<https://github.com/ros/genmsg/issues/38>`_)

0.4.23 (2013-09-17)
-------------------
* fix installation of __init__.py file for packages where name differs from
project name (`#34 <https://github.com/ros/genmsg/issues/34>`_)
* rename variable 'config' to not collide with global variable (`#33
<https://github.com/ros/genmsg/issues/33>`_)
* fix service files variable to only contain package relative paths (`#32
<https://github.com/ros/genmsg/issues/32>`_)

0.4.22 (2013-08-21)
-------------------
* make genmsg relocatable (`ros/catkin#490
<https://github.com/ros/catkin/issues/490>`_)
* add warning in case generate_messages() is invoked without any messages and
services (`#31 <https://github.com/ros/genmsg/issues/31>`_)
* check if files have been generated before trying to install them (`#31
<https://github.com/ros/genmsg/issues/31>`_)

0.4.21 (2013-07-03)
-------------------
* check for CATKIN_ENABLE_TESTING to enable configure without tests
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.

3 participants