You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this seems to make life simpler at first, these dependencies should be installed separately.
I am unfamiliar with how deployment goes on Windows systems but both Linux and OSX has package managers where these dependencies can be grabbed from. Dragging around copies of someone else's software is not too elegant. The current solution locks one in with the specific version of boost which if used in conjunction with other libraries (a ROS wrapper around a controller for instance) collisions would be very likely to occur.
My proposed solution is to move the external dependencies to a different repository which would only be downloaded if the person is on Windows, Linux and OSX systems can use the system default (apt or brew installated) versions of these libraries.
The text was updated successfully, but these errors were encountered:
bmagyar
changed the title
Shipping custom version of boost and Eigen?
[joss-review] Shipping custom version of boost and Eigen?
Dec 12, 2017
Like the others, since I've already merged the changes back into the master, unfortunately I can't put in a pull request. I'll reference the commits so you can still see how we addressed the issues. I'll make sure for the remaining work, I keep it in our joss_issues branch so I can make a pull request and be better at collaboration.
Good call on this one. In order to address this issue, we removed the external folder containing eigen and boost and moved them over to a different repository (https://gitlab.com/powan/CRexternal). To check for eigen and boost, we updated CMakeLists.txt to automatically find the needed packages. We also added eigen and boost to the docker image used as our CI runner. Instructions were adjusted for the new approach.
While this seems to make life simpler at first, these dependencies should be installed separately.
I am unfamiliar with how deployment goes on Windows systems but both Linux and OSX has package managers where these dependencies can be grabbed from. Dragging around copies of someone else's software is not too elegant. The current solution locks one in with the specific version of boost which if used in conjunction with other libraries (a ROS wrapper around a controller for instance) collisions would be very likely to occur.
My proposed solution is to move the external dependencies to a different repository which would only be downloaded if the person is on Windows, Linux and OSX systems can use the system default (apt or brew installated) versions of these libraries.
The text was updated successfully, but these errors were encountered: