Hi Team, I am new to the CLING interpreter. Currently, we are using CINT interpreter in our project for writing C++ scripts and we are using VS2012. Since CINT is not supprorted on VS2019, we are looking at using CINT alternative CLING interpreter and migrate our project to VS2019. The way CINT i…

Welcome to the ROOT Forum! I’m not sure if the syntax of the cling.exe arguments match the ones from cint.exe. Maybe @vvassilev or @Axel know

Thank you @bellenot for the response. I am looking forward for ROOT forum support on this !

Hi @vvassilev / @bellenot , Any updates for my query posted above? I have even dropped a mail in detail to “axel@cern.ch” yesterday. Looking for some details/inputs

Apologies for the late response. With cling you don’t need to do this anymore. You can simply #include your headers into cling and that’s it. What’s your workflow, would this work for you?

Hi @bellenot / @Axel , I am not sure whats the issue with the inclusion of windows standard header file “atlstr.h” into the CLING interpreter? I see the error as below upon including any header file that has <atlstr.h> header file in it: [cling]$ .L MSVP_Replication.h “[runStaticInitializersOnc…

It looks like ATL is not supported, but since it is MS specific, I don’t think we can do anything about it. Maybe @vvassilev can comment about this?

OK, I found the origin of the issue (FYI @vvassilev @Danilo ): this is the implicit using namespace std; in the interpreter. A simple example (without cling or root involed): #include <iostream> using namespace std; #include <atlstr.h> int main() { std::cout << "hello world!" << std::endl; …

And FYI, I opened a GitHub issue: The implicit `using namespace std;` can have nasty side effects on Windows. · Issue #14602 · root-project/root · GitHub

Home | News | Documentation | Download | Privacy Notice

ROOT Forum

Building CLING dll from source code

Newbie

root

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled