Re: C++ building question

You can create two different build directories: release and debug. Then you run cmake $ARROW_ROOT on the two different folders. On Fri, 22 Nov 2024 at 15:53 Carl Godkin wrote: > Hi, > > I'm using the arrow library with parquet version 18.0.0 on Windows and > Linux from C++. > > For development

Re: C++ building question

Hi Felipe, Thanks for your reply. I understand that and already build in two sub-directories of cpp called `win64_build` and `win64_debug`. But the libraries end up with the same names still so I can install them to the same place. In other words, when I do this: cmake -G "NMake Makefiles" ^

Re: C++ building question

Hi, -DARROW_OUTPUT_NAME_SUFFIX=d with the following patch will work: diff --git a/cpp/cmake_modules/BuildUtils.cmake b/cpp/cmake_modules/BuildUtils.cmake index 90839cb446..d1f641a953 100644 --- a/cpp/cmake_modules/BuildUtils.cmake +++ b/cpp/cmake_modules/BuildUtils.cmake @@ -377,7 +377,7 @@

Re: C++ building question

I could be wrong, but I think the change would look something like [1]. This would only affect libraries built using `add_arrow_lib`, so maybe it wouldn't affect all of the ones you'd like, but this would certainly affect the ones you've mentioned (e.g. "libarrow.*"). I haven't tested it though

C++ building question

Hi, I'm using the arrow library with parquet version 18.0.0 on Windows and Linux from C++. For development purposes, I build both a debug and release version of the libraries. However, I noticed that (e.g., on Windows) the arrow and parquet libraries are named arrow.lib/.dll and parquet.lib/.dll

Re: C++ building question

You can use two different versions of CMAKE_INSTALL_PREFIX: d:\arrow-18.0.0\release and d:\arrow-18.0.0\debug On Fri, Nov 22, 2024 at 5:16 PM Carl Godkin wrote: > Hi Felipe, > > Thanks for your reply. > > I understand that and already build in two sub-directories of cpp called > `win64_build` a

Re: C++ building question

As far as I can tell the library name is determined by arguments to  `add_arrow_lib`[1]. For the main arrow library, the argument itself is not parameterized [2]. So, I think the short answer is that the functionality you're asking for isn't available. If you're interested, you could locally (f