Non-deterministic behavior

[nbeck-SMT]

First of all I want to thank you for creating and sharing this tool! It could save us (and many others) a lot of tedious work.

However, I've run into some unexpected problems. I am trying to generate a CLI wrapper for a fairly large C++ project and each time I run the tool, I get slightly different output: Some methods are added or removed, and sometimes a method even ends up in the wrong class.

So far I haven't looked into the code, but it feels like there is some kind of race condition. Have you noticed similar behavior?

[nbeck-SMT]

I've been able to mitigate the problem somewhat by reducing the number of included headers.

But now I'm facing another problem. How can a wrap methods that return a fixed size C-style array? The source code has annotations like

#define SIZE(size) [[clang::annotate_type("size", #size)]]
int* GetArray() SIZE(5); 

However, I can't seem to find this information in the AST. The Attributes and the PreprocessedEntities for the method declaration are empty. The declarations's namespace does show the macro expansion in its PreprocessedEntities. But I don't see a way of associating this with the method.

Any help would be appreciated.

[tritao]

CppSharp does not really handle things like clang::annotate_type.

As for it not showing, I am guessing there is a bug in the implementation.

I don't really have time to work on fixing this right now, but feel free to send a PR and I will review it.

[nbeck-SMT]

Thanks for the clarification. I'm afraid I wouldn't even know where to start to create a PR for this. In the meantime I've worked around the issue by rewriting all headers so that the macro is at the beginning of the line, e.g. SIZE(5) int* GetArray(); This is a bit messy but it works for now.

Now the next question: How can I tell CppSharp to wrap functions with a C-style array of variable size as a parameter?

SIZE(array, size) void f(double* array, int size);

[nbeck-SMT]

The solution to the non-deterministic output was to set driver.ParserOptions.UnityBuild = true. This also reduced the amount of time it takes to generate the wrapper significantly.