[Qt-creator] Using QtCreator without GCC installed, which toolchain to configure?

[Diego Iastrubni]

Hi Tobias,

I am trying to use QtCreator to *edit* code to be compiled using IAR
Embedded Workbench® for ARM (*). Compilation integration is trivial by
running a utility by this vendor (easy to setup in QtCreator). This is not
a supported compiler by Qt, and I am not compiling a Qt application (duh!).
They provide an IDE, but its a full piece of unusable shit. I actually
prefer coding under linux using QtCreator and then pushing code to a remote
git branch). Ah yes, we use git, and this IDE does not support GIT - which
makes my life harder.

The headers for this compiler are available in:
%PROGRAM FILES%\IAR Systems\Embedded Workbench 6.4\arm\inc\c
%PROGRAM FILES%\IAR Systems\Embedded Workbench 6.4\arm\inc\{board} (in my
case ST, but not relevant).

There are also some other pre-defined macros and intrinsic functions
defined when compiling using this compiler.

Regarding the error finding in the compilation output, lets assume that I
will get bored and do it myself (should not be that hard, might even be
fun). But this is not my problem:

I expected that the code model would work even without knowing the exact
toolchain. Ok, so it will not know what "open", "snprintf" and others. But
all my own classes and functions? As far I understand, those should be well
defined and known to the code parser right?

(/me will try using gcc as a toolchain and report again in a day or two).

(*) http://www.iar.com/en/Products/IAR-Embedded-Workbench/

On Wed, Aug 22, 2012 at 2:15 PM, <tobias.hunger at nokia.com> wrote:

> Hi Diego!
>
> What exactly is a non-native toolchain? You surely are running something,
> so why can't you specify that as the tool chain? That is just as external
> as gcc or clang are external binaries... creator does not really care what
> they do!
>
> The tool chain for the following things only:
> * Find out which architecture the compiler can produce code for.
> * to find include pathes
> * to find pre-defined macros
>
> Creator will never run the tool chain directly except to query it for its
> settings (if required, not all tool chains do).
>
> Without a tool chain the parsing will be severly broken: The compiler's
> predefined macros are used heavily in your system headers. Without them you
> will get all kinds of strange code. No idea what the code model will make
> of that (if it can make out anything at all:-).
>
> Extraction of warnings and error messages from the compile output is based
> on the *type* of tool chain used.
>
> Provided you are using one of the supported kinds of compilers: Please
> consider to set up a script to run your compiler (on whichever
> machine/environment/setup you have), passing along all the options
> provided. That should suffice for creator to detect all the settings. Then
> create a tool chain in creator and point it to that script. Everything
> should then work fine, provided all the necessary headers are available on
> the machine creator runs on, etc.
>
> I hope this helps...
> Best Regards,
> Tobias
>
> Tobias Hunger
> Software Engineer
> Nokia, Qt Development Frameworks
>
> Nokia gate5 GmbH
> Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
> Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
> Umsatzsteueridentifikationsnummer: DE 812 845 193
> Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20120822/2847122a/attachment.html>