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 _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
