From 8eace143cac2339d5749eb5e0fd30ef784198046 Mon Sep 17 00:00:00 2001 From: Will Ayd Date: Tue, 29 Aug 2023 14:45:38 -0400 Subject: [PATCH 1/2] DOC: Add note about using conda to generate debug builds --- doc/source/development/debugging_extensions.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/source/development/debugging_extensions.rst b/doc/source/development/debugging_extensions.rst index 9ac4cf4083475..256a88787f477 100644 --- a/doc/source/development/debugging_extensions.rst +++ b/doc/source/development/debugging_extensions.rst @@ -21,6 +21,10 @@ By default building pandas from source will generate a release build. To generat pip install -ve . --no-build-isolation --config-settings=builddir="debug" --config-settings=setup-args="-Dbuildtype=debug" +.. note:: + + conda environements update CFLAGS/CPPFLAGS with flags that are geared towards generating releases. If using conda, you will may need to set ``CFLAGS="$CFLAGS -O0"`` and ``CPPFLAGS="$CPPFLAGS -O0"`` to ensure optimizations are turned off for debugging + By specifying ``builddir="debug"`` all of the targets will be built and placed in the debug directory relative to the project root. This helps to keep your debug and release artifacts separate; you are of course able to choose a different directory name or omit altogether if you do not care to separate build types. Editor support From 30efff12e15463029b6bbcde070569d05ffa9aaf Mon Sep 17 00:00:00 2001 From: Will Ayd Date: Tue, 29 Aug 2023 14:47:37 -0400 Subject: [PATCH 2/2] typo --- doc/source/development/debugging_extensions.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/development/debugging_extensions.rst b/doc/source/development/debugging_extensions.rst index 256a88787f477..dffc9deadd347 100644 --- a/doc/source/development/debugging_extensions.rst +++ b/doc/source/development/debugging_extensions.rst @@ -23,7 +23,7 @@ By default building pandas from source will generate a release build. To generat .. note:: - conda environements update CFLAGS/CPPFLAGS with flags that are geared towards generating releases. If using conda, you will may need to set ``CFLAGS="$CFLAGS -O0"`` and ``CPPFLAGS="$CPPFLAGS -O0"`` to ensure optimizations are turned off for debugging + conda environements update CFLAGS/CPPFLAGS with flags that are geared towards generating releases. If using conda, you may need to set ``CFLAGS="$CFLAGS -O0"`` and ``CPPFLAGS="$CPPFLAGS -O0"`` to ensure optimizations are turned off for debugging By specifying ``builddir="debug"`` all of the targets will be built and placed in the debug directory relative to the project root. This helps to keep your debug and release artifacts separate; you are of course able to choose a different directory name or omit altogether if you do not care to separate build types.