Arch Linux User Repository

The current release of OMPL (1.4.2) is incompatible with the version of Boost Arch now ships (1.71.0). That means that this package will not build if Boost is fully updated on your system.

The maintainers say that a new release fixing this bug (and others) should be out "soon" (https://github.com/ompl/ompl/issues/681). Unless users prefer that I update the PKGBUILD with a workaround to build 1.4.2 against Boost 1.71.0 (which can be done), I plan to wait for this release to update the PKGBUILD. I will also switch the package source from BitBucket to Github at this time, as the OMPL project has moved its active development to Github.

If you use this package and would prefer a patch before the 1.5.0 release, please comment saying so!

The current release of OMPL (1.4.2) is incompatible with the version of Boost Arch now ships (1.71.0). That means that this package will not build if Boost is fully updated on your system.

The maintainers say that a new release fixing this bug (and others) should be out "soon" (https://github.com/ompl/ompl/issues/681). Unless users prefer that I update the PKGBUILD with a workaround to build 1.4.2 against Boost 1.71.0 (which can be done), I plan to wait for this release to update the PKGBUILD. I will also switch the package source from BitBucket to Github at this time, as the OMPL project has moved its active development to Github.

If you use this package and would prefer a patch before the 1.5.0 release, please comment saying so!

@acxz: Great, sounds good. I'm working on a deadline right now, but I can also spend some time trying to get py++ working after that (6/5 or so).

@wbthomason Thanks for your response. I see. I recently started maintaining the omplapp package so I will try to fix things (maybe even trying to fix py++) and keep you updated on how things work out.

@acxz: I believe that's an upstream issue. I can reproduce your error, but given that py++ (once installed) also can't actually be imported by python2 (at least on my system), I suspect an issue with the py++ package. I have tried forcing the build by modifying the OMPL PKGBUILD to include -DOMPL_BUILD_PYBINDINGS=ON, but this also fails. It could be worth trying the (re)generation instructions here: https://ompl.kavrakilab.org/python.html. If those work, let me know and I can see if there's a good way to tweak the PKGBUILD to use them if py++ is installed.

I have py++ installed however, during the build process ompl was not able to recognize the optional dependency. Here is my build process, https://pastebin.com/z4NkxQKB, along with my optional dependency installed: (1/1) installing ompl [---------------------------------------] 100% Optional dependencies for ompl py++: Python binding [installed] ode: Plan using the Open Dynamics Engine [installed] eigen: For an informed sampling technique [installed]

I understand this might be an upstream issue or an issue with the py++ package, but thought I would post this here as well.

Updated to 1.4.2

Updated to 1.4.1

Sounds good, thanks! And thank you for your work creating and maintaining the package.

Sure, go ahead and take over maintenance.

@Sandmann: If you're no longer using OMPL, I'd be happy to take over maintenance of this package. There've been two version releases since this was last updated; I've manually updated using my own PKGBUILDs, but it would be nice for the official package to be up to date as well.