Re: [ros-users] compile problem nodelet in OSX

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: User discussions
Date:  
To: User discussions
Subject: Re: [ros-users] compile problem nodelet in OSX
Sorry I wish I did have a solution … but I don't. However, I think in this case, a simple solution exists that allows the use of the macports version. For lion I think python 2.7 really should be the default.

I like homebrew, because it seems simpler to make the packages, but that method doesn't seem prime time yet.

I tried doing my own macport port once for OpenCV and it was complicated. By the time I got everything working, an official macport popped up and made all my efforts futile :)

Also, I removed all of the source installs in the rosdep.yaml files in electric and replaced them with macports. It had issues if I left both of them (macports and source) in there. So far the macports seem to be working fine. The only thing that isn't is OpenCV (again) so I tried homebrew, but that didn't work out so well for me. So I finally threw in the towel and installed opencv from source because I just really needed it. I wasn't going to go through the head ache of making my own macport again.

We really need to come up with a good solution but I am not sure what that is.

On Sep 2, 2011, at 2:44 PM, Brian Gerkey wrote:

> On Fri, Sep 2, 2011 at 10:37 AM, Kevin Walchko wrote:
>> I don't like installing source code I can't easily remove. That is why I put up with macports.
>
> hi Kevin,
>
> That's a fair point. But it's also an indictment of entire source
> rosdep approach to pulling in third-party stuff. Can you suggest an
> alternative?
>
> We need a way to install code that isn't available (or at least isn't
> available at the needed version, or in the needed configuration) from
> an OS's package manager.
>
>     brian.
> _______________________________________________
> ros-users mailing list
> 
> https://code.ros.org/mailman/listinfo/ros-users