News for hackers. Stuff that matters.

A comment on Interactive workflows for C++ with Jupyter. Parent comment

Re:Interactive workflows for C++ with Jupyter by beojan on Thursday November 30, 2017 @04:07AM (#15814402)
It really doesn't matter what build system other libraries use. If you use CMake, you just need to use `find_package` directives (https://cmake.org/cmake/help/v3.10/manual/cmake-packages.7.h...) to integrate third party libraries (which should be separately installed in the system).

It only seems difficult if you're stuck in the mentality of shipping all your dependencies with your source code and statically linking everything. C and C++ libraries actually care about maintaining API (and usually ABI) compatibility, so you don't have to ensure you have a specific version of dependencies.

[ Parent | on HN ]
Re:Interactive workflows for C++ with Jupyter by AstralStorm on Thursday November 30, 2017 @10:18AM (#15816364)
Come on, you cannot even link C++ shared libraries from different version of standard library, potentially also compiler. ABI compatibility in C++ does not exist.

In C, you still had incompatibilities between compilers. (MS fastcall convention and declspec come to mind...)

[ Parent | on HN ]
Re:Interactive workflows for C++ with Jupyter by beojan on Friday December 01, 2017 @09:15AM (#15823915)
There's better ABI compatibility than in the languages where you have to rebuild after every minor version bump. The C++ standard library version (and to some extent, the compiler) should be considered part of the platform.
[ Parent | on HN ]