@zooba Could you please take a look? Is this a right way to add some specific flags to builds?

Looks fine, does the CLI argument match the equivalent option to configure?

Looks fine, does the CLI argument match the equivalent option to configure?

Actually, there's no such option to configure.
I'd like to add this in some future PR, I've already tested those changes locally.

Would it fit in? I mainly want the same option, and the configure maintainers are more opinionated about it, so let's make sure we pick a name that they'll be happy with.

I'm thinking about the following options:

--enable-stackref-debug[=no|yes|closed]

And this logic on it:

case $enable_stackref_debug in
  no)              stackref_debug_flags="" ;;
  yes)             stackref_debug_flags="-DPy_STACKREF_DEBUG" ;;
  closed)          stackref_debug_flags="-DPy_STACKREF_DEBUG -DPy_STACKREF_CLOSE_DEBUG" ;;

But at the time it's only my suggestion.

I'm OK with @efimov-mikhail suggestion. I'm also open to updating this PR accordingly.

Hmm, except we don't really have any options with values. Let's just rename to --enable-stackref-debug and not support =<no|yes|etc.> in build.bat - that should be the same as the other options we've got.

If the eventual configure argument gets its name changed, we can update to match. The build.bat interface isn't really public API, so it can change more easily than Python.

@zooba I renamed it. Could you please take a look?

Looks good to me now. Anything else you need to do, or is this good to merge?

It is good to merge.

Thanks!