Dependency on clangdev

[SylvainCorlay]

The clangdev conda-forge recipe is a multi-output recipe, which creates the following packages:

clangdev
libclang-cpp13(13 is the soversion) and libclang-cpp (only symlinks)
libclang and libclang13 (13 is the soversion) and libclang (only symlinks)
clang-16 (16 is the current major version) and clang (symlinks)
clangxx
clang-format-16 (16 is the current major version) and clang-format (only symlinks)
clang-tools
python-clang

It seems that clangdev depends on clangxx etc, which are the onces having run exports, so we should probablly depend on clangxx instead of clangdev.

[vgvassilev]

Which is the one which installs libclangInterpreter.a or libclangInterpreter.so?

[SylvainCorlay]

Clangdev is the correct dependency at build time (it has the CMake files and static libraries).

But we still need clang at runtime apparently.

Why do you ask about the .a files? Do we link statically with libClangInterpreter?

[SylvainCorlay]

Btw @vgvassilev, the Binder link of the readme works!

[vgvassilev]

Clangdev is the correct dependency at build time (it has the CMake files and static libraries).

But we still need clang at runtime apparently.

Hm, for which part? Is it because of the clang resource headers?

Why do you ask about the .a files? Do we link statically with libClangInterpreter?

We link statically or dynamically depending on what we have selected with BUILD_SHARED_LIBS.

Btw @vgvassilev, the Binder link of the readme works!

Awesome!

[SylvainCorlay]

Hm, for which part? Is it because of the clang resource headers?

I think it complains about not having an engine. I need to check again.

We link statically or dynamically depending on what we have selected with BUILD_SHARED_LIBS.

I meant do we link statically or dynamically with our dependencies (such as libclang)? BUILD_SHARED_LIBS defines whether we produce shared or static libraries, presumably.

[vgvassilev]

Hm, for which part? Is it because of the clang resource headers?

I think it complains about not having an engine. I need to check again.

Ok, thanks!

We link statically or dynamically depending on what we have selected with BUILD_SHARED_LIBS.

I meant do we link statically or dynamically with our dependencies (such as libclang)? BUILD_SHARED_LIBS defines whether we produce shared or static libraries, presumably.

We do not depend on libclang. If BUILD_SHARED_LIBS=On clang-repl will obey and link dynamically with the so files as the rest of llvm. Am I misunderstanding your question?

[SylvainCorlay]

We link statically or dynamically depending on what we have selected with BUILD_SHARED_LIBS.

I meant do we link statically or dynamically with our dependencies (such as libclang)? BUILD_SHARED_LIBS defines whether we produce shared or static libraries, presumably.

We do not depend on libclang. If BUILD_SHARED_LIBS=On clang-repl will obey and link dynamically with the so files as the rest of llvm. Am I misunderstanding your question?

When building xeus-cpp, BUILD_SHARED_LIBS will determine whether we build static or dynamic libraries for libxeus-cpp.

[vgvassilev]

In pull request #58 we have started depending on libCppInterOp. I'd consider this issue somewhat resolved.