Re: [Qt-creator] ** Caution Message may be spoofed ** Re: Find references of virtual functions?

[Konstantin Tokarev]

14.09.2020, 16:15, "Murphy, Sean" :
>>  > Anyhow, given it's a virtual, how can you know at compile time if
>>  > you're calling GrandChild::foo() or not?
>>  >
>>  > Abstract *blah = getFoo();
>>  > blah->foo(); // might call Grandchild::foo(), or not
>>
>>  FWIW, there are at least 3 cases when it is certainly known at compile time
>>  which overload is called:
>>
>>  1) if object is referenced by value:
>>
>>    Grandchild blah;
>>    blah.foo();
>>
>>  2) fully qualified method call:
>>
>>    Grandchild *blah = getFoo();
>>    blah->Grandchild::foo(); // or Base::foo() etc.
>>
>>  3) when foo() is final in Grandchild:
>>
>>    Grandchild *blah = getFoo();
>>    blah->foo();
>
> Thanks Konstantin, for clarifying better than my initial post did. The 3 
> examples
> above are exactly what I'm referring to. There are instances in the codebase
> where it should be pretty well determined at compile time which overload is
> going to get used, and I only want to see the ones that match for my use case
> (trying to find the impact of changing the behavior of just one of inherited
> classes' overloads).

Note that if such feature was implemented and you could find all places where
your target overload is certainly called, there would be other call sites where
it *might* be called and this is what "find all references" is trying to show.

>
> But currently find all references doesn't give me the option to disregard ones
> that clearly can't be the one I'm trying to find. And because the Search 
> Results
> pane only gives the single line of code that contains the symbol, I often 
> don't
> have enough context there to determine which overload is going to be called,
> forcing me to click on most of the search result entries to then manually
> evaluate whether that chunk of code is likely calling the broken function or 
> not.
>
> Sean
>
> This message has been scanned for malware by Forcepoint. www.forcepoint.com
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Find references of virtual functions?

[Konstantin Tokarev]

12.09.2020, 01:30, "Giuseppe D'Angelo via Qt-creator" 
:
> Il 11/09/20 22:59, Murphy, Sean ha scritto:
>>  Is there any way in Qt Creator to only show me the places where 
>> Grandchild::foo() is called? Right now, I'm finding that even if I go to 
>> grandchild.cpp, put my cursor on void Grandchild::foo(), and then select 
>> "Find Reference to Symbol Under Cursor", it shows me every instance of EVERY 
>> foo() called anywhere in the program, including the declarations/definitions 
>> of Abstract::foo(), Base::foo() and Child::foo(), which I don't care about 
>> at the moment.
>
> By "every foo()" do you mean even the ones completely unrelated to your
> class hierarchy, or all the foo() in the hierarchy?
>
> Anyhow, given it's a virtual, how can you know at compile time if you're
> calling GrandChild::foo() or not?
>
> Abstract *blah = getFoo();
> blah->foo(); // might call Grandchild::foo(), or not

FWIW, there are at least 3 cases when it is certainly known at compile time 
which overload is called:

1) if object is referenced by value:
  
  Grandchild blah;
  blah.foo();

2) fully qualified method call:

  Grandchild *blah = getFoo();
  blah->Grandchild::foo(); // or Base::foo() etc.

3) when foo() is final in Grandchild:
  
  Grandchild *blah = getFoo();
  blah->foo();


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Java support?

[Konstantin Tokarev]

11.09.2020, 10:43, "Eike Ziller" :
>>  On Sep 10, 2020, at 20:21, Jason H  wrote:
>>
>>  I'm working in an Android/iOS app and while creator is just fine for 
>> iOS/Objective-C, QtCreator is not fine at all for Android/Java.
>>
>>  I'm wondering how close QtCreator is to being able to:
>>  * present the java files and classes in the Project explorer (gradle 
>> integration?)
>
> I don’t see gradle integration coming. When we’d finished it, Google would 
> probably switch to something else :P

What about having another kind of generic project plugin which would query 
information from external process, maybe using cmake's file api as an 
inspiration? Like language server but for build systems.
I guess it will make easier for people to create (and maintain!) integrations 
of their favorite build systems then maintaining in-tree or out-of-tree Creator 
plugins.
It might also be that for Gradle it would be easier to write integration code 
in some JVM language.

> But you should be able to use a Generic Project for that: File > New > Import 
> Project > Import Existing Project. (For the language server you should 
> probably import the module base directory?)
> That could probably be made more obvious… like not putting it at the end of a 
> category with lots of version control related items, and calling it something 
> like Import Directory or such (there doesn’t need to be a “project” of any 
> kind).
>
>>  * parse and edit Java code
>>
>>  I'm thinking the language server would do a lot of the heavy lifting?
>
> The java-language-server would/should solve the “parse and edit” part.
> I have not tried it, but probably setting it up as “Start Server per Project” 
> is required, and probably having the module path as the base of the Qt 
> Creator project.
> Also, Qt Creator still has a specialized Java editor from the pre-LSP times, 
> which might interfere with the language client, so switching the handler for 
> text/x-java to “Plain Text Editor” in Preferences > Environment > MIME Types 
> might be needed to.
>
> I agree that someone should check this, potentially throwing the old Java 
> editor away, and maybe Qt Creator can help a bit with setting up the Java 
> language server too, similar to what we do for Python.
>
> Br, Eike
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Erich-Thilo-Straße 10
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Jouni Lintunen
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Tabs vs Spaces?

[Konstantin Tokarev]

09.03.2020, 17:41, "Jason H" :
> I also kind0f remember some string you could put at the top of a file to 
> specify to the editor what the settings are. Anyone know what that it called?

In vim it's called "modeline".

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Tabs vs Spaces?

[Konstantin Tokarev]

06.03.2020, 19:39, "Jason H" :
> I am a tabs guy. I change the Qt style to use tabs. I tab all the things!!
>
> Anyway, I now have other contributors to my project that are spaces people. 
> How can we live in harmony? One side effect is that it seems git considers 
> whitespace changes so his code is indented with spaces, mine are tabs and 
> it's making a mess in git.
>
> Or should this be handled by git? (And if so, how?)

https://stackoverflow.com/a/2318063/12485958

Note that this advices assumes GNU implementations of expand and unexpand,
BSD/macOS implementations don't support same arguments so adjustment may be 
needed

-- 
Regards,
Konstantin


___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Sourcing env

[Konstantin Tokarev]

11.12.2019, 16:25, "Darek Przygoda" :
> Unless 'Run Environment' is set to 'Build Environment' or 'Clean Environment'.
>

Build environment inherits system environment as well.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Sourcing env

[Konstantin Tokarev]

11.12.2019, 13:04, "Paweł Rutka" :
> Hi
> I have problem that before run od executable in qtcreator i have to source 
> env from file to set ld lib Path. Can this be automated for run settings?

You can just run Qt Creator from shell with sourced environment and it will be 
propagated to all child processes

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Generate missing members

[Konstantin Tokarev]

12.04.2019, 18:16, "Jason H" :
> I am really liking this refactor option!. But is there any way to generate 
> them in the .cpp? Currently Im using this refactor option, but I'd rather the 
> stuff just appear in the CPP to start with... Using the move to .cpp refactor 
> is a little clunky because it requires switching between files and you have 
> to hunt down where in the .h it placed them. If there was a "Generate missing 
> members in %class.cpp" that would be amazing.

https://bugreports.qt.io/browse/QTCREATORBUG-19364

>
> Also, sometimes the indentation is wonky. (under indented) in the .h
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator

-- 
Regards,
Konstantin

___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Qt Creator and (lack) Qt Assistant integration

[Konstantin Tokarev]

19.09.2018, 19:44, "Szyk Cech" :
> Hi
>
> At first I appreciate your effort to integrate context help in to Qt
> Creator. But...
>
> I find current solution of F1 key behavior is cumbersome. When I hit F1
> first time then I get (if I am lucky) contest help occupied right site
> (1/3?) of the window. Second F1 hit: I get almost whole window with help.
>
> Problems:
>
> 1. When I leave help and navigate in code then there is no way to get
> back to the help screen (many cases I am hundreds lines of code away
> from the place I invoke context help and I still want it).
>
> 2. When I hit F1 once it appears in verid mode commonly with horizontal
> scroll bar.
>
> 3. There is no easy (keyboard) way to get back (from one F1/partial
> window mode) to code without lost context help.
>
> 4. In two F1/full screen mode shortcuts from Qt Assistant does not work!
>
> 5. Is there any way to open two help documents in Qt Creator?!?
>
> To sum up: I think there is no reason to keep this cumber some build in
> help in Qt Creator. In my opinion far better will be good integration
> with Qt Assistant via local socket (unix socket or local pipe on WinDos)
> - hidden by QLocalSocket and QLocalServer. The only thing which can be
> restricted by system (or system specific) is to raise Qt Assistant from
> background. But I have solution for windows based on local socket and
> sending raised window handle via local socket - I can share this piece
> of code if you want.

On X11 sending _NET_ACTIVE_WINDOW should work fine for all EWMH-compliant
WMs (unlike XRaiseWindow, which still might be useful as a fallback for non-EWMH
capable WMs)

>
> best regards
>
> Szyk Cech
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin

___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

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

[Konstantin Tokarev]

12.03.2018, 15:46, "Orgad Shaneh" :
> On Mon, Mar 12, 2018 at 1:38 PM, Sree Gowtham Josyula 
>  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?


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] [Development] Requesting repository for telemetry plugin in Qt Creator

[Konstantin Tokarev]

23.02.2018, 13:55, "Edward Welbourne" :
> André Pönitz (22 February 2018 20:05)
>>  Any number for a "measured" value for rate of crashes or memory leaks
>>  is uninteresting for me when I run into the problem myself reqularly.
>>  And trust me, I do.
>
> I trust you.
> It is, however, possible your usage patterns of the UI are not typical;
> consequently, you'll prioritise the bugs you see most often; which might
> not be the bugs most often encountered by other users. Analytics may
> give you the data to know the pain points everyone else is as acutely
> aware of as you are of the pain points you meet most often.

Having statistics may also be valuable when you need to explain prioritization
to managers.

-- 
Regards,
Konstantin

___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] [Development] Requesting repository for telemetry plugin in Qt Creator

[Konstantin Tokarev]

22.02.2018, 16:39, "Ryein Goddard" :
> This might be nice to make pretty charts to show to managers, but to be 
> completely honest I think it is 100% useless.  If you don't know what people 
> are using your software for, or how then you aren't communicating with them.  
> You know once upon a time companies just talked with people to figure out 
> what they wanted and what they were having difficulties with.  Why not just 
> take a few surveys a year?

Well, there are things that are hard to report via survey, e.g. rate of crashes 
or memory leaking in clangbackend

>
> On 02/22/2018 08:26 AM, Simon Hausmann wrote:
>> Hi,
>>
>> Can you provide a bit more information about how this plugin / frontend fits 
>> into the Qt project? Where is the collected data sent to and how is it 
>> accessible to the community?
>>
>> (-1 from me, as I think this needs to be clarified)
>>
>> Simon
>> 
>> From: Development  
>> on behalf of Tuukka Turunen 
>> Sent: Thursday, February 22, 2018 2:14:14 PM
>> To: Tino Pyssysalo; qt-creator@qt-project.org; developm...@qt-project.org
>> Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
>> plugin in Qt Creator
>>
>> Hi,
>>
>> +1 for creating the repo, but what about qt/qtanalytics as a name? This item 
>> could be useful also for other applications.
>>
>> Yours,
>>
>>  Tuukka
>>
>> From: Qt-creator  on 
>> behalf of Tino Pyssysalo 
>> Date: Thursday, 22 February 2018 at 13.04
>> To: "qt-creator@qt-project.org" 
>> Subject: [Qt-creator] Requesting repository for telemetry plugin in Qt 
>> Creator
>>
>> Description:
>>
>> Telemetry plugin (frontend) to collect usage data from Qt Creator to help 
>> improving Qt, Qt features, and Qt tools.
>>
>> Non-personal data items, such as duration the user spent in design mode, 
>> will be collected in a way, which is completely transparent to the user.
>>
>> Responsible: Tino Pyssysalo
>>
>> Repository: qt-creator/plugin-telemetry
>>
>> ---
>>
>> Tino Pyssysalo
>>
>> Senior Manager
>>
>> The Qt Company
>>
>> Hämeenkatu 14 C 25
>>
>> 33100 Tampere, Finland
>>
>> tino.pyssys...@qt.io
>>
>> +358 40 8615475
>>
>> http://qt.io
>>
>> The future is Written with Qt
>>
>> ---
>>
>> ___ Qt-creator mailing list 
>> Qt-creator@qt-project.org 
>> http://lists.qt-project.org/mailman/listinfo/qt-creator
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] clangbackend slow code completion

[Konstantin Tokarev]

14.02.2018, 03:04, "Steve Atkins" :
>>  On Feb 13, 2018, at 4:00 PM, Nikos Chantziaras  wrote:
>>
>>  If you have the "clang-tidy" checks enabled, disable them, or only use 1 or 
>> 2 of them. That feature is extremely slow.
>
> That fixes it, thanks. Bit of a shame, as they were rather a nice feature.

There are 2 approaches to this problem:
* use faster CPU
* make clang-tidy itself faster

>
> Cheers,
>   Steve
>
>>  On 14/02/18 01:33, Steve Atkins wrote:
>>>  I'm using Creator 4.6.0-beta1 on a current generation macbook pro, and 
>>> code completion is painfully slow - it'll take four or five seconds to 
>>> complete anything. While it's doing so clangbackend will ramp up to 200% 
>>> CPU.
>>>  It's a reasonably simple project - less than 6,000 lines of code across 
>>> about 60 files. The completion, and everything else connected to the code 
>>> model seems to be working fine, it's just CPU intensive and slow.
>>>  Is this just how the clang backend is at the moment, or should I be 
>>> looking for misconfiguration or other problems?
>>>  Cheers,
>>>    Steve
>>
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin

___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] qt creator plugin license

[Konstantin Tokarev]

23.01.2018, 13:10, "Davide Coppola" :
> Hi,
>
> is there any restriction on licensing plugins for Qt Creator?
>
> Do plugins need to comply to any specific open-source license?
>
> Can they be released as closed source (lib only)?

Qt Creator is currently licensed as GPLv3, however there are exceptions

http://code.qt.io/cgit/qt-creator/qt-creator.git/tree/LICENSE.GPL3-EXCEPT

Second exceptions gives you permission to distiribute combined work
consisting of Qt Creator and your binary-only plugins as long as you share
modifications that you've made in Qt Creator's code. Please read original
license text, and also you may want to consult lawyer.

>
> Thanks
>
> --
> Davide Coppola
>
> email: vivala...@gmail.com
> website: http://www.davidecoppola.com
> blog: http://blog.davidecoppola.com
>
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] prepare-commit-msg and commit-msg hooks

[Konstantin Tokarev]

> On Tue, Jan 09, 2018 at 09:03:14AM -0500, Seth Raymond wrote:
> 
>> Is there a strong reason to keep the process in its current,
>> parallelized state?
> 
> yes. for example, a conscientious committer will want to revise the file
> list when during writing the commit message they notice that the commit
> is non-atomic. happens to me all the time.
> 
> fwiw, qtc is imo still inferior to git gui regarding fine-grained
> commits - the diff view and chunk-level staging are kinda hidden, and
> line-wise staging apparently isn't there at all.

FWIW, one can just press Ctrl-K and type "! git gui" to get it

> in fact, the selective staging context menu is outright broken in 4.5 -
> there is no indication which actions make sense, and there are
> duplicated actions.
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] [FYI] the new way to retarget gerrit changes

[Konstantin Tokarev]

08.01.2018, 16:51, "Orgad Shaneh" <org...@gmail.com>:
> On Mon, Jan 8, 2018 at 3:48 PM, Konstantin Tokarev <annu...@yandex.ru> wrote:
>
>> 08.01.2018, 16:40, "Oswald Buddenhagen" <oswald.buddenha...@qt.io>:
>>> On Mon, Sep 12, 2016 at 02:39:57PM +0300, Orgad Shaneh wrote:
>>>> Either extend the sanity bot, or create a new bot, which listens on
>>>> gerrit's event stream.
>>>> If the change's owner (or an approver?) posts a comment reading "Please
>>>> retarget ", run your script on the server side. You need some
>>>> sanity test that ensures this branch exists etc...
>>>
>>> ... which he implemented, and it's deployed now.
>>>
>>> for simplicity, only the change owner may issue the command. for other
>>> cases, you still need to go through an admin. the same is advisable for
>>> batch requests, but do as you wish.
>>
>> I think batch requests should be automated by adding comments via Gerrit's 
>> API
>> (to minimize your distractions)
>
> That's exactly what was done. Or did I misread your comment?
>
> All you need to do is add a comment in gerrit saying: "bot: move to 5.10" and 
> you're done.

I mean, there can be additional script on client side, to add this comment to 
several changes
(if I usderstood "batch request" correctly)

>
> - Orgad


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] [FYI] the new way to retarget gerrit changes

[Konstantin Tokarev]

08.01.2018, 16:40, "Oswald Buddenhagen" :
> On Mon, Sep 12, 2016 at 02:39:57PM +0300, Orgad Shaneh wrote:
>> Either extend the sanity bot, or create a new bot, which listens on
>> gerrit's event stream.
>> If the change's owner (or an approver?) posts a comment reading "Please
>> retarget ", run your script on the server side. You need some
>> sanity test that ensures this branch exists etc...
>
> ... which he implemented, and it's deployed now.
>
> for simplicity, only the change owner may issue the command. for other
> cases, you still need to go through an admin. the same is advisable for
> batch requests, but do as you wish.

I think batch requests should be automated by adding comments via Gerrit's API
(to minimize your distractions)

>
> the regex is
>
>   
> /^(?:gerrit-)?bot:\h*(?:please\h+)?move\h+(?:back\h+)?to\h+(?:branch\h+)?([\w.]*\w)\b/im
>
> which boils down to "bot: move to " at the start of any line of
> a gerrit cover message.

Oh, "please" keyword :)

> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] "Could not initialise GLX"

[Konstantin Tokarev]

> Hi,
> 
> What does Creator need GLX for and is there a way to disable the feature(s) 
> in question? I'm getting a GLX error when I try to use Creator on a remote X 
> display and don't get any further than that failure message.

Please update Qt Creator. Old versions used QML for Welcome screen, this is 
fixed now.
Otherwise you can just disable Welcome plugin by running with "-noload welcome"

> 
> Thanks,
> R.
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] How to make QtCreator to connect to a remote device (generic linux) with X forwarding enabled `ssh -X`?

[Konstantin Tokarev]

18.12.2017, 12:56, "Иван Кувалдин" :
> Hello.
>
> I develop a cross-platform Qt application with GUI. It works fine on host 
> system in both x32 and x64 variants. Next is to deploy the application on a 
> remote i386 host. It works fine there too. But when I run the app on the 
> remote host through QtCreator, it fails to connect to a display, because it 
> does not exist. The solution is to access to remote host with `-X` option. 
> Definitely. This way it opens window(s) on a local (development) machine.
>
> How to explain QtCreator->Tools->Devices module to connect via `ssh -X`?!
> I believe there is a hidden configuration option in some file, and no need to 
> recompile.
> Thanks in advance.

Note that Qt Creator does not use system ssh client for running remote 
processes,
but uses internal SSH client library built on top of Botan. So it's not 
possible to pass
arbitrary arguments of openssh client to some magic place and get its behavior.

Advice with setting DISPLAY variable seems to be closer to what this feature was
originally meant to do: run application on remote device in the same way as it 
would be
run there normally. X11 forwarding runs application remotely but using your 
local X server
to display it.


>
> Related Questions:
>  0. 
> https://forum.qt.io/topic/86047/how-to-make-qtcreator-to-connect-to-a-remote-device-generic-linux-with-x-forwarding-enabled-ssh-x
>  1. 
> https://stackoverflow.com/questions/47838027/how-to-remotely-debug-graphic-application-with-qtcreator
>
> --
> With best regards Ivan Kuvaldin
> С уважением Иван Кувалдин.
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Clang Static Analyzer does not find STL headers

[Konstantin Tokarev]

05.11.2017, 02:23, "Christian Gagneraud" :
> On 5 November 2017 at 03:03, Christian Gagneraud  wrote:
>>  On 5 November 2017 at 01:40, Benjamin TERRIER  wrote:
>>>  2017-11-03 18:07 GMT+01:00 Nikolai Kosjar :
  There is not much configuration for the clang static analyzer.

  Please create a bug report with:
   * used versions of Qt Creator and configured clang version for the 
 analyzer
   * whether this already happens with a "normal" toolchain. If not, please
  provide some information how to set up your used toolchain.
>>
>>  Hi Nikolai, Benjamin
>>
>>  What is a "normal toolchain", Boot2Qt, Yocto, Qbs or own QtC sauce?
>
> Or maybe you meant a non-bare-metal toolchain? Or a toolchain that
> does not involved Qt/qmake? Or...

When people say "toolchain" without further clarification, they usually mean 
compiler
toolchain which consists of preprocessor, compiler, assembler, and linker

>
> Chris
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Unit testing private parts of shared libraries

[Konstantin Tokarev]

16.10.2017, 20:04, "Elvis Stansvik" :
> 2017-10-16 18:57 GMT+02:00 Elvis Stansvik :
>>  Hi all,
>>
>>  (Posting this as a new thread instead of necroposting to my old thread
>>  about the design of Qt Creator [1], which did end with some
>>  discussions about testing.)
>>
>>  I'm working on some tests for my own application, and started thinking
>>  about unit testing of private parts of shared libraries (think the
>>  _p.h/_p.cpp parts). Such parts are normally not exported AFAIK (in the
>>  visibility attribute sense). This becomes a problem if you link the
>>  unit tests dynamically against the code under test, as the tests won't
>>  be able to see those symbols.
>>
>>  So it seems to me there is only a few options:
>>
>>   1. Exporting the private parts after all,
>>   2. Adding the sources of the code under test to the unit tests,
>>   3. ?
>>
>>  1 is not really good, as you export more than you really have to. But



>
> And build times go up as well of course.
>
> Elvis
>
>>  I guess it's not so bad after all, since you a) have to include _p.h
>>  to get at them and b) they're normally called PrivateSomething or
>>  InternalSomething, both of which should tell you you're doing
>>  something bad. 2 is not really good either though, as you really want
>>  to test the code as shipped, not as compiled as part of your test.
>>
>>  I had a quick look at Qt Creator because I know you folks are seasoned
>>  developers, and it looks like you've gone with option 1. For example,
>>  ExtensionSystem::Internal::PluginSpecPrivate is exported, and I guess
>>  the reason is you want to be able to unit test it?
>>
>>  I just wanted to ask in case you have any other ideas or better ways
>>  to let unit tests access things that are normally not exported?
>>
>>  Thanks in advance,
>>  Elvis
>>
>>  [1] 
>> http://lists.qt-project.org/pipermail/qt-creator/2017-September/006712.html
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QtHelp for Chrome browser extension?

[Konstantin Tokarev]

11.10.2017, 14:34, "Tomasz Siekierda" :
> On 9 October 2017 at 10:40, René J.V. Bertin  wrote:
>>  Hi,
>>
>>  This is an idea that came up when discussion the fact that it seems 
>> overkill to embed an almost full-fledged browser (WebKit or WebEngine) into 
>> an IDE just for the sake of browser API documentation.
>>
>>  Would it be possible (feasible) to write an extension for Chrome-based 
>> browsers that adds qthelp: support to them? If so, does one exist already?
>
> It exists already.
> https://chrome.google.com/webstore/detail/qt-doc-search/gfigdpnkjnilcielpnmfmdnnbloabjoh?utm_source=chrome-app-launcher-info-dialog

AFAIU it uses online search, not local files

>
>>  Thanks,
>>  René
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Difference between QtC tarballs from github and qt.io

[Konstantin Tokarev]

26.05.2017, 13:19, "Andrzej Telszewski" :
> Hi,
>
> I noticed there is a difference between tarball from
> https://github.com/qtproject/qt-creator/archive/v4.3.0.tar.gz
>
> and
> https://download.qt.io/official_releases/qtcreator/4.3/4.3.0/qt-creator-opensource-src-4.3.0.tar.gz
>
> namely, "src/shared/qbs" is empty in tarball from github, but it is
> present in tarball from qt.io
>
> Is this intentional?

src/shared/qbs is a submodule, and apparantly Github doesn't include
submodules contents into autogenerated archives.

Actually, I wouldn't recommend using Github autogenerated archives
for any purpose, use official tarballs that have approved contents and
good compression.

>
> The lack of qbs source in github's tarball bit me yesterday, when I was
> trying to compile QtC against system-wide qbs installation.
>
> It turns out I have to add
> DEFINES+=QBS_ENABLE_PROJECT_FILE_UPDATES
>
> to qmake's command line when generating Makefile for QtC.
>
> This is required so that declarations from "qbs/api/project.h":
> #ifdef QBS_ENABLE_PROJECT_FILE_UPDATES
>  ErrorInfo addGroup(const ProductData , const QString
> );
>  ErrorInfo addFiles(const ProductData , const GroupData ,
> const QStringList );
>  ErrorInfo removeFiles(const ProductData , const GroupData
> ,
>    const QStringList );
>  ErrorInfo removeGroup(const ProductData , const GroupData
> );
> #endif // QBS_ENABLE_PROJECT_FILE_UPDATES
>
> are available when compiling QtC.
>
> If I recall correctly, this problem didn't exist when using tarball from
> qt.io and compiling against system-wide qbs.
>
> Am I missing some documentation or is documentation missing something? :-)
>
> Thanks!
>
> --
> Best regards,
> Andrzej Telszewski
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Where to install Ninja on macOS Sierra (10.12)

[Konstantin Tokarev]

07.04.2017, 14:06, "Tobias Hunger" :
> Hi Mike,
>
> I am not much of an Apple user, so I hope I do not make a fool out of myself 
> by
> trying to answer:
>
> Creator should not default to ninja unless it sees a "ninja" binary in PATH.

AFAIK question was about using ninja consciously, not as default option.

Mike: Change build command in project settings from "cmake --build ." to
/usr/local/bin/ninja or where do you have it

>
> On Thu, 2017-04-06 at 12:42 -0400, Mike Jackson wrote:
>>  What is the recommended location to install ninja on macOS Sierra so
>>  that QtCreator can find it? We tried the usual /usr/local/bin but
>>  QtCreator does not seem to find it there.
>>
>>  Note: putting it in /usr/bin or /bin is NOT a correct answer since SIP
>>  is on by default and will not allow it.
>
> Add the directory with Ninja to PATH? Does that work?
>
> Creator will call "cmake --build .". CMake needs to find ninja somehow. From
> what I see in the manual CMake should find anything in PATH, but I got a 
> report
> that this is apparently not the case on Macs.
>
>>  Could QtCreator ship with a Ninja in its "Resources" directory or is
>>  there some preference setting (like the CMake path) that we are missing?
>
> No, there is no special setting.
>
> I would love to ship more development tools with Qt Creator (e.g. cmake, 
> ninja,
> git) and have them optionally installed along with the IDE. But this is not my
> call to make, no idea whether or not we will do so.
>
> Best Regards,
> Tobias
>
> --
> Tobias Hunger, Senior Software Engineer | The Qt Company
> The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
> 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@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Generic highlighter für Bitbake *.inc files

[Konstantin Tokarev]

16.01.2017, 14:11, "Eike Ziller" :
>>  On Jan 16, 2017, at 12:06 PM, André Hartmann  
>> wrote:
>>
>>  I found the bitbake-syntax-highlighter generic highlighter on Github [1] 
>> and started to use it for my bitbake receipes with QtCreator.
>>
>>  Highlighting of .bb and .bbappend files works well, but .inc files are not 
>> highlighted at all. If I edit the XML file and change "*.inc" to "*.bbinc" 
>> in the extension list line and rename my file, the highlighting is fine. But 
>> that's not what I want to do :)
>>
>>  Any ideas on this?
>
> Looks like it conflicts with the highlighter for Doxyfile

