Couple of quick questions.
From what I've seen, it looks like you can upgrade your stacks to catkin and build/release from source with catkin (releases have to be catkin enabled?). Alternatively if your stack is not yet catkin enabled, you can still apt-get or catkin build/install dependencies, then use the old 'in place' build via rosco and rosmake to compile your sources. Am I tuned in to the master plan correctly?
Rospack is now using your rewrite brian? i.e.
- hg:
local-name: rospack
Rosinstall - if it's a permanent feature, it would be good if it detected the presence of catkin and made that symbolic link 'catkin/toplevel.cmake -> CMakeLists.txt'.
What is the situation with rx tools and ros-fuerte-swig-wx? I'm sudo apt-get'ing ubuntu's swig at the moment and that is sufficient to compile. I suspect this is in the works as mentioned on the migration page (it's a source rosdep?).
I'm going to hit the cross-compiling over the next couple of days, so I'll hit the tracker with patches for you.
Cheers,
Daniel.
On 4 February 2012 01:55, Jack O'Quin
<jack.oquin@gmail.com> wrote:
>> I'm working on rosinstall at the moment. This works fine except for the
>> case where rospack hasn't been built yet. I'll work in some helpful
>> message.
>
> rosinstall 0.5.25 is released and does the above. Please give it a whirl
> and let me know if it works.
Another problem: setup.sh creates a broken $PATH entry for Fuerte:
export ROS_ROOT=/opt/ros/fuerte/share/ros
export PATH=$ROS_ROOT/bin:$PATH
There is no /opt/ros/fuerte/share/ros/bin. Apparently,
/opt/ros/fuerte/bin is the correct directory (but only for Fuerte).
--
joq