tree b0c86c264864fa4843ad500752d348b1506f99eb
parent 6e2e623fa94bf26a3d80a6f310aba26028952278
author Junjie Bai <bai@in.tum.de> 1511801107 -0800
committer Facebook Github Bot <facebook-github-bot@users.noreply.github.com> 1511801228 -0800

Do not link against libpython when building python bindings

Summary:
our cmake build used to link against libpython.so with its absolute path (instead of -LSOME_LIB_PATH -lpython), so at runtime loader will think it needs the libpython.so at that specific path, and so load in an additional libpython.so, which causes the python binding built with one python installation not reusable by another (maybe on same machine or sometimes even not on same machine). The solution is quite simple, which is we don't link against libpython, leave all the python related symbols unresolved at build time, they will be resolved at runtime when imported into python.
Closes https://github.com/caffe2/caffe2/pull/1514

Reviewed By: dzhulgakov

Differential Revision: D6412405

Pulled By: bddppq

fbshipit-source-id: 9ff5b752ae3806bfac94085942f82d89c304c887