[Qt-creator] GSoC 2018: New feature proposal for Qt Creator

Tue Mar 13 10:20:34 CET 2018

Hello,

Creating custom compilers is documented here: http://doc.qt.io/qtcreator/creator-tool-chains.html#adding-custom-compilers

Leena

----------------------------------------------------------------------------------------------------------------------
Leena Miettinen
Documentation Engineer

The Qt Company Germany GmbH
Rudower Chaussee 13
D-12489, Berlin, Germany
Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho 
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
riitta-leena.miettinen at qt.io
+49 30 63 92 3255
http://qt.io 

> -----Original Message-----
> From: Qt-creator [mailto:qt-creator-bounces+riitta-leena.miettinen=qt.io at qt-
> project.org] On Behalf Of Eike Ziller
> Sent: Dienstag, 13. März 2018 10:00
> To: Sree Gowtham Josyula <sreegowthamj at gmail.com>
> Cc: qt-creator at qt-project.org
> Subject: Re: [Qt-creator] GSoC 2018: New feature proposal for Qt Creator
> 
> 
> > On Mar 13, 2018, at 09:54, Sree Gowtham Josyula
> <sreegowthamj at gmail.com> wrote:
> >
> > Hi Orgad,
> >
> > I do not understand what you mean by a custom compiler. Is it some
> > sort of a script on development machine which returns the same values
> > as the remote compiler when queried with -v and -dM flags? What is its
> > significance?
> 
> In Qt Creator settings (Build & Run > Compilers > Add > Custom) you can create
> a “custom” compiler, manually specifying ABI, predefined macros, system
> include paths etc.
> Then you can set that as a compiler for the kit, to make code completion work
> with these values.
> 
> Br, Eike
> 
> >
> > On Tue, Mar 13, 2018 at 12:41 AM, Orgad Shaneh <orgads at gmail.com>
> wrote:
> >> On Mon, Mar 12, 2018 at 11:33 PM, Harri Pasanen <harri at mpaja.com>
> wrote:
> >>>
> >>>
> >>>
> >>>> On Mar 12, 2018, at 4:32 PM, Konstantin Tokarev <annulen at yandex.ru>
> >>>> wrote:
> >>>>
> >>>>
> >>>>
> >>>> 12.03.2018, 15:46, "Orgad Shaneh" <orgads at gmail.com>:
> >>>>> On Mon, Mar 12, 2018 at 1:38 PM, Sree Gowtham Josyula
> >>>>> <sreegowthamj at gmail.com> wrote:
> >>>>>> Hi André & Everyone,
> >>>>>>
> >>>>>> Thanks for showing interest in my suggestion. QTCREATORBUG-16246
> is
> >>>>>> indeed almost like what I had intended in my previous mail.
> >>>>>>
> >>>>>>> * Would it be enough to have the files on a network share instead of
> >>>>>>> rsync'ing them?
> >>>>>>> * Is it really needed to have Clang running on the remote machine?
> >>>>>>> Would it be enough to have access to the included headers on
> remote?
> >>>>>>
> >>>>>> I think Network share you suggest is a good idea. It solves both of
> >>>>>> the above issues. With network sharing, we wouldn't need rsync and we
> >>>>>> wouldn't need to run clang on remote machine.
> >>>>>>
> >>>>>> I will refine my initial proposal and put forth a more detailed
> >>>>>> proposal considering your suggestions and more use-cases asap.
> >>>>>> If you have any other thoughts and suggestions, kindly let me know.
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> I strongly suggest not to use network share. We tried that several
> >>>>> years ago (with SMB), and it was awful. Parsing takes forever over the
> >>>>> network. Working locally and using rsync before build works much better
> >>>>> (once you have ssh keys set up).
> >>>>>
> >>>>> We have a local partial copy of the sysroot, which includes the include
> >>>>> directory, and the shared libraries that are linked with our application
> >>>>> (for each platform we support).
> >>>>
> >>>> Why not to go further and get full copy and toolchain locally?
> >>>>
> >>>
> >>> Network share would in a proper setup be the local disk of the compilation
> >>> server.
> >>>
> >>> Also, one cannot copy locally the toolchain if the server is different OS,
> >>> unless a cross compilation environment is setup, which in itself is a major
> >>> piece of work.
> >>
> >>
> >> That's right. What we did was to create dummy compilers that return the
> same
> >> values as the real compiler when called with -v and -dM etc. This is no
> >> longer needed, as a "custom compiler" can be created instead.
> >>
> >> I suggest to read the values from the remote compiler, and create a local
> >> custom compiler with the same values (except include directories which
> >> should be adapted to the local sysroot location).
> >>
> >> - Orgad
> > _______________________________________________
> > Qt-creator mailing list
> > Qt-creator at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/qt-creator
> 
> --
> Eike Ziller
> Principal Software Engineer
> 
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.ziller at qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB
> 144331 B
> 
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator