onqtam / rcrl Goto Github PK

cling based C++ as scripting language / hot code reload
Why? Able to run C++ script in runtime or compile it for max speed ( as in example https://github.com/derofim/cling-cmake )
Also: May be used to improve modules compile time

HOT code reload
possible approaches:

store app state
fix cling undo for files
https://root-forum.cern.ch/t/loading-unloading-class-as-interpreted-macro-in-cling-multiple-times/32976/2

execute cling code to change callbacks & variables
nested cling::Interpreter with multiple cling::MetaProcessor
IDK how to do it, but you can create child cling::Interpreter

1. calling cmake from command line throws "Error: could not load cache"

2. opening the folder from CS/IDE stops with " ninja: error: build.ninja:123: bad $-escape (literal $ must be written as $$)"

?any ideas

I have forked your library RCRL and used libclang with some changes as the following:

• Text input is feed to clang.
• Traverse the parsed code for functions & variables definition "ignore errors".
• Add export prefix for them and put them in plugin.cpp.
• Every non-parsed text would be regarded as once in plugin.cpp.
• Append plugin.hpp with functions prototypes and extern variables.
• Load library with RTLD_GLOBAL, so variables can be reused.

Your library is very very helpful. Thanks a bunch.

I attracted to your library when I was using a C++17 library and cling--clang5-- wasn't able to handle header files.

Regards.

For some reason this test (which exports a function called test_ctor_dtor_order() and calls it from RCRL-submitted code) for the order of construction and destruction of variables from a vars section doesn't work on MacOS - this is the output of a failing build - it is as if the function was never called! The weird thing is that it doesn't crash or assert or anything like that - the compiled plugin is copied and loaded successfully...

and the MORE weird thing is that I have no problems calling such exported functions in the demo application (the host_app target) that is the focus of the repository itself

and the EVEN MORE weird thing is that before doing this test with exported symbols I was just inspecting the stdout output when loading the plugin and when unloading it (this commit is with the changes from text-based testing to an exported function) and it... didn't work on MacOS (but output redirecting works perfectly fine for the host_app target)

I tried not to reuse the same plugin.cpp filename for the plugin for the host_app target and the rcrl_compiler_tests target but that didn't help. Maybe the host_app target just works because of some CMake flags inherited from one of the third parties it links against (perhaps glfw?).

So I'm giving up - I cannot waste any more hours on that platform - hopefully someone else helps me.

I read the GLFW documentation about the GLFW_COCOA_RETINA_FRAMEBUFFER window hint and the NSHighResolutionCapable bundle key and tried with a custom Info.plist file (as discussed here)

This is what happens on a retina display on a Mac (something that should have been 45% is 90% horizontally:

Hi, I'm interested in using your RCRL in VSCode for msvc compiler. I successfully built and ran the tests but I have no clue how to use it within the VSCode environment (not sure if this is even possible).
Thanks in advance :)