Revision history [back]

Sorry I guess the mechanism on this forum makes it difficult to vote on your thoughts, I can only accept one of you as answers, while there is actually no real answer - only discussion and ideas on this.

As to KruseT's answer, yes, I understand how people have been distributing, but my issue is that most users of our framework won't be people from robotics - we want this also for virtual agents, and that's where this issue comes from.

However, we also want to work with robotics people, so the problem is on finding something that can easily be placed between both the high-level agent developers, and the robot programmers.

That actually leads me to trininghost's answer. That is what I am trying to do now. As most of our work is based on C# running in OSX and Windows, I am trying to build a dotnet library in windows that uses roscpp to connect to ROS - that way I can build my framework to communicate through this dotnet dll, and other people can also build their modules in python or c++ and have everything connected anyway.

Currently I'm just having some troubles compiling the c++ code into a class, but I believe I'll eventually get through it, so then I just have to check if I can get this compiling in OSX (or plan B - make an OSX version).

I guess that although the installation stuff might be an issue, it would be really positive for us to use ROS as that makes it possible to collaborate with other people who are using it. So I'm keeping that as long as I can get the communication mechanisms running clean out of C#, we'll stick with it.

Then if I plan on distributing it to someone, I just have to figure out what do I actually need to include in my distribution, and pack everything up, even if it takes up several houndreds of MB.

Thanks to both for your considerations on this! Cheers.