Re: [C++] Static/Shared Linkage in CMakeLists.txt

No worries! I appreciate the information. I'm currently focusing on improving the CMake side, so I’ll probably stick with that for now. But it’s good to know that there's an alternative approach with Meson. Btw, there is actually a cmake variable BUILD_SHARED_LIBS

Re: [C++] Static/Shared Linkage in CMakeLists.txt

I have been a bit hesitant to respond as I don't want to hijack this thread, but if you: * Are OK not using CMake * Are OK with an "unofficially supported" build system generator in Arrow * Do not require every single feature of the CMake build system You _might_ also be interested in the Me

Re: [C++] Static/Shared Linkage in CMakeLists.txt

HI, Ah, you only focus on our CMake configuration, right? (You don't focus on downstream users, right?) And you want to simplify our CMake configuration, right? We can do it. Let's open a new issue and PR for it. Thanks, -- kou In "Re: [C++] Static/Shared Linkage in CMa

Re: [C++] Static/Shared Linkage in CMakeLists.txt

IC=ON, we can > build both of shared version and static version in the same > build process. Am I missing something? > > > Thanks, > -- > kou > > In > "Re: [C++] Static/Shared Linkage in CMakeLists.txt" on Tue, 3 Jun 2025 > 16:37:42 +0800, > Eddie Ch

Re: [C++] Static/Shared Linkage in CMakeLists.txt

LD_STATIC=ON, we can build both of shared version and static version in the same build process. Am I missing something? Thanks, -- kou In "Re: [C++] Static/Shared Linkage in CMakeLists.txt" on Tue, 3 Jun 2025 16:37:42 +0800, Eddie Chang wrote: > Hi Kou, > > Building bot

Re: [C++] Static/Shared Linkage in CMakeLists.txt

used for shared > >> linking and static linking? For example, you want to use > >> Parquet::parquet for shared linking and static linking, > >> right? > >> > >> In my understanding, we can't do it with CMake. We need to > >> specify "

Re: [C++] Static/Shared Linkage in CMakeLists.txt

Thanks, -- kou In "RE: Re: [C++] Static/Shared Linkage in CMakeLists.txt" on Tue, 3 Jun 2025 14:49:02 +0800, Eddie Chang wrote: > Just to clarify, my suggestion was assuming that each build only produces > either static or shared libraries, not both. > > Given that a

RE: Re: [C++] Static/Shared Linkage in CMakeLists.txt

add_library(). > See also: > https://cmake.org/cmake/help/latest/command/add_library.html#normal > > Thanks, > -- > kou > > In > "[C++] Static/Shared Linkage in CMakeLists.txt" on Tue, 3 Jun 2025 13:45:36 +0800, > Eddie Chang wrote: > > > He

Re: [C++] Static/Shared Linkage in CMakeLists.txt

create a CMake target by add_library(). See also: https://cmake.org/cmake/help/latest/command/add_library.html#normal Thanks, -- kou In "[C++] Static/Shared Linkage in CMakeLists.txt" on Tue, 3 Jun 2025 13:45:36 +0800, Eddie Chang wrote: > Hello everyone, I've notice

[C++] Static/Shared Linkage in CMakeLists.txt

Hello everyone, I've noticed that in our CMakeLists.txt files, we have multiple instances where we conditionally select either the static or shared version of a linked target based on a cache variable such as ARROW_BUILD_SHARED. For example, the following pattern appears in several places: if(