hexomethyl

Results 17 comments of hexomethyl

Could it be this line ? `template class Streamable;` This line depends on `#include ` and `#include `

Nevermind, the issue was the `Streamable` class specializations, as they aren't necessary I have removed them from my LinkDef.h.

I now seem to be failing in `CppyyLegacy::ExecAutoParse`, the following `code` fails on call to `cr = interpreter->parseForModule(code);` This occurs after the shared library has been loaded into cppyy, and...

Thanks for the info, I'll give Cppyy 3.5 a shot.

Using Cppyy 3.5 didn't resolve the issue, the issue seems to be within Clang like you said, do I still need to pass the include paths to Cppyy ? `[libCling.so]...

The paths are not relative. is that the issue ? EDIT: The root map file has relative headers, however the `code` string passed to `ExecAutoParse` contains headers with absolute paths

Is there a full working example of creating a shared library, generating a dictionary and loading it into Cppyy ?, I feel like I'm missing something fundamental here.

It seems it should "just work" which is a shame. Is there anything I can do to debug this ?, it loads the shared library and rootmap file fine yet...

I managed to compile Clang and Cling as debug and managed to get the following stack trace ![image](https://github.com/user-attachments/assets/f67303ca-a9e4-45bf-b089-8861e535d7a6) With the following assertion being raised ![image](https://github.com/user-attachments/assets/bd3c11f9-2a6b-48f7-b78f-c0cb24b56ad6)

Turns that an error occurs during `[libCling.so] cling::IncrementalParser::commitTransaction IncrementalParser.cpp:595`, which causes Cling to attempt to unload the failed transaction. ![image](https://github.com/user-attachments/assets/e3b3a65f-d9c0-481f-9e53-2e704103920d)