Is it possible to add environment variables to the nanobind_add_stub function?

[maximiliank]

I am having an issue when building my extension with sanitizers enabled when running the stub generation. I would have to add env LD_PRELOAD=/lib64/libasan.so.8 to the command which is executed https://github.com/wjakob/nanobind/blob/master/cmake/nanobind-config.cmake#L471

So it should result in

COMMAND env LD_PRELOAD=/lib64/libasan.so.8 ${NB_STUBGEN_CMD}

Is this somehow possible?

[nurpax]

Not ideal but if you just want a workaround:

One option is to take a copy of the nanobind_add_stub and add it into your bindings project (f.ex in an include file), and then modify your own copy of that function to do what you need.

I recently did that in my bindings project as I had to run some postprocessing on the generouted .pyi output and couldn't figure out a good way to do it.

[wjakob]

FYI (@nurpax , @maximiliank): see PR #1000

[wjakob]

(Can you let me know if this addresses your requirements?)

[maximiliank]

To solve it like that is great. I just made a comment on the PR for the detection of libasan on systems using the input syntax.

[nurpax]

The change looks good. My case was a little different and I eventually switched not doing stubgen in cmake but in a separate shell script. But I also need to use stubgen -r (for submodules) which I suspect is not supported by the cmake nanobind_add_stub API. I've been meaning to write a separate post on the GH Discussions about this as I still feel like I'm not doing my stubgens in the intended way.