Actually, *.inc file extension may correspond to different file types depending 
on context, e.g. LLVM project uses this extension for 1) C++ "header" files 
intended to be included in the middle or at the end of source file, and 2) for 
TableGen include files.

>
> Br, Eike
>
>>  Best regards,
>>  André
>>
>>  I have tried QtCreator 3.4 and 4.2.
>>
>>  [1] https://github.com/ikoveshnikov/bitbake-syntax-highlighter
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@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.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Feature request: "hot" folders?

[Konstantin Tokarev]

29.12.2016, 19:33, "Jason H" :
> Is it possible to have QtCreator add files dropped into a folder to 
> automatically add it to a QRC?
>
> So often I copy assets into an $$PWD/assets folder, then have to manually add 
> them to a file named assets.qrc.
>
> When the file arrives (or leaves) maybe QtC could prompt to add the file(s) 
> to the QRC?

As for removed files, they are marked red in QRC editor so you can easily 
remove them

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] About building plugins without whole source tree

[Konstantin Tokarev]

23.11.2016, 18:39, "Kakadu" :
> Hey, folks
>
> At the moment we need to compile QtCreator itself to setup right paths
> and compile a plugin. I'm kind of curious is it possible to compile
> QtCreator, do `make install` and do `make install-some-dev-files`
> after that to be able not to store whole source and build files that
> are required to compile a pluign (I think only some headers and shared
> objects are really required).
>
> This thing should generally be possible because GNU/Linux -dev
> packages suit the same purpose. I just do not want to dive into
> packaging scripts... Maybe you have this thing described in some wiki
> page which I'm not aware about?

This has nothing to do with packaging scripts. In fact, dev/devel packages
in Linux distros serve to _split_ a part of normal installation product apart,
not to add something to it.

Qt Creator just does not install headers and other files necessary for building
plugins in its "make install" implementation.

>
> Happy hacking,
> Kakadu
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator for Linux Kernel Development

[Konstantin Tokarev]

