HP NonStop C++ cross compiler in QtCreator, possible?
I was wondering how to use the HP NonStop C++ cross compiler(1) available as a .exe in Windowz in QtCreator.
I tried, but struggle creating the toolchains and the the Qt release to add.
Is it possible or will it become possible?
Native C/C++ PC Cross Compiler:
The PC cross compiler produces TNS/R native object code that runs on NonStop servers in the Guardian or OSS environment. You can invoke the cross compiler from the command line (DOS prompt) if you are using the native C/C++ cross compiler (named c89), version G06.14 and later. The command-line input format is similar to that of c89 on the OSS platform.
Is there any particular reason to want to use that exact compiler, which BTW is not even mentioned in the "list of compilers, supported by Qt":http://qt-project.org/doc/qt-5.0/qtdoc/supported-platforms.html.
Or maybe you mean in Creator as in using Creator as a stand-alone IDE for non-Qt development?
I have been developing for KDE in Qt using Eclipse, KDevelop and QtCtreator and I love Creator. Every home should have one :-)
Yes, I want to use QtCreator for non-Qt framework dev, I need to compile HP NonStop programs.
This NonStop cross-compiler, an .exe, can be used to compile from cmd line in Windows . Also there is a NonStop plugin-in for MS VS2008. Compared to Creator 2.6 it’s like browsing in IE2 compared to today’s browsers. Linked it with (e)ld, an .exe, also used from cmd line. All you do is to transfer this complied/linked binary to NonStop and it runs on Itanium chips in the Guardian Operating system. All compiled and linked in Windowz.
I really think this should theoretically be possible in Creator. But I do not know how to set this up in Creator.
The answer is of course: It depends:-)
Which build system do you want to use for your project? Does that support the compiler?
Creator basically needs to extract some information from the tool chain (macros, include path, etc.), all of which can be set using a "custom tool chain" in master (not sure whether that is in 2.7 already right now;-). That should get the code model to work properly.
Getting build issues from the compiler output requires some coding (assuming the output is different from what gcc/clang produces), maybe you can hack around this with a wrapper script that mangles the output though.