+1 on installing 3rdpart packages. I used to build a C++ Mesos framework with local/system packages (protobuf, boost), but protobuf failed because of header file backward compatibility. I have to go through the Mesos build to include 3rdpart packages and got following Makefile: https://github.com/klaus1982/mesos-ping/blob/master/Makefile
It'll be great if we can ship the 3rdpackages when installing Mesos. ---- Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform OpenSource Technology, STG, IBM GCG +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me On Wed, Jan 20, 2016 at 6:03 AM, Kapil Arya <ka...@mesosphere.io> wrote: > Hi All, > > I wanted to get your opinion on installing the 3rdparty packages glog, > protobuf, boost and picojson[1] when installing Mesos itself. These > packages are required to build Mesos modules. > > Currently, a module write has to manually install these 3rdparty > packages, either system-wide or locally, and update the compilation > flags such as CPPFLAGS to point to the installation which is > error-prone. Further, one might have a system-wide installation with > the wrong package version, causing even more headache. > > The proposal here is to install these 3rdparty packages when > installing Mesos. To avoid any conflicts with system-wide or local > installation, we can install them as follows: > > ${PREFIX}/include/mesos/3rdparty -- for header files > ${PREFIX}/<LIBDIR>/mesos/3rdparty -- for library files (LIBDIR can be > lib or lib64 depending upon the installation) > > where PREFIX refers to the `--prefix` flag for Mesos configure script. > > We would then update `mesos.pc` with the correct flags so that a > module write can simply use `pkg-config` to get all the required > flags. > > I have created an issue > https://issues.apache.org/jira/browse/MESOS-4434 to track this. > > Best, > Kapil > > > [1]: picojson is currently installed in ${PREFIX}/include. See > https://issues.apache.org/jira/browse/MESOS-3909 >
