-
Notifications
You must be signed in to change notification settings - Fork 60
generate java code for actions in same source workspace #71
Comments
Hi @fmessmer , I sometimes had issuies because the generated However I can tell that message generation works fine in kinetic when building them with I'll take a closer look at this when I'm back in the office on Monday... |
Thanks for your reply @exo-core I've prepared a small demo repo that we could use for discussion: Some details about my setup:
What I'm trying to do:
|
Experimenting some more: Test1: https://github.com/fmessmer/helloworld_rosjava_messages/tree/a45530618642966b327a0e36608a7328a4023a51: Test2: fmessmer/helloworld_rosjava_messages@26a4b31 So it seems, it's not the messages/actions being located in the same workspace as |
Hi @fmessmer, I've tried to reproduce your example. What I did:
After that I checked What am I missing? Do we need to have a copy of that file in another directory? |
@exo-core let me have another look at this...but it won't be before Wednesday |
hmm, I can't get it to work...but I don't think it's (just) the message generation for actions... here is what I found out:
by doing so, everything happens in I just can't figure out why it is so difficult to tell one more thing: I appreciate any help/pointer! |
I think I found a solution for my problem.... |
in case anyone is interested... |
I'm very happy to see the PRs provided by @exo-core wrt. code generation for action files...
we've recently been hacking around this, too, without finding a satisfying solution
the current
kinetic
branch works with actions which are already released (although, I think this is because the msg files generated for each action can be found in themsg
folder within the respective pkg under/opt/ros
- thus the java classes get generated by the sameMessageGeneration
doing the topicmsg
files)still, I'm having trouble generating code for actions which are defined in packages which are located in the same source workspace as
rosjava_bootstrap
,genjava
& cowe also need this to work for our CI (travis)...using
ros-industrial/industrial_ci
where everything is compiled in a single workspace (in whichsrc
is read-only)I'm still playing around with it a bit more and try to provide a
rosinstall
file to reproduce my usecase.@exo-core @jubeira
what is your experience? have you used it this way?
The text was updated successfully, but these errors were encountered: