Have Bazel rules for creating shared libraries
- Lenguaje dominante
- C++
- Estrellas
- 18.1k
- Forks
- 3.2k
- Merge medio
- 20 h 36 min
- PR fusionados (30 d)
- 1
Descripción
### Describe the issue
it is possible to build shared libraries with cmake with BUILD_SHARED_LIBS=ON
AFAIK, it is not possible to create them with Bazel.
According to https://ltekieli.com/linux-shared-libraries-with-cmake-and-bazel/
it requires additional cc_shared_library rules to setup up the needed dynamic deps.
The reason why it is important to have this feature setup, it is to allow to build other projects linking with abseil that are exclusively using bazel.
For example, https://github.com/google/tcmalloc is such project.
It currently statically links with abseil. This makes it impossible to build tcmalloc as a shared library and use the resulting so lib file in a project also linking with cmake generated Abseil libraries without breaking the ODR rule.
Being able to build Abseil shared libraries within Bazel is a prerequisite to be able to build tcmalloc shared libraries that can be used with projects already dynamically linking with Abseil.
### Steps to reproduce the problem
there is no cc_shared_library rules in abseil BUILD files or if it is possible to create shared libraries, it is not well documented.
I could not find anything on the topic.
### What version of Abseil are you using?
20240722 LTS
### What operating system and version are you using?
ArchLinux kernel 6.10.4
### What compiler and version are you using?
gcc version 14.2.1 20240805 (GCC)
### What build system are you using?
bazel 7.2.1
### Additional context
_No response_
Guía de contribución
Línea de trabajo
Look at the existing BUILD files to understand the current cc_library rules. Research how cc_shared_library works in Bazel and examine the linked blog post for guidance. The goal is to add rules that produce shared libraries compatible with projects like tcmalloc, ensuring they don't break ODR when used with CMake-built Abseil.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- cpp
- Área
- build-system
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 30/100