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" ^ -DCMAKE_BUILD_TYPE=Release ^ -DCMAKE_INSTALL_PREFIX=d:\arrow-18.0.0 ^ -DARROW_CSV=ON ^ -DARROW_PARQUET=ON ^ -DPARQUET_BUILD_EXECUTABLES=ON ^ -DPARQUET_BUILD_EXAMPLES=ON ^ -DARROW_WITH_SNAPPY=ON ^ .. nmake nmake install and then do the same thing for my debug build, the libraries overwrite each other. Other libraries that I use append a "d" or "D" to the library and DLL names which is what I hope to be able to do here. But I can't see how to do it and I'm by no means a cmake expert. I realize that I can rename the files AFTER I build them (e.g., using this <https://github.com/cmberryau/rename_dll/blob/master/rename_dll.py>Python script) but that doesn't quite work in this case since parquet.dll depends on arrow.dll. What ends up happening is that my "parquetD.dll" depends on the original name ("arrow.dll"). Thanks a lot for any suggestions, carl On Fri, Nov 22, 2024 at 12:00 PM Felipe Oliveira Carvalho < [email protected]> wrote: > 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 <[email protected]> wrote: > >> 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 after both >> builds. >> >> I'd like to specify a different name for the debug builds and don't find >> a cmake option for this. >> >> Is there a good way to do this? >> >> Thanks a lot, >> >> carl >> >