23.11.2016, 08:51, "Jason A. Donenfeld" :
> Hello Eike & Qt Creator mailing list,
>
> I'm insane and decided to try using an IDE for Linux kernel
> development. Much to my delight, it actually works well. (Everybody on
> the mailing list to which this message is cross-posted just vomited a
> little bit in their mouth and swallowed, but fear not: I'm a competent
> VIM user too. It's just that sometimes clickity clicking around Qt
> Creator is buttery nice. Here's a screenshot [2].)
>
> I'm working on a small kernel module [1], and for it I made a very
> minimal .pro file to import its files into Qt Creator. I even hooked
> the build/run commands up to my qemu testing rig. Seems to work pretty
> well. Here's the .pro I use:
>
> CONFIG -= qt
> INCLUDEPATH = /usr/src/linux/arch/x86/include
> /usr/src/linux/arch/x86/include/generated/uapi /usr/src/linux/
> arch/x86/include/generated /usr/src/linux/include
> /usr/src/linux/arch/x86/include/uapi /usr/src/linux/arch/x
> 86/include/generated/uapi /usr/src/linux/include/uapi
> /usr/src/linux/include/generated/uapi
> DEFINES = __KERNEL__ DEBUG MODULE
> SOURCES = $$system(find -L . -type f -iname $$system_quote(*.c) -and
> -not -path $$system_quote(./tests/*)) $
> $system(find -L . -type f -iname $$system_quote(*.S) -and -not -path
> $$system_quote(./tests/*))
> HEADERS = $$system(find -L . -type f -iname $$system_quote(*.h) -and
> -not -path $$system_quote(./tests/*))
>
> As you can see, it's a real hack.
>
> I also do development on the main Linux kernel tree, and similarly for
> that, I have a .pro file that works well:
>
> CONFIG -= qt
> INCLUDEPATH = $$system(find -L include/ -type d)
> SOURCES = $$system(find -L . -type f -iname \'*.c\')
> HEADERS = $$system(find -L . -type f -iname \'*.h\')
> INCLUDEPATH = include/ arch/x86/include
>
> Download the linux sources, put that in the tree, and load it up in Qt
> Creator. It works. Amazing!
>
> But don't get too excited. Unfortunately, there are two issues that
> make things unbearable:
>
> (A) Qt Creator doesn't seem to parse the C correctly. Things like
> designated initializers and a few other C features here and there just
> don't get parsed correctly, and the IDE stops being useful. I suspect
> this is because things are actually being parsed in C++ mode. Bummer.
> Developers: any interest in improving C support in Qt Creator?
>
> (B) There is no way to tell Qt Creator that a particular header file
> is included in every file -- that is, that gcc's "-include" is in use.
> There is a way of messing with the "C++ Code Model" on a file-by-file
> basis, for the duration of the time that the file is open, but no way
> to automatically have it included in every file of the project. This
> is a major hindrance. It means that every ifdef for every kconfig
> option is a grayed out unclickable region, rendering most things
> useless.

BTW, I'm facing similar issue with QtWebKit: config.h is included into all
source files, but never in headers, so all #if's in headers are disabled
and code model does not function properly.


> Developers: any interest in fixing this? I spoke to a few of
> you in IRC several months ago about this, and there was interest, but
> it seems to have evaporated.
>
> So, anyway, if you think it would be cool to be able to say, "Qt
> Creator is used for Linux Kernel Development!", then maybe we can work
> together to actually get things working properly. It's already 85%
> there, and the remaining chunk seems well within reach.
>
> Not only that, but if Qt Creator becomes generally usable for ordinary
> C projects, it would most likely become a regular tool during my
> professional activities, namely, auditing large code bases for
> vulnerabilities and improving the security of systems.
>
> Let me know if you are interested in assisting with this.
>
> Thanks,
> Jason
>
> [1] https://www.wireguard.io/
> [2] https://data.zx2c4.com/qt-creator-wireguard-development.png
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] error with position independent code : qt 5.x

[Konstantin Tokarev]

16.09.2016, 18:09, "Tobias Hunger" :
> Hi Kapil,
>
> according to the error message you will need to build your code with
> -fPIC. Not very helpful, but the best I can do with that information,
> sorry.
>
> https://cmake.org/cmake/help/v3.6/variable/CMAKE_POSITION_INDEPENDENT_CODE.html#variable:CMAKE_POSITION_INDEPENDENT_CODE
> might help though:-)
>
> You will need to figure out how to tell that to your project's build
> system. That is a task I do not expect creator being able to help with
> -- each project has its own set of particularities:-/

When Qt5Core module is linked to the target, it adds -fPIC automatically in 
case Qt requires it. So this error usually happens when tartget's sources 
include Qt headers but no Qt library is linked.

>
> Best Regards,
> Tobias
>
> On Fri, Sep 16, 2016 at 4:28 PM, Kapil Gupta  wrote:
>>  Hi,
>>
>>  I am having this error with qt code :
>>  ```
>>  In file included from
>>  /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37:0,
>>   from
>>  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>>   from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>>   from
>>  /usr/include/x86_64-linux-gnu/qt5/QtMultimedia/qaudioformat.h:38,
>>   from
>>  
>> /home/cortana/libdash/libdash/qtplayer/libdashframework/Buffer/AudioChunk.h:16,
>>   from
>>  
>> /home/cortana/libdash/libdash/qtplayer/libdashframework/Buffer/AudioChunk.cpp:12:
>>  /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1067:4: error: #error
>>  "You must build your code with position independent code if Qt was built
>>  with -reduce-relocations. " "Compile your code with -fPIC (-fPIE is not
>>  enough)."
>>   # error "You must build your code with position independent code if Qt was
>>  built with -reduce-relocations. "\
>>  ^
>>  [ 57%] Building CXX object
>>  
>> CMakeFiles/qtsampleplayer.dir/libdashframework/Buffer/MediaObjectBuffer.cpp.o
>>  [ 60%] Building CXX object
>>  CMakeFiles/qtsampleplayer.dir/libdashframework/Input/DASHReceiver.cpp.o
>>  [ 63%] Building CXX object
>>  CMakeFiles/qtsampleplayer.dir/libdashframework/Input/MediaObject.cpp.o
>>  [ 66%] Building CXX object
>>  CMakeFiles/qtsampleplayer.dir/libdashframework/Input/DASHManager.cpp.o
>>  CMakeFiles/qtsampleplayer.dir/build.make:389: recipe for target
>>  'CMakeFiles/qtsampleplayer.dir/libdashframework/Buffer/AudioChunk.cpp.o'
>>  failed
>>  make[2]: ***
>>  [CMakeFiles/qtsampleplayer.dir/libdashframework/Buffer/AudioChunk.cpp.o]
>>  Error 1
>>  make[2]: *** Waiting for unfinished jobs
>>  In file included from
>>  /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37:0,
>>   from
>>  /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>>   from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>>   from
>>  /usr/include/x86_64-linux-gnu/qt5/QtMultimedia/qaudioformat.h:38,
>>   from
>>  
>> /home/cortana/libdash/libdash/qtplayer/libdashframework/Input/DASHManager.h:23,
>>   from
>>  
>> /home/cortana/libdash/libdash/qtplayer/libdashframework/Input/DASHManager.cpp:12:
>>  /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1067:4: error: #error
>>  "You must build your code with position independent code if Qt was built
>>  with -reduce-relocations. " "Compile your code with -fPIC (-fPIE is not
>>  enough)."
>>   # error "You must build your code with position independent code if Qt was
>>  built with -reduce-relocations. "\
>>  ```
>>  What can I do to remove this error? The code is the libdash library's
>>  qtsampleplayer which is based on cmake.
>>
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Problem building qt based code from libdash

[Konstantin Tokarev]

11.09.2016, 17:03, "Kapil Gupta" :
> Hi,
>
> I am trying to build the code provided in the libdash repository which is 
> based on qt. Now I am having this error:
> ```
> [  6%] Building CXX object 
> CMakeFiles/qtsampleplayer.dir/libdashframework/Buffer/AudioChunk.cpp.o
> In file included from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37:0,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia/qaudioformat.h:38,
>  from 
> /home/cortana/libdash-master/libdash/qtplayer/libdashframework/Buffer/AudioChunk.h:16,
>  from 
> /home/cortana/libdash-master/libdash/qtplayer/libdashframework/Buffer/AudioChunk.cpp:12:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1067:4: error: #error "You 
> must build your code with position independent code if Qt was built with 
> -reduce-relocations. " "Compile your code with -fPIC (-fPIE is not enough)."
>  #  error "You must build your code with position independent code if Qt was 
> built with -reduce-relocations. "\
>     ^
> CMakeFiles/qtsampleplayer.dir/build.make:389: recipe for target 
> 'CMakeFiles/qtsampleplayer.dir/libdashframework/Buffer/AudioChunk.cpp.o' 
> failed
> make[2]: *** 
> [CMakeFiles/qtsampleplayer.dir/libdashframework/Buffer/AudioChunk.cpp.o] 
> Error 1
> CMakeFiles/Makefile2:63: recipe for target 
> 'CMakeFiles/qtsampleplayer.dir/all' failed
> make[1]: *** [CMakeFiles/qtsampleplayer.dir/all] Error 2
> Makefile:75: recipe for target 'all' failed
> make: *** [all] Error 2
> ```
>
> I understand that it says to run the code with -fPIC tag on. But I dont know 
> and cant find out how to do so.

This error may happen when you have code which includes Qt headers, but its 
target does not link to any Qt library.

>
> Kapil Gupta
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] [Development] [FYI] on gerrit change retargeting requests

[Konstantin Tokarev]

06.09.2016, 12:44, "Oswald Buddenhagen" :
> On Mon, Sep 05, 2016 at 09:17:59PM +, J-P Nurmi wrote:
>>  On 05 Sep 2016, at 19:27, Marc Mutz  wrote:
>>  > It's not about restricting what a user can do. It's simply missing
>>  > implementation, and I believe that if it were easy to implement,
>>  > Ossi would have done it long ago instead of playing retarget-monkey
>>  > for the rest of us :)
>>
>>  Doing it through the web UI would be a nice bonus, but having access
>>  to the same script that is already used by the admins would be good
>>  enough for starters.
>
> yep - because i'm totally going to give everyone full write access to
> the database. ;)
>
> if you make a secure web frontend that authenticates against qt account
> and verifies change ownership using the gerrit ssh interface, i'm
> totally willing to deploy that. ;)

Idea: IRC bot accepting retarget requests, with rate limit e.g. one request per 
minute. Bot runs on host with db access and can do only this one thing.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] (no subject)

[Konstantin Tokarev]

19.08.2016, 18:05, "Kapil Gupta" :
> Hi,
>
> I am really new to qt so please bear with me. I have deleted this file:
> "/usr/lib/x86_64-linux-gnu/qt5/bin/cmake" , by mistake. What can I do to get 
> it back.

Ubuntu does not provide this file. Where did you get it?

>
> I am on qt5.7 and Ubuntu 14.04.
> I have tried reinstalling which didn't help.
>
> I have also tried installing qt5-default, qtbase5-dev-tools.
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QtCreator 4.1 "Installer"?

[Konstantin Tokarev]

08.07.2016, 12:48, "Jake Petroules" :
>> On Jul 8, 2016, at 1:36 AM, Eike Ziller  wrote:
>>
>>> On Jul 7, 2016, at 5:36 PM, Jake Petroules  wrote:
>>>
 On Jul 6, 2016, at 11:10 PM, Eike Ziller  wrote:

> On Jul 6, 2016, at 19:47, Jake Petroules  wrote:
>
> I agree this is a -1. Is this something we're just doing for the beta and 
> the final should be correctly shipped as a drag n drop dmg?
>
>> On Jul 6, 2016, at 10:36 AM, Mike Jackson  wrote:
>>
>> Out of curiosity why was there a switch from a "Drag-n-Drop" 
>> installation of QtCreator to an actual "installer" that I have to run?
>>
>> I would like to put a "-1" vote for the installer? Was there really a 
>> need for it? And where all is stuff being installed? I tend to use the 
>> nightlies which as a Drag-n-Drop install was easy to update on a daily 
>> basis and have multiple versions available at any one time.

 This is the result of consolidating how we build Qt Creator standalone and 
 the diverse Qt packages.
 So far we had completely different setups for Qt Creator standalone and Qt 
 packages, and it is far from optimal or even good.
>>>
>>> That was extremely optimal and good. Besides, they are separate and 
>>> unrelated products, why on earth would their setup processes have anything 
>>> to do with each other?
>>
>> Because one (Qt) includes the other (Qt Creator). And while it might be 
>> reasonable to keep packaging processes separate if these products are done 
>> by completely unrelated people, it doesn’t make sense at all if people and 
>> infrastructure are the same.
>>
>> It avoids duplication of efforts like license changes, changes in what 
>> exactly must be packaged, checking that the correct MSVC runtime is 
>> installed and install it if necessary, registering menus on Windows and 
>> Linux, registering as default application for file types, and even the 
>> decision which version of the installer framework is used. And it will make 
>> thinks like providing the CDB debugging extension for both 32bit and 64bit 
>> for both 32&64 bit packages easier, and enable us to get rid of the 
>> error-prone hack with the binary-artifacts repository 
>> (http://code.qt.io/cgit/qt-creator/binary-artifacts.git/tree/), without 
>> duplicating the effort of packaging cdbextension and jom as well.
>>
>> Yes, none of these is interesting for the opensource Qt Creator for macOS. 
>> Some of these _are_ interesting for the enterprise product even on macOS, 
>> which shipped with an installer already before.
>> I have on my list to investigate if and how we can get the drag’n’drop dmg 
>> back on macOS.
>
> As long as that is *also* provided, there is no problem. Providing it as an 
> option shouldn't affect your goals for the above.
>
> Considering that the Qt Creator application bundle is already built as part 
> of the overall build process anyways and is itself completely self contained, 
> the DMG packaging step is quite simple.
>
>>> Changes like this are not user friendly. People do not want an installer on 
>>> macOS. They do not want bin and lib directories. They want drag n drop 
>>> application bundles in a DMG. This is how virtually all applications are 
>>> deployed on macOS. Whoever decided this:
>>> • Doesn't own a Mac
>>> • Is a KDE/Linux user/developer
>>> • Is a developer and not a product manager
>>> At least one of the three is true. Am I right?
>>
>> I think you can simplify that to “is not a product manager who owns a Mac”.
>>
>> It was done by the one who is responsible for releasing Qt Creator, who 
>> happens to work 95% on Macs.
>>
>>> It's really frustrating to see constant accumulation of concepts and ideas 
>>> that arise from 90% of our developers being long time KDE/Linux developers 
>>> and having no interest in anything else. The other platforms of the world 
>>> are not KDE. Things are done differently there. Please start acknowledging 
>>> this.
>>
>> I don’t see any relation between KDE/Linux and GUI installers. Actually most 
>> Linux users would prefer having 
>> .deb/.rpm/ packages.
>
> Yes, that's my point -- provide what the users of the target platform expect. 
> deb/rpm packages would be nice, but of course that has other issues that DMGs 
> do not (conflict w/ system packages).

It's possible to have deb/rpm packages that install the same bundle of official 
binaries to /opt and don't conflict with system packages.


>
>> [snip from other mail]
 OTOH, there are a lot of Mac applications shipped with installer, though 
 they are not the majority.
>>>
>>> When there's a necessity for it, like installing kernel extensions. Does Qt 
>>> Creator require kexts or other system-wide state? No? Then it should not 
>>> have an installer.
>>
>> I have seen many applications that have an 

Re: [Qt-creator] snap or flatpak?

[Konstantin Tokarev]

07.07.2016, 20:39, "Ryein C. Goddard" :
> I was curious if you guys had any plans to release a snappy or flatpak package
> for Linux? Sorry if this was already brought up. I just subscribed.

Qt Project already provides self-contained binary packages for Linux:

http://download.qt.io/official_releases/qtcreator/4.0/4.0.3/qt-creator-opensource-linux-x86_64-4.0.3.run


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QtCreator 4.1 "Installer"?

[Konstantin Tokarev]

07.07.2016, 18:36, "Jake Petroules" :
>> On Jul 6, 2016, at 11:10 PM, Eike Ziller  wrote:
>>
>>> On Jul 6, 2016, at 19:47, Jake Petroules  wrote:
>>>
>>> I agree this is a -1. Is this something we're just doing for the beta and 
>>> the final should be correctly shipped as a drag n drop dmg?
>>>
 On Jul 6, 2016, at 10:36 AM, Mike Jackson  wrote:

 Out of curiosity why was there a switch from a "Drag-n-Drop" installation 
 of QtCreator to an actual "installer" that I have to run?

 I would like to put a "-1" vote for the installer? Was there really a need 
 for it? And where all is stuff being installed? I tend to use the 
 nightlies which as a Drag-n-Drop install was easy to update on a daily 
 basis and have multiple versions available at any one time.
>>
>> This is the result of consolidating how we build Qt Creator standalone and 
>> the diverse Qt packages.
>> So far we had completely different setups for Qt Creator standalone and Qt 
>> packages, and it is far from optimal or even good.
>
> That was extremely optimal and good. Besides, they are separate and unrelated 
> products, why on earth would their setup processes have anything to do with 
> each other?
>
> Changes like this are not user friendly. People do not want an installer on 
> macOS. They do not want bin and lib directories. They want drag n drop 
> application bundles in a DMG. This is how virtually all applications are 
> deployed on macOS. Whoever decided this:
>
> * Doesn't own a Mac
> * Is a KDE/Linux user/developer
> * Is a developer and not a product manager
> At least one of the three is true. Am I right?
>
> It's really frustrating to see constant accumulation of concepts and ideas 
> that arise from 90% of our developers being long time KDE/Linux developers 
> and having no interest in anything else. The other platforms of the world are 
> not KDE. Things are done differently there. Please start acknowledging this.
>

Hmm, what? There are no installers in KDE.

OTOH, there are a lot of Mac applications shipped with installer, though they 
are not the majority.

>> In any case, for running the opensource content Qt Creator does not require 
>> an installer on any platform, and you can just go ahead and unpack the 
>> sevenzips located in the “installer_source” sub-directories for the 
>> platform, e.g.
>> https://download.qt.io/development_releases/qtcreator/4.1/4.1.0-beta1/installer_source/mac_x64/
>> (on other than macOS, you should be aware that these do not contain any 
>> “qt-creator” subdirectory, and directly contain “bin/“, “lib/“, etc 
>> directories).
>>
>> Br, Eike
>>
 --
 Michael A. Jackson
 BlueQuartz Software, LLC
 [e]: mike.jack...@bluequartz.net
 ___
 Qt-creator mailing list
 Qt-creator@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>
>>> --
>>> Jake Petroules - jake.petrou...@qt.io
>>> Consulting Services Engineer - The Qt Company
>>> Qbs build tool evangelist - qbs.io
>>>
>>> ___
>>> Qt-creator mailing list
>>> Qt-creator@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.zil...@qt.io
>> +123 45 6789012
>> http://qt.io
>> Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
>> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
>> HRB 144331 B
>
> --
> Jake Petroules - jake.petrou...@qt.io
> Consulting Services Engineer - The Qt Company
> Qbs build tool evangelist - qbs.io
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Alternative / secondary keyboard shortcuts

[Konstantin Tokarev]

27.06.2016, 16:12, "Ariel Molina" :
> Most of the bugs really have few, if any votes, yet they get fixed.

Citing André Pönitz, 

"The problem is not a missing vote, but missing code."

http://lists.qt-project.org/pipermail/qt-creator/2012-December/001699.html

>
> Ariel
>
> On Mon, Jun 27, 2016 at 6:16 AM, Juan Navarro  wrote:
>> Thanks, I've casted my vote there, but seeing that it only has 5 votes now, 
>> I guess it means that almost nobody finds desirable to have the possibility 
>> of secondary shortcuts :-(
>>
>> On Fri, Jun 24, 2016 at 7:51 AM, Eike Ziller  wrote:
 On Jun 23, 2016, at 13:27, Juan Navarro  wrote:

 Hi,

 All my coworkers use the default keyboard shortcut for the 
 "UnCommentSelection" (Toggle Comment Selection) command, which is 
 "Ctrl+/". However, I'm used to do this same operation with Ctrl+D, which 
 is easier and can be done with just one hand.

 Sometimes we do pair programming where either of us has the keyboard, and 
 its very annoying for each one of us to find out that this keyboard 
 shortcut is set up the other way around.

 I tried to find out whether it is possible to define alternative or 
 secondary keyboard shortcuts, which seems to be common in several other 
 tools that I've used in the past. However Qt Creator doesn't have an 
 obvious way to do this.

 If it's not possible at all, then I'd like to submit a feature request, 
 but before its better to ask here.
>>>
>>> https://bugreports.qt.io/browse/QTCREATORBUG-72
>>>
>>> --
>>> Eike Ziller
>>> Principal Software Engineer
>>>
>>> The Qt Company GmbH
>>> Rudower Chaussee 13
>>> D-12489 Berlin
>>> eike.zil...@qt.io
>>> +123 45 6789012
>>> http://qt.io
>>> Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
>>> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
>>> HRB 144331 B
>>
>> ___
>> Qt-creator mailing list
>> Qt-creator@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> --
> Ariel Molina R.
>
> Oficina: +52 (222) 3723196
> Movil: +521 2226 758874
> http://edis.mx
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Use clang UBSan with QtC

[Konstantin Tokarev]

04.06.2016, 20:25, "Denis Shienkov" <denis.shien...@gmail.com>:
>> If you use GCC-based kit, you will use GCC implementation of UBSan instead 
>>of Clang's (GCC >= 4.9 required)
>
> Ok, clear, I use GCC 5.xxx
>
>> UBSan is dynamic analysis tool, based on compiler instrumentation. It has 
>>nothing to do with static analysis.
>
> So, should I just run my app and see debug outputs?

Yes, it will crash in case UB is detected

>
> 2016-06-04 20:16 GMT+03:00 Konstantin Tokarev <annu...@yandex.ru>:
>> 04.06.2016, 20:07, "Denis Shienkov" <denis.shien...@gmail.com>:
>>>> As with other sanitizers, just add -fsanitize=undefined to QMAKE_CXXFLAGS 
>>>>and QMAKE_LFLAGS
>>>
>>> 1. Should I use the Clang-based Kit and compile my sources with this Kit, 
>>> or I can use GCC-based kit for this?
>>
>> If you use GCC-based kit, you will use GCC implementation of UBSan instead 
>> of Clang's (GCC >= 4.9 required)
>>
>>> 2. Is this will work when I click on "Analyze -> Clang Static Analyzer" 
>>> from the QtC menu?
>>
>> UBSan is dynamic analysis tool, based on compiler instrumentation. It has 
>> nothing to do with static analysis.
>>
>>>
>>> 2016-06-04 19:39 GMT+03:00 Konstantin Tokarev <annu...@yandex.ru>:
>>>> 04.06.2016, 19:27, "Denis Shienkov" <denis.shien...@gmail.com>:
>>>>> Hi all,
>>>>>
>>>>> 1) is it possible to use the clang's UBSan with QtC? :)
>>>>
>>>> Why not?
>>>>
>>>>>
>>>>> 2) if yes - then how to do it?
>>>>
>>>> As with other sanitizers, just add -fsanitize=undefined to QMAKE_CXXFLAGS 
>>>> and QMAKE_LFLAGS
>>>>
>>>>>
>>>>> 3) if yes - is it possible to use on Windows?
>>>>
>>>> http://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html#supported-platforms
>>>>
>>>>>
>>>>> BR,
>>>>>
>>>>> Denis
>>>>>
>>>>> ___
>>>>> Qt-creator mailing list
>>>>> Qt-creator@qt-project.org
>>>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>
>>>> --
>>>> Regards,
>>>> Konstantin
>>
>> --
>> Regards,
>> Konstantin
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Use clang UBSan with QtC

[Konstantin Tokarev]

04.06.2016, 19:27, "Denis Shienkov" :
> Hi all,
>
> 1) is it possible to use the clang's UBSan with QtC? :)

Why not?

>
> 2) if yes - then how to do it?

As with other sanitizers, just add -fsanitize=undefined to QMAKE_CXXFLAGS and 
QMAKE_LFLAGS

>
> 3) if yes - is it possible to use on Windows?

http://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html#supported-platforms


>
> BR,
>
> Denis
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Generating QtCreator cmake project for given CMakeLists.txt from command line

[Konstantin Tokarev]

02.06.2016, 19:07, "René J.V. Bertin" :
> Hi,
>
> Reviving an older thread after, well to honest, not having had a reason to 
> use Creator for a while ...
>
> So I updated to git/master, and discover that it's become even more 
> complicated to import a CMake-based project for which you already have a 
> (lengthy) cmake command line. Have I missed a place to input the commandline 
> "as is" during the import procedure, or does one really have to cut it up and 
> create the entries one by one through a WYSIAYG interface?

The next sequence have worked for me:

1. Open CMakeLists.txt
2. Choose appropriate Kit from list, or create one if it is missing. Import 
project
3. Go to project settings and switch build directory to the one which has your 
configured build.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Close Project "xxxxx" behavior

[Konstantin Tokarev]

22.02.2016, 22:01, "Jason H" :
> It would be cool if when closing a project, the files belonging to that 
> project are closed in the editor as well. Currently, creator keeps them open.

File can belong to different projects, or it may have been already opened 
before x was opened.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] qmake and backtick command arguments

[Konstantin Tokarev]

22.02.2016, 11:55, "Nikos Chantziaras" :
> On 22/02/16 10:45, Andrzej Telszewski wrote:
>>  On 22/02/16 09:39, Ziller Eike wrote:
  This yields yet another inconvenience. Using QMAKE_CFLAGS allows
  application to compile fine, but header files are not seen by Qt
  Creator and so cannot be nicely navigated.
>>>  Looks like Qt Creator handles QMAKE_CXXFLAGS, but not QMAKE_CFLAGS.
>>>
>>>  Br, Eike
>>
>>  OK, now I understand what you meant.
>>
>>  This works for navigation/browsing:
>>  QMAKE_CXXFLAGS += $$system(php-config --includes)
>>
>>  but this, does not work:
>>  QMAKE_CFLAGS += $$system(php-config --includes)
>
> INCLUDEPATH sets both of these automatically.

But output of pkg-config-like tools is supposed to be directly fed into 
compiler, e.g. if --includes output contains -isystem your code will fail.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] qmake and backtick command arguments

[Konstantin Tokarev]

21.02.2016, 13:59, "Andrzej Telszewski" <atelszew...@gmail.com>:
> On 21/02/16 11:53, Konstantin Tokarev wrote:
>>  21.02.2016, 13:50, "Andrzej Telszewski" <atelszew...@gmail.com>:
>>>  On 21/02/16 11:34, Nikos Chantziaras wrote:
>>>>    On 21/02/16 11:47, Andrzej Telszewski wrote:
>>>>>    Hi,
>>>>>
>>>>>    I'm trying to do something like this in .pro file:
>>>>>    INCLUDEPATH += \
>>>>>   `php-config --includes`
>>>>
>>>>    Try the system() function in combination with the "$$" operator (for
>>>>    variable expansion):
>>>>
>>>>   INCLUDEPATH += $$system(php-config --includes)
>>>
>>>  It works!
>>>
>>>  Now I have another problem:
>>>
>>>  The output of php-config --includes is:
>>>  -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM
>>>  -I/usr/include/php/Zend -I/usr/include/php/ext
>>>  -I/usr/include/php/ext/date/lib
>>>
>>>  And in consequence INCLUDEPATH becomes:
>>>  -I-I/usr/include/php -I-I/usr/include/php/main -I-I/usr/include/php/TSRM
>>>  -I-I/usr/include/php/Zend -I-I/usr/include/php/ext
>>>  -I-I/usr/include/php/ext/date/lib
>>>
>>>  that is, extra "-I" is added by qmake.
>>>
>>>  Is there an easy way to work around it?
>>>
>>>  "php-config" does not seem to have any possibility of tweaking its output.
>>
>>  You need to use QMAKE_CXXFLAGS (or QMAKE_CFLAGS if you build C) instead of 
>> INCLUDEPATH.
>
> This yields yet another inconvenience. Using QMAKE_CFLAGS allows
> application to compile fine, but header files are not seen by Qt Creator
> and so cannot be nicely navigated.
>
> Any thoughts on that?

Is it possible to use pkg-config instead of php-config? In this case you can 
use pkg-config integration in qmake.

>
> --
> Best regards,
> Andrzej Telszewski

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] qmake and backtick command arguments

[Konstantin Tokarev]

21.02.2016, 13:50, "Andrzej Telszewski" :
> On 21/02/16 11:34, Nikos Chantziaras wrote:
>>  On 21/02/16 11:47, Andrzej Telszewski wrote:
>>>  Hi,
>>>
>>>  I'm trying to do something like this in .pro file:
>>>  INCLUDEPATH += \
>>> `php-config --includes`
>>
>>  Try the system() function in combination with the "$$" operator (for
>>  variable expansion):
>>
>> INCLUDEPATH += $$system(php-config --includes)
>
> It works!
>
> Now I have another problem:
>
> The output of php-config --includes is:
> -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM
> -I/usr/include/php/Zend -I/usr/include/php/ext
> -I/usr/include/php/ext/date/lib
>
> And in consequence INCLUDEPATH becomes:
> -I-I/usr/include/php -I-I/usr/include/php/main -I-I/usr/include/php/TSRM
> -I-I/usr/include/php/Zend -I-I/usr/include/php/ext
> -I-I/usr/include/php/ext/date/lib
>
> that is, extra "-I" is added by qmake.
>
> Is there an easy way to work around it?
>
> "php-config" does not seem to have any possibility of tweaking its output.

You need to use QMAKE_CXXFLAGS (or QMAKE_CFLAGS if you build C) instead of 
INCLUDEPATH.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] qmake and backtick command arguments

[Konstantin Tokarev]

21.02.2016, 13:34, "Nikos Chantziaras" :
> On 21/02/16 11:47, Andrzej Telszewski wrote:
>>  Hi,
>>
>>  I'm trying to do something like this in .pro file:
>>  INCLUDEPATH += \
>> `php-config --includes`
>
> Try the system() function in combination with the "$$" operator (for
> variable expansion):
>
>    INCLUDEPATH += $$system(php-config --includes)

Note that in this case command will run when qmake is executed, not make.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Valgrind it doesn't work in OS X

[Konstantin Tokarev]

09.02.2016, 18:02, "Freddy Martinez" :
> Hi guys… I’m trying to run Valgrind inside Qt Creator in OS X El Capitan. I 
> have the last Qt version and when I run the Valgrind (using Valgrind Memory 
> Analizer or Valgrinf Function Profile) valgrind remain unfunctional and my 
> progrmam never start…
>
> what am i suppose to do ? any idea ?? regards

This issue has nothing to do with Qt Creator, please ask on Valgrind mailing 
list (valgrind-us...@lists.sourceforge.net).

However, Valgrind more often than not has issues when running on latest and 
greatest OS X. If using Valgrind is important for you, I'd recommended not to 
rush for OS updates as long as previous OS X release is supported.


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] License update! Please check license template!

[Konstantin Tokarev]

16.01.2016, 15:21, "Hunger Tobias" :
> Hi Peter,
>
> I was not involved in the agreement between the Free Qt Foundation and the Qt 
> Company, so I can not comment in any meaningful way, sorry. Neither have I 
> insight in our sales numbers, so I can not comment on the effect of GPL or 
> LGPL on actual sales figures either.
>
> Please consider to comment on the blog post announcing the change: You are 
> more likely to contact people driving this change there. This is basically 
> just our out-of-the-way technical mailing list.
>
> I *personally* welcome the outcome very much: We get to provide more free 
> software and I agree with the idea of software freedom as expressed by the 
> GPL. It also makes my work-live much easier as I will have less repositories 
> to juggle once the code moved into the public repository.

There are actually two separate license change events here: 

1. Proprietary plugins were relicensed under GPL. I believe that everyone here 
agrees that this is a positive change that should be highly appreciated.

2. Exisiting code base (including core components) was relicensed to much more 
restrictive license. I *personally* see this as a negative change, however I 
guess it as a necessary precondition for point #1 to happen.

I know there is a third party that was (is?) trying to make a commercial IDE 
based on Qt Creator with value added components. Their chief didn't want to 
allow developers to act as a part of community, he wanted to just grab the 
sources, cripple them and sell as their own product. I am happy that this 
license change will drive away such people. But I'm concerned that it will also 
drive away more well-intentioned contributors having some commercial interest.

As for my personal contributions to Qt Creator project, I'm happy to see them 
being in use under any free license that community likes, be it GPLv3 or BSD or 
something else.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] License update! Please check license template!

[Konstantin Tokarev]

16.01.2016, 18:09, "Peter Kümmel" :
>>  2. Exisiting code base (including core components) was relicensed to much 
>> more restrictive license. I *personally* see this as a negative change, 
>> however I guess it as a necessary precondition for point #1 to happen.
>
> But who uses internal QtCreator libraries in his product? This would be
> the usecase for LGPL. But QtCreator is a all-or-nothing app not a
> node.js, so GPL is here maybe really better.

E.g. look at Eclipse RCP which became a foundation for lots of open-source and 
commercial products.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QT Creator, compiling and deploying a c or c++ to a remote device (BeagleBone or R pi)

[Konstantin Tokarev]

27.09.2015, 11:33, "Davide Picchi" :
> I'm trying since days to write and develop programs on my host pc (Ubuntu 
> 64bit) using qt-creator for my beaglebone and raspberry pi devices. I looked 
> for 'qt-creator cross compile beagle, raspberry etc...' and it leads me to 
> hundred of links and tutorial on how to compile qt-creator for my target 
> plattform. But seriously, that not my idea. All what I want is to simply use 
> my pc for developing my programs and lately deploy them to the remote device.
>
> So first of all a noob question: Is something wrong with my idea? Should I 
> really compile the source of qt for beaglebone or raspberry on my pc for 
> writing programs which lately should be run on that devices
>
> I will not compile qt-creator again for another plattform, so I don't know 
> how to find the right way. A lot of informations on internet are misleading.
>
> So after many hours spend look for the right information I come up with the 
> following procedure:
>
> first I installed a arm-gnu toolchain on my 64bit Ubuntu.
>
> $sudo apt-get install build-essential libc6-armhf-cross libc6-dev-armhf-cross 
> binutils-arm-linux-gnueabihf linux-libc-dev-armhf-cross 
> libstdc++6-armhf-cross gcc-4.8-arm-linux-gnueabihf g++-4.8-arm-linux-gnueabihf
>
> then I installed qt-creator from the repository on my Ubuntu:
>
> $sudo apt-get install qtcreator
>
> I tried to configure to use qt for compiling my projects using the toolchain 
> for arm (see following pictures)
>
> Screenshot #1
>
> and here:
>
> Screenshot #2
>
> but it seems that qt-creator doesn't recognize the new kit when I start a new 
> project:
>
> Screenshot #3
>
> Now: I m really confused, I could think that the problem is related to qt, 
> but I m not sure, whether the way of thinking, that I can compile on ubuntu 
> 64bit and then run my application on the remote device is right or not.
>
> For this reason it would be nice if you can answer the question above.
>
> Furthermore: I tried adding a QT-version to my kit and in this case it 
> happens that the gnueabi compiler conflicts with that options and the 
> following problem arises:
>
> Screenshot #4
>
> I would like to say again that I don't need to use qt-library or something 
> like that on my remote device. I need just to use the qt-IDE as IDE for my 
> projects (mainly c or c++ plain projects)
>
> Thanks and regards

FWIW, you can use Qt Creator with Makefile-based projects, so you don't have to 
struggle if qmake stands in your way.


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] unnamed namespace and internal linkage

[Konstantin Tokarev]

22.09.2015, 14:45, "Lorenz Haas" :
>>  I don't know, but shouldn't the "static" keyword be preferred anyway due
>>  to being less noisy?
>
> Okay, beside the theoretical question, let's make it concrete -and
> clear-: 
> https://github.com/qtproject/qt-creator/blob/51bb52139c479cca2dae82eb08aeb8d04718fca1/src/plugins/beautifier/artisticstyle/artisticstylesettings.cpp#L52
> Should it be:
>
> a) namespace { const char kUseOtherFiles[] = "useOtherFiles"; }
> b) namespace { static const char kUseOtherFiles[] = "useOtherFiles"; }
> c) static const char kUseOtherFiles[] = "useOtherFiles";
>
> So one should favor c, right?
>

You should favor

d) const char kUseOtherFiles[] = "useOtherFiles";

because constants have internal linkage by default.


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] NimPlugin: autocompletion

[Konstantin Tokarev]

22.05.2015, 20:59, Filippo Cucchetto filippocucche...@gmail.com:
 I think that it isn't so impossible to implement, we just need to:
 - hook a webservice for deploying a plugin source code and put it inside the 
 plugin folder where QtCreator is built
 - change the plugin.pro for adding a new subdir folder
 - build and profit
 i could be a great idea

I always built my plugins out of tree, no need to touch plugin.pro


 2015-05-22 18:51 GMT+02:00 Tobias Hunger tobias.hun...@gmail.com:
 Am 22.05.2015 15:23 schrieb Cristian Adam
 Or a central place where people can get plugins for Qt Creator. Visual 
 Studio has Visual Studio Gallery (5437 items)

 One would get working / tested plugins without having to compile themselves.

 Oh, that would indeed rock!

 --
 Filippo Cucchetto
 ,

 ___
 Qt-creator mailing list
 Qt-creator@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/qt-creator


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] where better to start

[Konstantin Tokarev]

22.01.2015, 15:41, Андрей Полтавец andrey.poltav...@gmail.com:
 Dear, Qt-developers! Today I created a thread in web-forum and some man 
 redirect me here. So I merely copy that text:

 Where better to start learning QtC?
 Now I am going to set-up my portfolio, because, I am beginner c++/qt 
 developer. So, I need a real experience in real project. Some seniors-dev 
 advised me to invovle in development processes of projects like QtCreator or 
 LibreOffice.
 So, where I should start for bugfixing and creating plugins?
 Btw, example plugin I am already wrote. Actually I want to find information 
 about Pluginmanager, IPlugin, Internal::PluginManagerPrivate and so on… Is 
 there some kind of graphics, documents or smthng else?
 Thanks and peace!

 Thanks again!

Try to implement features that *you* personally are missing, or fix bugs that 
you are hitting (if any).

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] [Development] [FYI] if you find diffing in gerrit slow ...

[Konstantin Tokarev]

11.09.2014, 19:00, Oswald Buddenhagen oswald.buddenha...@digia.com:
 ... then use chrome/chromium.
 because the slowness is coming from gerrit running massive amounts of js
 in your browser, and chrome is literally an order of magnitude faster at
 it than firefox (no clue about ie).
 if you already use it, well, tough luck. get a cryo-cooled cpu, or
 something.
 if you hate it (like i do), tough luck, too - it won't get better until
 we upgrade to gerrit 2.11 (presumably), which is more than half a year
 in the future.

Well, one can just turn off syntax highlighting to get rid of this issue.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Ugly font rendering?

[Konstantin Tokarev]

23.06.2014, 16:33, Nikos Chantziaras rea...@gmail.com:
 I was using Qt Creator 2.8.1 and decided to try 3.1.1. So I installed it
 using the official Linux installer.

 The fonts look washed out and lack blackness, making them tiring to
 read. Here's how fonts look in Creator 2.8.1:

    http://s15.postimg.org/es4jn3xdn/qt4.png

 and here's how they look in 3.1.1:

    http://s28.postimg.org/lic77ee25/qt5.png

 Is there anything I can do about this?

As for me, it would look quite nice if full hinting was enabled.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Compiling Qt Creator in under 3 minutes

[Konstantin Tokarev]

22.05.2014, 11:50, Christian Kandeler christian.kande...@digia.com:

  On 05/21/2014 09:28 PM, Jussi Pakkanen wrote:
   On Wed, May 21, 2014 at 10:10 PM, André Pönitz apoen...@t-online.de
   mailto:apoen...@t-online.de wrote:

   I am not sure I understood what the unity build does. Closest I can
   imagine
   is that it concatenates some (or all?) translation units into one
   and tries
   to compile the result. Of course that would not work with normal C++
   projects
   but would impose rather harsh restriction on naming conventions and 
 code
   structure, so this can't be what is meant as this interpretation
   conflicts
   with the in theory unity builds should not require any code changes.

   There is a more involved explanation in Meson wiki:

   https://sourceforge.net/p/meson/wiki/Unity%20builds/
  There may also be some bugs in the source that need to be fixed before
  Unity compiles work. As an example, if both src1.c and src2.c contain a
  static function or variable of the same name, there will be a clash.

  How on earth is that a bug? That's a perfectly legal and normal thing to
  do, as the concept of translation units is well-defined. By merging them
  all together, one can probably even introduce subtle semantic changes
  (though admittedly that's just a gut feeling, I don't have a concrete
  example).
  What is the use case anyway? I guess it can only be an area where
  incremental builds are irrelevant. CI?

For example, we use such setup to reduce binary size of embedded application,
where LTO is not available.

-- 
Regards, Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Clang based code model

[Konstantin Tokarev]

14.02.2014, 23:57, Pawel pawelfaro...@wp.pl:
 Hello,

 I've tried the Clang code model and unfortunately found out that it
 doesn't support the old KR style function parameter declarations like
 this:

 int func(a, b, c)
 int a;
 int b;
 int c;
 {
    return a + b + c;
 }

 You may not believe there are still people who use it... and almost every
 IDE is at lost with it :) Do you think that there is anything that can be
 done with it?

clang compiler parses this code just fine, so it should be possible to fix.

$ clang -cc1 -ast-dump knr_params.c
TranslationUnitDecl 0x200cf70 invalid sloc
|-TypedefDecl 0x200d240 invalid sloc __builtin_va_list 'char *'
`-FunctionDecl 0x200d380 knr_params.c:1:1, line:7:1 func 'int (int, int, int)'
  |-ParmVarDecl 0x200d280 line:2:5, col:9 a 'int'
  |-ParmVarDecl 0x200d2c0 line:3:5, col:9 b 'int'
  |-ParmVarDecl 0x200d300 line:4:5, col:9 c 'int'
  `-CompoundStmt 0x200d4a8 line:5:1, line:7:1
`-ReturnStmt 0x200d498 line:6:4, col:19
  `-BinaryOperator 0x200d480 col:11, col:19 'int' '+'
|-BinaryOperator 0x200d440 col:11, col:15 'int' '+'
| |-ImplicitCastExpr 0x200d420 col:11 'int' LValueToRValue
| | `-DeclRefExpr 0x200d3ec col:11 'int' lvalue ParmVar 0x200d280 'a' 
'int'
| `-ImplicitCastExpr 0x200d430 col:15 'int' LValueToRValue
|   `-DeclRefExpr 0x200d404 col:15 'int' lvalue ParmVar 0x200d2c0 'b' 
'int'
`-ImplicitCastExpr 0x200d470 col:19 'int' LValueToRValue
  `-DeclRefExpr 0x200d458 col:19 'int' lvalue ParmVar 0x200d300 'c' 
'int'


Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Disable shadow build permanently for a project.

[Konstantin Tokarev]

24.09.2013, 05:14, Joseph Crowell joseph.w.crow...@gmail.com:
 Is there a config that can be added to the .pro file or something that
 can be uploaded to git which would automatically disable shadow building
 on fresh clones of a project? I have a project with data files in the
 run folder and a version tool which runs on each compile to generate a
 version header. Both of these things break when using shadow builds. In
 cases like this it would be nice to be able to disable shadow build on a
 project level. I don't think I am the only Qt Creator user that would
 like this. It would eliminate a bit of instruction from our wiki as well.

All generated files should be placed into build directory.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Disable shadow build permanently for a project.

[Konstantin Tokarev]

24.09.2013, 12:56, Frédéric Marchal frederic.marc...@wowtechnology.com:
  24.09.2013, 05:14, Joseph Crowell joseph.w.crow...@gmail.com:
  Is there a config that can be added to the .pro file or something that
  can be uploaded to git which would automatically disable shadow building
  on fresh clones of a project? I have a project with data files in the
  run folder and a version tool which runs on each compile to generate a
  version header. Both of these things break when using shadow builds. In
  cases like this it would be nice to be able to disable shadow build on a
  project level. I don't think I am the only Qt Creator user that would
  like this. It would eliminate a bit of instruction from our wiki as well.
  All generated files should be placed into build directory.

 The problem is about manually constructed files.

 The files can be dynamically loaded images, lists of messages, I/O mapping
 files, and so on.

Since your executable is in build directory, there should be no problem.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Disable shadow build permanently for a project.

[Konstantin Tokarev]

24.09.2013, 12:52, Frédéric Marchal frederic.marc...@wowtechnology.com:
  Is there a config that can be added to the .pro file or something that
  can be uploaded to git which would automatically disable shadow building
  on fresh clones of a project? I have a project with data files in the
  run folder and a version tool which runs on each compile to generate a
  version header. Both of these things break when using shadow builds. In
  cases like this it would be nice to be able to disable shadow build on a
  project level. I don't think I am the only Qt Creator user that would
  like this. It would eliminate a bit of instruction from our wiki as well.

 You are not the only one to wish for that feature.

 I heavily rely on text files that are stored in the repository but must be
 accessible to the application.

You can copy them to build directory, or make a symbolic link.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Disable shadow build permanently for a project.

[Konstantin Tokarev]

24.09.2013, 13:51, Frédéric Marchal frederic.marc...@wowtechnology.com:
  24.09.2013, 12:56, Frédéric Marchal frederic.marc...@wowtechnology.com:
   24.09.2013, 05:14, Joseph Crowell joseph.w.crow...@gmail.com:
   Is there a config that can be added to the .pro file or something that
   can be uploaded to git which would automatically disable shadow
  building on fresh clones of a project? I have a project with data
  files in the run folder and a version tool which runs on each compile
  to generate a version header. Both of these things break when using
  shadow builds. In cases like this it would be nice to be able to
  disable shadow build on a project level. I don't think I am the only
  Qt Creator user that would like this. It would eliminate a bit of
  instruction from our wiki as well.
   All generated files should be placed into build directory.
  The problem is about manually constructed files.

  The files can be dynamically loaded images, lists of messages, I/O
  mapping files, and so on.
  Since your executable is in build directory, there should be no problem.

 The manually created files are in the source directory. There lies the
 problem.

Why are they created there?

Anyway, if you first build with qmake and then import build into Qt Creator 
(like I do),
you won't get shadow build accidentally.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Xcode 5 no longer has GDB included. Ramifications?

[Konstantin Tokarev]

20.09.2013, 16:54, Michael Jackson imikejack...@gmail.com:
 On Sep 19, 2013, at 5:35 PM, André Pönitz 
 andre.poen...@mathematik.tu-chemnitz.de wrote:

  On Thu, Sep 19, 2013 at 01:19:13PM -0700, Jonathan S. Shapiro wrote:
  If GDB can support code coming from clang-llvm, perhaps a simpler interim
  solution would be to build and ship a copy of gdb in the OSX bundle for
  QtCreator?
  I don't really think that's a viable option, certainly not one that
  requires less work than bringing real LLDB support up to snuff. We used to
  ship usable GDB builds for Windows a while ago when the MinGW builds
  where lacking scripting support and the whole process was a huge sink of
  ressources. I'd rather not repeat that, for various reasons.

  LLDB exposes a lot of its innards to its Python bindings in a 
 straight-forward
  manner, so it's really just cobbling a few things together. Really no
  rocket science. On side provides a full debugger, the other side needs
  a full debugger, missing are only (some of the) connections.

  Documentation could be a bit better (where not...), so one doesn't end up
  in dead ends too often, but in general it's a predictable and rewarding
  environment to work in. I'd rather spend energy moving forward than to
  maintain last year's status quo.

  Andre'

 Thanks all for the comments, I'm going to add my own 2 cents worth since I am 
 a glass is half empty kind of person but also a realist.

 OS X 10.9 Mavericks will most likely require Xcode 5. Based on History this 
 will probably hold true although I really hope I am wrong. Why? Because 
 without a viable debugger in QtCreator under Xcode 5 anyone upgrading to OS X 
 10.9 Mavericks will basically render QtCreator useless for Debugging. You can 
 still compile and run, just not debug. Now it sounds like QtCreator is 
 getting close to a release so the LLDB support will not be in there. And the 
 project needs some programmers to help write all the glue code and then test 
 everything. I'll bet this takes until next summer to get completed. I'm not 
 placing blame anywhere, just my opinion based on the comments in here about 
 finding the time to write the codes. So for those that are using QtCreator 
 but want to run the latest and greatest OS X you have 2 choices:

 1: Run OS X 10.9 but have NO debugger.
 2: Run OS X 10.8 and have a debugger.

 There are a few other possible options:
 1: The programmer can attempt to compile a newer GDB but from my googling 
 that seems to go nowhere and just does not work.

Use gentoo prefix, macports, or something like these.

 2: Purchase a commercial debugger like Intels IDB which I thought was GDB 
 Compatible. Which makes me wonder if one can swap IDG for GDB and QtCreator 
 will know the difference? Comments on this idea?

I doubt IDB support gdb-compatibly python API, so it probably won't be usable 
from within Creator.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator 2.8 on Linux - g++ version

[Konstantin Tokarev]

02.07.2013, 14:14, Ziller Eike eike.zil...@digia.com:
 On 02.07.2013, at 11:22, Peter Pearson pe...@thefoundry.co.uk wrote:

  Hi,

 Hi,

  While trying the beta of 2.8 on Linux 64, I notice it now needs a
  libstdc++ for g++ 4.6 or greater.

  This is slightly annoying, as for platforms like RHEL / CentOS 6.4, they
  come with g++ 4.4, so it's not possible to run Qt Creator 2.8 without
  building a new g++ from source using either setting the LD_LIBRARY_PATH
  to the newer libstdc++ location, or symb-linking it.

  Was this decision by design?

 Qt Creator 2.7 packages were built on Ubuntu 10.04 LTS.
 Qt Creator 2.8 packages are built on Ubuntu 11.10, which puts it in line with 
 the Qt 5 packages.
 (And also support for Ubuntu 10.04 LTS has ended in May this year.)

What is the point of binary packages if they don't work on reasonably modern 
distros?
Why not build on CentOS 6.x instead?


  Does Qt Creator need to be built with g++
  4.6 or above for say newer C++ features?

 No. You should have no problems building Qt Creator yourself.

 Br, Eike

 --
 Eike Ziller, Senior Software Engineer - Digia, Qt

 Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
 Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
 Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
 HRB 144331 B

 ___
 Qt-creator mailing list
 Qt-creator@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator 2.8 on Linux - g++ version

[Konstantin Tokarev]

02.07.2013, 15:15, Peter Pearson pe...@thefoundry.co.uk:
 On 02/07/13 12:02, Ziller Eike wrote:

  It is basically impossible to provide a single binary build that works even 
 on all reasonably modern distros (however that might be defined). We have 
 seen that over and over again, and that's why it was decided a longer time 
 ago to use Ubuntu as a reference platform. (Even providing a binary package 
 that works through multiple Ubuntu versions has its trickiness as we've seen 
 in the past.)

 Sorry, but I don't believe this is true, at least in a practical sense
 if you're willing to build with older compilers - I write software for
 Linux distros, and we build with g++ 4.1 for precisely this reason: so
 that it's pretty much guaranteed to work on a useful range of modern and
 older systems.

Actually, you don't have to build with g++ 4.1. RHEL 5 / CentOS 5 comes with
g++ 4.4 in repos, and you can build portable Linux binaries with it keeping
compatibility with RHEL 5.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Is there a way to load qtcreator plugins 'manually'?

[Konstantin Tokarev]

20.06.2013, 17:56, Guido Seifert warg...@gmx.de:
  The plugin manager doesn't support this. The list of (potential) plugins is 
 initialized before loading any plugin.

 Thought so. :-(
 Another ugly problem. My plugin downloads updates from a website. Under Linux 
 I just write
 the updated plugins in the correct folder and restart. 

Doing so can easily crash the process, if plugin is in use.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Is there a way to load qtcreator plugins 'manually'?

[Konstantin Tokarev]

20.06.2013, 20:58, Guido Seifert warg...@gmx.de:
  Thought so. :-(
  Another ugly problem. My plugin downloads updates from a website. Under 
 Linux I just write
  the updated plugins in the correct folder and restart.
  Doing so can easily crash the process, if plugin is in use.

 I would not care much, since I'd restart the creator immediately after the 
 write.

... if it didn't crash earlier.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 11:28, Orgad Shaneh org...@gmail.com:
 Hi,
 I'm trying to create interactive rebase support for Git plugin. WIP change 
 can be found here.

 I created a small tool that communicates with qtc using a local socket. It is 
 used as GIT_EDITOR.

I doubt this feature is really useful. You have to provide real GUI so that 
user can reorder, 
delete, squash commits and edit their messages from it, otherwise it has no 
advantages over command
line rebase.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 13:58, Orgad Shaneh org...@gmail.com:
 On Thu, Feb 14, 2013 at 11:57 AM, Konstantin Tokarev annu...@yandex.ru 
 wrote:
 14.02.2013, 11:28, Orgad Shaneh org...@gmail.com:
 Hi,
 I'm trying to create interactive rebase support for Git plugin. WIP change 
 can be found here.

 I created a small tool that communicates with qtc using a local socket. It 
 is used as GIT_EDITOR.

 I doubt this feature is really useful. You have to provide real GUI so that 
 user can reorder,
 delete, squash commits and edit their messages from it, otherwise it has no 
 advantages over command
 line rebase.

 --
 Regards,
 Konstantin

 Have you tried it? I open an editor for that...

git rebase -i opens an editor too

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 14:00, Orgad Shaneh org...@gmail.com:
 On Thu, Feb 14, 2013 at 11:59 AM, Konstantin Tokarev annu...@yandex.ru 
 wrote:
 14.02.2013, 13:58, Orgad Shaneh org...@gmail.com:
 On Thu, Feb 14, 2013 at 11:57 AM, Konstantin Tokarev annu...@yandex.ru 
 wrote:
 14.02.2013, 11:28, Orgad Shaneh org...@gmail.com:
 Hi,
 I'm trying to create interactive rebase support for Git plugin. WIP 
 change can be found here.

 I created a small tool that communicates with qtc using a local socket. 
 It is used as GIT_EDITOR.

 I doubt this feature is really useful. You have to provide real GUI so 
 that user can reorder,
 delete, squash commits and edit their messages from it, otherwise it has 
 no advantages over command
 line rebase.

 --
 Regards,
 Konstantin

 Have you tried it? I open an editor for that...

 git rebase -i opens an editor too

 --
 Regards,
 Konstantin

 For this you need to run it in a shell... I open an editor inside Qt Creator.

Creator's PlainTextEditor has no advantages over vim for this purpose. Vim has 
proper highlighting though.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 14:00, Orgad Shaneh org...@gmail.com:
 On Thu, Feb 14, 2013 at 11:59 AM, Konstantin Tokarev annu...@yandex.ru 
 wrote:
 14.02.2013, 13:58, Orgad Shaneh org...@gmail.com:
 On Thu, Feb 14, 2013 at 11:57 AM, Konstantin Tokarev annu...@yandex.ru 
 wrote:
 14.02.2013, 11:28, Orgad Shaneh org...@gmail.com:
 Hi,
 I'm trying to create interactive rebase support for Git plugin. WIP 
 change can be found here.

 I created a small tool that communicates with qtc using a local socket. 
 It is used as GIT_EDITOR.

 I doubt this feature is really useful. You have to provide real GUI so 
 that user can reorder,
 delete, squash commits and edit their messages from it, otherwise it has 
 no advantages over command
 line rebase.

 --
 Regards,
 Konstantin

 Have you tried it? I open an editor for that...

 git rebase -i opens an editor too

 --
 Regards,
 Konstantin

 For this you need to run it in a shell... I open an editor inside Qt Creator.

BTW, you can already use Qt Creator as git editor (just set EDITOR variable to 
'qtcreator -client',
or change core.editor throught git config to make it persistent).

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 14:25, Orgad Shaneh org...@gmail.com:
 On Thu, Feb 14, 2013 at 12:04 PM, Konstantin Tokarev annu...@yandex.ru 
 wrote:
 My point is that there is no need for GUI just imitating behavior of 
 command-line tool with GUI'ish text editor

 --
 Regards,
 Konstantin

 You could say that on any other action. Why is it different than commit

Commit *has* GUI.

or log or diff?

Ideally, they also should be reworked. But at least they cannot damage user 
repository because of saving/closing editor lightly.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 14:27, Orgad Shaneh org...@gmail.com:
 Did you actually try this? qtcreator -client returns immediately.

Yes, works for me. It opens file in current Qt Creator instance.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 14:29, Orgad Shaneh org...@gmail.com:
 On Thu, Feb 14, 2013 at 12:28 PM, Konstantin Tokarev annu...@yandex.ru 
 wrote:
 14.02.2013, 14:27, Orgad Shaneh org...@gmail.com:
 Did you actually try this? qtcreator -client returns immediately.

 Yes, works for me. It opens file in current Qt Creator instance.

 --
 Regards,
 Konstantin

 Well, on Windows it immediately returns. Does it return when the editor is 
 closed?

It should open new Qt Creator instance if it is not already running, otherwise 
it should
return, and file is open in running instance. If it does not behave like this 
on Windows,
it is a separate issue.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Git interactive rebase

[Konstantin Tokarev]

14.02.2013, 14:34, Orgad Shaneh org...@gmail.com:
 But if an instance is running, it immediately returns and the rebase proceeds 
 without letting the user edit anything!

Ah, you are right. Sorry for noise.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] making static app under creator

[Konstantin Tokarev]

16.01.2013, 17:39, Duane Hebert duane.heb...@group-upc.com:
 Linux platform.  TinyCore.  Stripped down for a controller.

 I'm building already with CONFIG -= qt.  But if I run ldd, I get a few 
 dependancies - libstdc++, libc etc.

You can get rid of them by using proper QMAKE_C(XX)FLAGS 

http://www.trilithium.com/johan/2005/06/static-libstdc/


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt-Creator and Qwt under Win, MinGW

[Konstantin Tokarev]

15.01.2013, 14:52, Martin Mensch mmen...@siegrist.de:
 Hi,

 I tried to install Qwt under Win7 compiled with MinGW which works so far that 
 I can compile and run the examples.
 Now I wanted to install Qwt to Qt Creator so I can use the integrated 
 designer to setup my forms. But this fails. When  using the integrated 
 designer I get a message under Tools | Form Editor | About Qt Designer 
 Plugins... - Failed plugins:
 The plugin 
 'C:/Qt/Qwt/6.0.2/designer/plugins/designer/qwt_designer_plugin.dll' uses 
 incompatible Qt library. Expected build key Windows msvc release 
 full-config, got Windows mingw release full-config
 Googling for that I found some comments that say it is because Qt Creator is 
 compiled with Visual Studio and cannot work together with dlls compiled with 
 MinGW.
 So I just want to ask the Qt Creator experts:
 - Is that the reason for this message?

Yes. Executables and plugins built by MinGW and MSVC are binary incompatible. 
They cannot be used together.

 - Is there a ready to use Qt Creator compiled with MinGW?
 - Are there other ways to get me working with Qwt and Qt Creator?

Rebuild designer plugin(s) with Visual Studio [Express], or ask Qwt to provide 
them.

 - What about stand alone Qt Designer? Does it have the same issue?

You can get pre-compiled Qt built with MinGW. It's Designer should be 
compatible with your plugin(s).

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] gerrit-speak

[Konstantin Tokarev]

13.12.2012, 21:15, Cristian Tibirna tibi...@kde.org:
 (Rethoric: should this go to a more generic qt list?)

 Hello

 (First a side question, is there a more consequent documentation about the use
 of gerrit?)

 Is it only me that finds the -1 review default message in gerrit rather
 irritating?

 I would prefer that you didn't submit this

I don't see anything irritating here. I could agree if it was Do not submit 
like -2.


 reads to my brain much like go f*k yourself without the raw words.

Well, it's your own words...


 I get all the idea of the automating thing and all, and that machines have no
 emotion, but, if I don't miss something obvious (this happens to me though...)
 and if that message is configurable, how about

 This requires more work

== I'd prefer you didn't submit this.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] .pro files parser Interface

[Konstantin Tokarev]

12.12.2012, 14:23, Jeandet alexis alexis.jean...@lpp.polytechnique.fr:
 Hello,

 I would like to write a Qt-creator plugin for flashing some
 microcontrollers(such as CortexM family or Leon3) because I also use
 Qt-creator as standalone IDE without Qt library. I've read this good
 introduction
 http://www.vcreatelogic.com/downloads/files/Writing-Qt-Creator-Plugins.pdf
 and I'm able to run a simple plugin.
 But in my case I would like to access pro/pri files from my plugin, I've
 looked inside Qt-creator source and specially inside Qt4ProjectManager
 plugin, I've found some informations in Qt4ProFileNode class and
 Qt4Project::update*Model.

It would be great if your plugin was NOT bound to Qt4ProjectManager by design.
This may require adding new APIs to ProjectExplorer, depending on data you'd
like to access.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] .pro files parser Interface

[Konstantin Tokarev]

12.12.2012, 16:50, Jeandet alexis alexis.jean...@lpp.polytechnique.fr:
 Le 12/12/2012 13:23, Konstantin Tokarev a écrit :

  12.12.2012, 14:23, Jeandet alexis alexis.jean...@lpp.polytechnique.fr:
  Hello,

  I would like to write a Qt-creator plugin for flashing some
  microcontrollers(such as CortexM family or Leon3) because I also use
  Qt-creator as standalone IDE without Qt library. I've read this good
  introduction
  http://www.vcreatelogic.com/downloads/files/Writing-Qt-Creator-Plugins.pdf
  and I'm able to run a simple plugin.
  But in my case I would like to access pro/pri files from my plugin, I've
  looked inside Qt-creator source and specially inside Qt4ProjectManager
  plugin, I've found some informations in Qt4ProFileNode class and
  Qt4Project::update*Model.
  It would be great if your plugin was NOT bound to Qt4ProjectManager by 
 design.

 Yes this is also my feeling.

  This may require adding new APIs to ProjectExplorer, depending on data you'd
  like to access.

 In my case I need to get some customs variables in pro/pri files. They
 look like:

 CPU=stm32f4xxxG
 BSP=STM32F4Discovery
 DESTDIR=somepath

 My plugin would use them to find the binary file to load (This could be
 done with /ProjectExplorer::RunConfigurations/  I think), but it need to
 know the CPU target and the the BSP to use the good tool and protocol to
 flash the target.

 The problem is that they are in different files = I need to follow
 inclusion and sometime I need to evaluate qmake functions such as
 contains(variablename, value). I would prefer to use the same API as
 QtCreator,qmake,...  if there is one?

I think the best API here would be Unix way. E.g. make an executable (or 
script)
implementing flashing process which takes CPU, BSP, and DESTDIR as
command line parameters or (slightly worse) environment variables.

Then you will be able to add flashing step to your qmake project (or any other 
project
kind) as a custom target, or set up custom deployment step in Qt Creator. If 
you want
to configure CPU, BSP, and DESTDIR in .pro file, you create variables and then 
use
them to run your flashing application.

No plugin is needed.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Any Madde users left?

[Konstantin Tokarev]

11.12.2012, 19:39, Attila Csipa q...@csipa.in.rs:
 On 11/12/12 16:57, Christian Kandeler wrote:

  if there is anyone out there who would be terribly inconvenienced if Qt
  Creator 2.7 no longer supported Fremantle and Harmattan development via
  the Madde framework, they are advised to speak up now.

 Not terribly, but it certainly is annoying to pile up the various
 versions of QtCreator as it has a non-overlapping set of supported
 platforms for different versions. I have one QtCreator for Symbian, one
 QtCreator for Qnx, one QtCreator for Nemo, had one QtCreator for MeeGo,
 now one QtCreator for Maemo, one for... you get the idea (and one latest
 head build for my own hackery ;). I understand that nobody breaks things
 voluntarily and that the real solution is to have maintainers, but it's
 just easier to have separate builds than taking up maintainership (which
 in turn kind of defeats the whole pluggable architecture concept of
 QtCreator).

Well, if Qt Creator had stable plugin API, in most cases it would be possible 
just
recompile old unmaintained plugin against new Qt Creator to get it working...

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Kit-Device relation

[Konstantin Tokarev]

16.11.2012, 13:11, Christian Kandeler christian.kande...@digia.com:
 On 11/15/2012 07:10 PM, Konstantin Tokarev wrote:

    But
    what if there is no run configuration... ?
    Then there's no need to choose device, device type is enough.
  I don't understand your reasoning. Where would you deploy to in that case?
  Nowhere. Why do I need to deploy if I don't know where to run it? :)

 Does the term library ring a bell?

Surely. If it compiles it must be perfect and must not require running even 
smallest
test program.

Well, there is one real use case: when run configuration just cannot be set up 
in terms
of Qt Creator and requires direct manipulations with device.

However, I don't get how does this all relate to independence of build 
configuration (i.e.
device type) and IP of device where thing is deployed and maybe run

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Shadow-Build

[Konstantin Tokarev]

16.11.2012, 03:07, André Pönitz andre.poen...@mathematik.tu-chemnitz.de:
 On Thu, Nov 15, 2012 at 12:46:09PM +0100, Tobias Hunger wrote:

  On 12.11.2012 08:29, Michael Klank wrote:
  Is there a way to disable “Shadow-Build” by default? If this is not
  possible, is it doable via plugin? I already have plugin which takes
  care of a loaded/changed project. If I can control the Shadow-Build
  option from there, it would be nice. Can anyone point me in the right
  direction?
  Hi Michael!

  Just change the build directory to point to your source directory.

  Do you think we should introduce a UI for this again? I really would
  like to discourage in-source building as much as possible as it does
  cause all kind of really hard to pinpoint issues when switching between
  configurations.

 I think a global option Offer shadow builds by default (on by
 default) would do the trick.

It should affect all ProjectManager plugins, not only Qt4ProjectManager, 
shouldn't it?
So we need additional API (right now plugins don't share any knowledge about
what 'shadow build' is).

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Text Editor - Behavior settings stored on a per project basis.

[Konstantin Tokarev]

15.11.2012, 11:59, Orgad Shaneh org...@gmail.com:
 On Thu, Nov 15, 2012 at 9:54 AM, Diego Iastrubni diegoi...@gmail.com wrote:
 On Wed, Nov 14, 2012 at 4:40 PM, Orgad Shaneh org...@gmail.com wrote:
 In Projects Mode (5th on the side bar) there are tabs for Editor and Code 
 Style.
 See http://qt-project.org/doc/qtcreator-2.6/creator-editor-settings.html 
 and http://qt-project.org/doc/qtcreator-2.6/creator-code-style-settings.html

 I wish it could be done per document. VIM/kate modelines support would be a 
 good feature.

 How would you configure it?

By specially formed comment in the beginning or at the end of document.
@sa vim modelines.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Kit-Device relation

[Konstantin Tokarev]

15.11.2012, 19:34, Christian Kandeler christian.kande...@digia.com:
 On 11/15/2012 04:23 PM, Orgad Shaneh wrote:

  On Thu, Nov 15, 2012 at 5:10 PM, Ziller Eike eike.zil...@digia.com
  mailto:eike.zil...@digia.com wrote:

  If that means pulling the device out of the Kit and putting it
  somewhere else (where?), or if that means making it easier and more
  obvious to switch the device in a kit, I'm not sure.

  Regarding the 'where' question, I think it should appear in the
  project's Run Configuration

 So the user should be able to create n run configs using n different
 devices? For the same project and kit? And don't forget deployment,
 which also needs the device: Do you want the device to be settable
 separately for every single deploy step? Or per deploy configuration? Or
 should it always be the same as the one for the run configuration?

It should be the same for all deployment steps and run configuration.

 But
 what if there is no run configuration... ?

Then there's no need to choose device, device type is enough.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Kit-Device relation

[Konstantin Tokarev]

15.11.2012, 20:19, Christian Kandeler christian.kande...@digia.com:
 On 11/15/2012 05:15 PM, Konstantin Tokarev wrote:

  But
  what if there is no run configuration... ?
  Then there's no need to choose device, device type is enough.

 I don't understand your reasoning. Where would you deploy to in that case?

Nowhere. Why do I need to deploy if I don't know where to run it? :)

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Configuration changes

[Konstantin Tokarev]

09.10.2012, 16:54, Harri Pasanen ha...@mpaja.com:
 Well, the N9 skin is quite close to many Android devices.   I faintly
 recall seeing some docs on creating your own skins as well.

 Are you saying that Simulator will no longer be supported in Qt
 Creator?  Is it dropped already in 2.6?

 For me personally the Simulator was quite good.  It was fast, comparable
 to the iPhone simulator.  The QEmu based Android simulator is much slower.

You compare apples and oranges. qemu is _emulator_, not _simulator_.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] premake4 plugin

[Konstantin Tokarev]

28.09.2012, 16:27, Daniel Price daniel.pr...@fxhome.com:

  Hi what’s the situation with the premake4 plugin?

  I really need this as I’m looking to switch to premake4. I tried grabbing 
 the source form git but it didn’t build against the latest build of Creator 
 (2.6.x - something about a missing ide_version.h in CorePlugin and gazillion 
 other errors). I’m using OSX 10.8.

Unfortunately, PremakeProjectManager is not compatible with 2.6, mostly because 
of dramatic changes in API related to Kits, which are still in flux (e.g., Kits 
were Profiles not so long ago).

I'll port it to 2.6/master after releasing 0.3 version (compatible with Qt 
Creator 2.3.x-2.5.x), dropping compatibility with older versions.

  Anyone else using premake4 projects with Creator?

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] [Development] Stepping down as maintainer

[Konstantin Tokarev]

21.09.2012, 01:08, leandro.m...@nokia.com leandro.m...@nokia.com:
 Hi everyone,

 it's been an awesome time participating in the development of Qt Creator. 
 However, I've recently decided to follow a different path and I will no 
 longer be able to maintain the text editors and C++ language support. A new 
 maintainer will be suggested soon.

 Thanks for all of those who contribute to the success of Qt and let it 
 continues to rock!

We will miss you :(

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Is MSVC on Windows supported?

[Konstantin Tokarev]

06.09.2012, 15:16, Harri Pasanen ha...@mpaja.com:
 What I took away from is that you many not want to use icc (Intel) if
 you plan to run on AMD, as the generated code looks for the processor
 brand, not the supported instruction set.

That's not true for recent versions. (Thiago: could you confirm?)

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Is MSVC on Windows supported?

[Konstantin Tokarev]

05.09.2012, 15:00, Peter Kümmel syntheti...@gmx.net:
 On 05.09.2012 12:50, Peter Kümmel wrote:

  We build it regularly with MSVC without any magic incantations.
  And of course we care about MSVC as it's the reference toolchain for
  this platform. (I personally do not give a^W^Wcare about MinGW but
  that's another story. ;))
  MinGW will have a rise because MS again has the worst C++ support,
  MSVC2012 is a joke.

 When looking for a MinGW alternative with good C++11 support and
 better debugging than gdb I stumbled over the Intel compiler.

 I know the non-Studio debugger support for msvc isn't that good,
 and using msvc features is prohibited.

 Would this improve when a Intel compiler/toolchain is used?
 Is there a Intel debugger/API which could be integrated into QtCreator?

On Windows Intel compiler is MSVC-compatible, so anything that can debug
MSVC should be able to debug Intel.

Try CDB integration.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Why Creator's Qbs plugin need to special process for Qt?

[Konstantin Tokarev]

30.08.2012, 12:37, Theo de Vries t.j.a.devr...@gmail.com:
 2012/8/29 Konstantin Tokarev annu...@yandex.ru:

  29.08.2012, 07:55, Loaden loa...@gmail.com:
  See:
  void QbsProject::createBuildProject(const QString buildProjectName, 
 QtSupport::BaseQtVersion *qtVersion)
  {
  if (qtVersion) {
  if (qtVersion-defaultBuildConfig() == 
 QtSupport::BaseQtVersion::DebugBuild || qtVersion-defaultBuildConfig() == 
 QtSupport::BaseQtVersion::BuildAll) {
  buildConfiguration[qbs.buildVariant] = debug;
  } else {
  buildConfiguration[qbs.buildVariant] = release;
  }
  buildConfiguration[qt/core.qtPath] = 
 qtVersion-sourcePath().toString();

  } else {
  buildConfiguration[qbs.buildVariant] = debug;
  }

  I don't like the design.
  I thought QbsProjectManager should like CMakeProjectManager.
  No need Qt depends!
  Actually, missing Qt dependence is a big gap in CMakeProjectManager which 
 needs to be fixed.

  --
  Regards,
  Konstantin
  ___
  Qt-creator mailing list
  Qt-creator@qt-project.org
  http://lists.qt-project.org/mailman/listinfo/qt-creator

 Konstantin, would you mind explaining your point of view?

Proper build system plugin should allow to select Qt version, used in project, 
from UI.
In current 2.6 and master this implies it should use Qt version from selected 
profile.

 I can see
 that Qt dependence is an advantage when building a Qt project, but
 when doing a non-Qt development, I agree with Loaden that it is a pain
 to have a dependency on qtVersion etc as in the current design of qbs.

Awareness of Qt versions in plugin has nothing to do with forcing of Qt 
dependence
on project.


-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Why Creator's Qbs plugin need to special process for Qt?

[Konstantin Tokarev]

29.08.2012, 07:55, Loaden loa...@gmail.com:
 See:
 void QbsProject::createBuildProject(const QString buildProjectName, 
 QtSupport::BaseQtVersion *qtVersion)
 {
     if (qtVersion) {
     if (qtVersion-defaultBuildConfig() == 
 QtSupport::BaseQtVersion::DebugBuild || qtVersion-defaultBuildConfig() == 
 QtSupport::BaseQtVersion::BuildAll) {
     buildConfiguration[qbs.buildVariant] = debug;
     } else {
     buildConfiguration[qbs.buildVariant] = release;
     }
     buildConfiguration[qt/core.qtPath] = 
 qtVersion-sourcePath().toString();

     } else {
     buildConfiguration[qbs.buildVariant] = debug;
     }

 I don't like the design.
 I thought QbsProjectManager should like CMakeProjectManager.
 No need Qt depends!

Actually, missing Qt dependence is a big gap in CMakeProjectManager which needs 
to be fixed.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Minimizing compile-time conditionals in Qt Creator

[Konstantin Tokarev]

28.08.2012, 11:56, Christian Kandeler christian.kande...@nokia.com:
 However, most of the time that is not the case, such as in
 this example:
  QStringList rc(QLatin1String(.svn));
  #ifdef Q_OS_WIN
  rc.push_back(QLatin1String(_svn));
  #endif
  return rc;
 The code would compile on any platform, but we hide it from the compiler
 and Qt Creator's code model on all of them except Windows. This means
 that if, for instance, you are developing on Linux and you are using
 Creator's refactoring support to rename the rc variable in the above
 example, Creator will miss the occurrence inside the #ifdef'ed block, as
 that one is not part of the code model. 

I think this issues is a fault of Qt Creator. While I understand that it may be
impossible to parse disabled block completely in some cases (not in this one
btw), it would be very desirable to support basic things like code navigation 
and
variable renaming for disabled blocks too. Otherwise maintaining cross-platform
code (not only for desktop platforms!) is sometimes painful.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Minimizing compile-time conditionals in Qt Creator

[Konstantin Tokarev]

28.08.2012, 16:19, Stephen Chu step...@ju-ju.com:
 On 8/28/12 3:56 AM, Christian Kandeler wrote:

    QStringList rc(QLatin1String(.svn));
    if (Utils::HostOsInfo::isWindowsHost())
    rc.push_back(QLatin1String(_svn));
    return rc;

 Doesn't this generate dead code that will never be executed on platforms
 other than the intended one?

 My understanding is unless the function is declared as constexp and
 build with C++11 option, the compiler will not be able to optimize out
 the code for non-targeted platform.

Your understanding is correct, but probably elimination of dead code is not too
interesting here.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qtcreator 2.5.2 issues

[Konstantin Tokarev]

27.08.2012, 12:14, Ramakanthreddy_Kesireddy 
ramakanthreddy_kesire...@mahindrasatyam.com:
 Hi,

 I have taken Qt5 Beta sources from link 
 http://releases.qt-project.org/qt5.0/beta-snapshots/latest/

 After Qt5 build is successful on windows, am trying to configure Qt5 Beta 
 using Qtcreator 2.5.2 using below steps

Qt Creator 2.5 is incompatible with Qt 5. Use 2.6 or master branch instead.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qtcreator 2.5.2 issues

[Konstantin Tokarev]

27.08.2012, 15:13, Ramakanthreddy_Kesireddy 
ramakanthreddy_kesire...@mahindrasatyam.com:
 Hi,

 Could you please let me know where can we get QtCreator 2.6 as
 it is not released?

Essentially the same way as you get unreleased Qt 5: from git

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] LLDB support

[Konstantin Tokarev]

27.08.2012, 15:24, Michael Seydl michael.se...@gmail.com:
 Hi.

 Progress. Progress. :) I'm push my changes on my github account soon, but 
 here's the caveat when using lldb on Mac. When debugging binaries build with 
 llvm-gcc almost all the lldb python stl formatter and helper are broken. And 
 even if someone would take it on to write some new formatters it would be 
 hard for the debugger to distinguish which compiler actually build the binary.

 Therefore my implementation of the lldb debugger just debugs binaries 
 properly, which were build with clang. Guess that's a bummer as clang is 
 still and unsupported mkspec.

 What do you think?

I think it's better than nothing, but should not be used instead of gdb by 
default.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] LLDB support

[Konstantin Tokarev]

27.08.2012, 15:24, Michael Seydl michael.se...@gmail.com:
 Hi.

 Progress. Progress. :) I'm push my changes on my github account soon, but 
 here's the caveat when using lldb on Mac. When debugging binaries build with 
 llvm-gcc almost all the lldb python stl formatter and helper are broken. And 
 even if someone would take it on to write some new formatters it would be 
 hard for the debugger to distinguish which compiler actually build the binary.

I think you should report about missing formatters to LLVM bugzilla. Maybe 
Apple is also interested in maintaing backward compatibility of debugger.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Why we need .81 on the version number?

[Konstantin Tokarev]

25.08.2012, 09:40, Loaden loa...@gmail.com:
 QTCREATOR_VERSION =2.5.81
 What does the mean about .81? and always .81? never changed.

It's incremented after initial beta release, while Qt Creator is finally 
approaching
2.(N+1).0

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Open Source debugger ZeroBUGS

[Konstantin Tokarev]

23.08.2012, 22:36, Peter Kümmel syntheti...@gmx.net:
 On 23.08.2012 20:05, André Pönitz wrote:

  On Thu, Aug 23, 2012 at 01:16:25PM +0200, Peter Kümmel wrote:
  While reading the LLDB thread I had the idea to
  mention here that ZeroBUGS was open sourced last year:
    http://www.zerobugs.org/

  It's a one-man-show, so the code base couldn't be gigantic.
  History of this project could be read in the blog post.
 ZeroBUGS is a visual debugger for Linux, a project that
  ate up all of my spare time between 2004 and 2008.

  Four or five years of all spare time can be quite a bit.
  And the result is something that supposedly runs on Linux
  (which I couldn't verify, since my distro doesn't ship
  the packages it depends on...)

 Yes, seems development is stalled.

  It's interesting to see that you don't need hundreds
  of mean-years to write a debugger from scratch.
  Nobody mentioned hundred man-years. But having something
  usable, cross-platform takes a while.

 I only had gdb and LLVM in mind: gdb is several decades old
 and LLDB is developed by Apple.

pathdb [1] also.

[1] https://github.com/path64/debugger

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] How about the future of qbs after Nokia sells Qt to Digia?

[Konstantin Tokarev]

11.08.2012, 10:56, Loaden loa...@gmail.com:
 I noticed Nokia stop developing qbs for a long time, and qtcreator's wip/qbs 
 seems stop developing too.
 And for now Nokia sells Qt to Digia, I want know how about the future of qbs?
 If the Digia give up qbs, I will choice CMake as my build system.
 So, any news or commens are very welcome!

You can try to use Premake [1, 2]. It's under active development, and I'm 
working on plugin for Qt Creator [3]. I hope I'll be able to get it into 
upstream at some point.

[1] http://industriousone.com/premake
[2] 
http://industriousone.com/topic/full-stack-qt-based-development-premake-available-download
[3] http://qt-project.org/wiki/PremakeProjectManager

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QtCreator build system is broken after OSX upgrade.

[Konstantin Tokarev]

 Hi
 
 I just noticed this and posted a question on SO; to prevent re-writting the 
 whole thing I just put the link directly here:
 
 http://stackoverflow.com/questions/11764216/qtcreator-build-system-is-broken-after-osx-upgrade
 
 I also noticed, as pointed in the answer, that using the Clang toolchain 
 fixes the issue. The only difference I can see when invoking the toolchain is 
 the -spec option passed to the quake:
 
 qmake /Users/mirzadeh/codes/Projects/FVM/FVM.pro -r -spec 
 unsupported/macx-clang CONFIG+=x86_64 CONFIG+=declarative_debug (this works)
 
 rather than:
 
 qmake /Users/mirzadeh/codes/Projects/FVM/FVM.pro -r -spec macx-llvm 
 CONFIG+=x86_64 CONFIG+=declarative_debug (this does *NOT* work)
 
 I did not have this issue on OSX lion and before upgrading to OSX mountain 
 lion. Any idea what broke it?


Maybe llvm-gcc is missing in Mountain Lion?

 -- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator