[
https://issues.apache.org/jira/browse/MESOS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921216#comment-13921216
]
Till Toenshoff commented on MESOS-550:
--------------------------------------
I would like to propose a new approach that should solve this and other issues
(MESOS-1010, MESOS-1054 etc.). Instead of hardcoding the library paths and
enforcing their build, we could just as well allow the user to supply their
locations in case they dont exist in the standard lib-path e.g. via
"--with-zookeeper=/some-funky-folder/zookeeper_mt.a".
Within setup.py.in we then simply rely on these variables instead of hardcoding
the dependency paths.
This scheme could also be used for glog, protobuf and leveldb. libev may be a
bit hazardous as it needs specific build-settings enabled to properly function
with libprocess.
That way we do not have to build dependencies that are preinstalled and used in
an unmodified version within mesos or libprocess and still are able to properly
link against them in our language bindings. All of the above, I think, would
gain us more flexibility, shorter build-times - and - no immediate need to
bundle those dependencies.
Please let me know if you see any problem in this approach as I will start
implementing it.
> Python compilation fails when trying to compile without included zookeeper
> libs
> -------------------------------------------------------------------------------
>
> Key: MESOS-550
> URL: https://issues.apache.org/jira/browse/MESOS-550
> Project: Mesos
> Issue Type: Bug
> Components: python api
> Affects Versions: 0.12.0
> Reporter: Julien Eid
>
> Hey, I'm trying to compile Mesos against a separate Zookeeper install for
> packaging. The python setup.py only links against the .libs folder and
> doesn't check LDFLAGS for a different location for the lib.
> Relevant lines
> /src/python/setup.py: os.path.join(abs_top_builddir, zookeeper, '.libs',
> 'libzookeeper_mt.a')
--
This message was sent by Atlassian JIRA
(v6.2#6252)
