Description
Most of our third-party dependencies are included in the project and statically linked into our resulting binaries and libraries. We would like to enable building Mesos but using system installed dependencies instead.
In certain circumstances this is more difficult because we've actually needed to "patch" these libraries (either for C++11 or to alter semantics).
Rather than eliminating our internal copies of these third-party dependencies the first step should be to just enable using external (i.e., system installed) dependencies. We already do this for ZooKeeper by allowing people to use the --without-included-zookeeper flag during compilation. We should do this for other libraries as well. In fact, for the libraries that we have not patched (and even for some that we have patched) we should check to see if an appropriate system installed dependency exists and preferentially use that unless --with-included-dependency is explicitly used.
Note that this issue represents a stepping stone to removing our third-party dependencies from our repository.
Attachments
Attachments
Issue Links
- blocks
-
MESOS-1167 Update system check (boost)
- Resolved
-
MESOS-1168 Update system check (zookeeper)
- Resolved
-
MESOS-1169 Update system check (distribute)
- Resolved
-
MESOS-1170 Update system check (glog)
- Resolved
-
MESOS-1173 Update system check (picojson)
- Resolved
-
MESOS-1174 Update system check (protobuf)
- Resolved
-
MESOS-1175 Update system check (http-parser)
- Resolved
- incorporates
-
MESOS-550 Python compilation fails when trying to compile without included zookeeper libs
- Resolved
-
MESOS-1072 Update system check (python boto)
- Resolved
- is related to
-
MESOS-899 make install does not install python libraries
- Resolved
-
MESOS-1171 Update system check (gmock)
- Resolved
-
MESOS-1172 Update system check (libev)
- Resolved
- relates to
-
MESOS-2537 AC_ARG_ENABLED checks are broken
- Resolved