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

[Peter Kümmel]

Am 15.01.2016 um 15:46 schrieb Hunger Tobias:

In essence Qt Creator will be GPL (with exception) from here on out. This
effects the master branch of the Qt Creator repository. The stable branches are
not going to get updated to the new licensing scheme.


Strange; change from LGPL to GPL without any discussions.

Is this again the idea, "if we don't GPL our code someone else earns MY 
money" misbelief?





Please take a bit of time and check whether the patches change the copyright in
unintended ways, especially if you have contributed code to Qt Creator. I think
I managed to keep all information in the headers intact, but please help to make
sure. Checking and double-checking all this information is tedious work and I
might have done some unintended changes.

Please also check your license template: Please use the one we ship with Qt
Creator in dist/copyright_template.txt (after adapting the copyright information
of course)! This file is already updated in git (master branch).

The first patch of the set is here:
https://codereview.qt-project.org/#/c/146218/

Please help reviewing the patches!


The commercial plugins that are effected by the agreement are currently getting
a similar license update and will get merged into the master branch once that is
complete.

Best Regards,
Tobias


___
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!

[Peter Kümmel]

Am 16.01.2016 um 14:30 schrieb 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.


I hope nothing useful will be abandoned because of the change.



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.




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.


I assume you talk about http://www.pathscale.com/DogFood
And nothing was contributed back, very sad.



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.


___
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!

[Peter Kümmel]

Am 16.01.2016 um 14:36 schrieb Konstantin Tokarev:



16.01.2016, 13:45, "Peter Kümmel" <syntheti...@gmx.net>:

Am 15.01.2016 um 15:46 schrieb Hunger Tobias:

  In essence Qt Creator will be GPL (with exception) from here on out. This
  effects the master branch of the Qt Creator repository. The stable branches 
are
  not going to get updated to the new licensing scheme.


Strange; change from LGPL to GPL without any discussions.


Peter,

If you read contributor agreement carefully, in 3.1 you grant non-exlusive rights to the 
code you've contributed to The Qt Company "under license terms of The Qt Company's 
choosing including any Open Source Software license".


Thanks for the reminder: I forgot I already sold my soul ;)





Is this again the idea, "if we don't GPL our code someone else earns MY
money" misbelief?


  Please take a bit of time and check whether the patches change the copyright 
in
  unintended ways, especially if you have contributed code to Qt Creator. I 
think
  I managed to keep all information in the headers intact, but please help to 
make
  sure. Checking and double-checking all this information is tedious work and I
  might have done some unintended changes.

  Please also check your license template: Please use the one we ship with Qt
  Creator in dist/copyright_template.txt (after adapting the copyright 
information
  of course)! This file is already updated in git (master branch).

  The first patch of the set is here:
  https://codereview.qt-project.org/#/c/146218/

  Please help reviewing the patches!

  The commercial plugins that are effected by the agreement are currently 
getting
  a similar license update and will get merged into the master branch once that 
is
  complete.

  Best Regards,
  Tobias


___
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

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

[Peter Kümmel]

Am 16.01.2016 um 13:21 schrieb 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.


I agree, if all is GPL integrating stuff is much simpler.



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, 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

Re: [Qt-creator] Focus after build

[Peter Kümmel]

Am 11.03.2015 um 15:43 schrieb Ziller Eike:

 On Mar 11, 2015, at 3:32 PM, Peter Kümmel syntheti...@gmx.net wrote:

 On Linux after every build QtCreator gets the focus, even
 when it is minimised after starting the build. Is there a
 way to disable this (there is no option in Build and Run)
 If not, where is this triggered in the code, I would like
 to make this optional.

 I suppose this should just not happen?
 I would guess that either the  QApplication::alert call in 
 BuildManager::finish, or the  ICore::raiseWindow call in  
 OutputPaneManager::showPage could be responsible for this.

QApplication::alert triggers the popup.
So is it a bug (feature) of the window manager (Cinnamon) or 
one in Qt5?


 Br, Eike

 Peter
 ___
 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

[Qt-creator] Focus after build

[Peter Kümmel]

On Linux after every build QtCreator gets the focus, even 
when it is minimised after starting the build. Is there a 
way to disable this (there is no option in Build and Run)
If not, where is this triggered in the code, I would like
to make this optional.

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

Re: [Qt-creator] Using C++11 in Creator's source

[Peter Kümmel]

On 07.03.2014 11:54, Daniel Teske wrote:
 On Friday 07 Mar 2014 11:42:30 Tobias Hunger wrote:
 On 04.03.2014 14:09, Daniel Teske wrote:
 Hi,

 since we have branched 3.1 from master, master no longer needs to support
 OS X 10.6. As such I propose, that we open up master for those C++11
 features that are supported by VS 2010, g++ 4.5 and clang 3.1.
 That is the list that is used for Qt 5, but why can't we go for
 something a bit newer?
 Because it makes no difference in which parts of C++11 we can use. VS 2010
 limits what we can use, g++ 4.5 and clang 3.1 are simply the first versions
 that more or less support a superset of VS 2010's support.

So, why is it necessary to support VC 2010?
MSVC is the most foreign compiler in QtCreator-land,
and it should not be the limiting factor.

Peter


 As I wrote in my initial mail, in practice I would expect no one to use those
 compilers any more.

 I am no Windows user, maybe we can just bump the requirement to MSVC
 2012 there? That would be a huge step forward for our C++11 support!
 No, I think it's too early for that.

 daniel
 ___
 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

Re: [Qt-creator] Qt Creator 3.1 release schedule

[Peter Kümmel]

On 10.01.2014 12:36, Poenitz Andre wrote:

 This is will be the first release containing the previous wip/clang
 branch as experimental plugin. It's already integrated into the master
 branch, but building currently still takes some manual effort, see
 https://qt.gitorious.org/qt-creator/qt-creator/commit/83bfaa630b38801feba1fb42e24cd3800133

A simplified way to build Clang could be found here

https://github.com/syntheticpp/Der-Clang

It's a meta-repository which hosts the necessary
repositories as submodules.

To get the code, clone it and run ./update (works
on Linux and Windows with a bash).

BTW, the fastest way to build on Windows is to use cmake with ninja.

Peter

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

[Qt-creator] Qbs build without QtWebKit

[Peter Kümmel]

Is it possible to build Qt Creator with Qbs but without having QtWebKit build?
It makes no problem when using qmake.

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

[Qt-creator] Slow cdb

[Peter Kümmel]

Wasn't there a wiki entry about dead slow cdb or cdb in general?

I think there was something related to the warning
 WARNING: Unable to verify checksum for ...
but I couldn't find it any more.

What was the reason for this warning, is this warning related to the slowdown?
How could I fix the bad cdb speed on my installation side?

(I use cdb to debug gdb support atm)

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

Re: [Qt-creator] Slow cdb

[Peter Kümmel]

On 04.06.2013 10:27, David Schulz wrote:
 Hi Peter,

 the warning could result from using the Microsoft Symbol Server.
 The problem is that the cdb tries to get all your symbols from this server.
 What results in some overhead for all the symbols which are not
 available. For Example the whole Qt and QtCreator libraries.

 If you have a Creator checkout from the 2.8 branch you schould be able
 to add a symbol cache to the symbol paths for the cdb in the options
 under Debugger - CDBPaths - Symbol Paths - Insert... - Symbol Cache...
 It is important that you insert the cache before the symbol server
 otherwise the symbols wouldn't get cached and read before the server is
 contacted.

 If you are using an older QtCreator add the symbolcache manually. The
 setting can be found under Options - Debugger - CDB - Paths - Symbol
 Paths - Edit... in versions  2.8.

 For Example:
 cache*C:\dev\symbolcache

 srv*http://msdl.microsoft.com/download/symbols


 You should also remove the folder from the path with srv*. Otherwise The
 symbols from the server would be cached in two places.

 BR David

Great! Seems this solves the issue.

But I couldn't test with Creator and qbs, because 2.8/qbs build is broken:

 ..\diffeditoreditable.cpp': No such file or directory

Peter




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

Re: [Qt-creator] Qt Creator 2.7 onward does not work with some gdb on Windows

[Peter Kümmel]

rubenvb mingw-w64 build reports a GDB version string with the GCC version in 
parentheses:
   GNU gdb (rubenvb-4.7.2-release) 7.5.50.20120920-cvs

I pushed a merge request.

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

[Qt-creator] Refactoring function declarations

[Peter Kümmel]

Refactoring function declarations is a great feature!
But is there a way to disable the C-ish */ placement?

For instance when I change a function from QString s to QString s
in the header it becomes QString s

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

Re: [Qt-creator] code style option: pointer, reference

[Peter Kümmel]

On 06.12.2012 15:45, Markus Rathgeb wrote:
 Hello!

 Would it be possible to add an option to the code style settings to decide
 on which position the whitespace and the pointer / reference sign should be
 located on auto completion.

 For example:
 I added a definition of a member function function to a class in the the
 header file e.g.
 class ClassX
 {
  void fooA(const ObjectA a, ObjectB* b);
  void fooB(const ObjectA a, ObjectB *b);
 }

 No I open the cxx (cpp or whatever naming scheme is used) file of the class
 and would like to implement the functions.
 I write
 void ClassX::fooA(
 the auto completion suggests me the write signature, I press return to
 apply it and I get:
 void ClassX::fooA(const ObjectA a, ObjectB *b);
 Same for fooB(..).

 It would be nice, if there would be an option where I can state if I want
 to use:
 - Object obj OR Object obj
 - Object* obj IR Object *obj

 There is no correct or wrong, this is simply a styling stuff.

 Could someone add this feature?
 It would be great!

 Best regards and thanks for the top IDE,
 Markus


Seems you had the same idea. I didn't read your post before I send mine ;)



 ___
 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

Re: [Qt-creator] Toolchain detection Windows SDK amd64

[Peter Kümmel]

On 20.11.2012 00:21, Wolfgang Baron wrote:
 Hi,

 Peter Kümmel wrote:
 /amd64 and /x86 are the same, have a look at vcvarsall.bat:

 if /i %1 == amd64 goto amd64
 if /i %1 == x64   goto amd64

 I assume your real problem is different.

 No. The fix would not work then, right? In your answer, you are
 referring to vcvarsall.bat, which is used for the compiler called
 Microsoft Visual C++ Compiler 10.0 (amd64). I am talking about the
 Windows SDK version called Microsoft Windows SDK for Windows 7
 (7.1.7600.0.30514) (amd64), as quoted in my fixed entry for toolchains.xml:

valuemap type=QVariantMap
 value type=QString
 key=ProjectExplorer.MsvcToolChain.SupportedAbix86-windows-msvc2010-pe-64bit/value
 value type=QString
 key=ProjectExplorer.MsvcToolChain.VarsBatC:/Program Files/Microsoft
 SDKs/Windows/v7.1/bin/SetEnv.cmd/value
 value type=QString
 key=ProjectExplorer.MsvcToolChain.VarsBatArg/x64/value
 value type=bool
 key=ProjectExplorer.ToolChain.Autodetectfalse/value
 value type=QString
 key=ProjectExplorer.ToolChain.DisplayNameWindows SDK 7.1 x64/value
 value type=QString
 key=ProjectExplorer.ToolChain.IdProjectExplorer.ToolChain.Msvc:{7afba206-0e0e-4e07-a623-2932c01e21f4}/value
/valuemap

 The Windows SDK version of the compiler uses setenv.cmd, which only
 knows about x64, not amd64.


Does your compiler dialog also list Microsoft Visual C++ Compiler 10.0 (amd64)?
Then you could use this compiler (or x86_amd64 when you are on a 32bit Windows).
setenv.cmd only maps to these compilers.
Maybe the Windows SDK entries for the compilers are superfluously. Could you 
check
how many cl.exe versions are on your system?



 I proposed a workaround for a bug in the autodetection. I browsed a
 little in the buglists, but did not find an exact match. Before I open a
 new Bug, I wanted to know, whether this applies to a bug, which has
 already been published. Anyone?

If you can't find a existing report file a new one. There will be some cleanup 
in 2.7.

I've fixed the autodetection code, could you check if this version works:
https://github.com/syntheticpp/qt-creator/downloads

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

Re: [Qt-creator] Toolchain detection Windows SDK amd64

[Peter Kümmel]

On 18.11.2012 01:44, Wolfgang Baron wrote:
 Hi,

 I just worked around a bug in Qt Creator 2.6.0 concerning jom or nmake
 not finding the compiler for the Windows SDK 7.1 amd64. This happens,
 when you want to generate code for amd64 using the autodetected toolchains.

 The underlying problem is, that the autodetections uses /amd64 for
 initializing the MSVC compiler environment. This should be /x64 instead.

/amd64 and /x86 are the same, have a look at vcvarsall.bat:

if /i %1 == amd64 goto amd64
if /i %1 == x64   goto amd64

I assume your real problem is different.


 I have not found a way to change this in Qt Creator, so I use a text
 editor to edit the file
 .../AppData/Roaming/QtProject/qtcreator/toolchains.xml. Changing the
 autodetected entry did not help me, as it was overwritten the next time
 I started Qt Creator. So you have to clone the entry for amd64 Windows
 SDK 7, quit Qt Creator, edit the new entry and start Qt Creator again.
 Then you can use your new entry for setting up kits.

 I have not found a bug report for this, but maybe I missed it. Has
 anybody seen a bugreport or should I post one?

 My working toolchain entry is:

 data
variableToolChain.11/variable
valuemap type=QVariantMap
 value type=QString
 key=ProjectExplorer.MsvcToolChain.SupportedAbix86-windows-msvc2010-pe-64bit/value
 value type=QString
 key=ProjectExplorer.MsvcToolChain.VarsBatC:/Program Files/Microsoft
 SDKs/Windows/v7.1/bin/SetEnv.cmd/value
 value type=QString
 key=ProjectExplorer.MsvcToolChain.VarsBatArg/x64/value
 value type=bool
 key=ProjectExplorer.ToolChain.Autodetectfalse/value
 value type=QString
 key=ProjectExplorer.ToolChain.DisplayNameWindows SDK 7.1 x64/value
 value type=QString
 key=ProjectExplorer.ToolChain.IdProjectExplorer.ToolChain.Msvc:{7afba206-0e0e-4e07-a623-2932c01e21f4}/value
/valuemap
   /data

 Cheers,

 Wolfgang

 ___
 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

[Qt-creator] Real shadow builds with CMake and Qt Creator 2.6

[Peter Kümmel]

Currently Qt Creator pollutes the source directory with a CMakeLists.txt.user
file even when building out-of-source (shadow).

A patch and Windows binary which adds a option in the CMake wizard dialog
to also save the .user file in the build directory could be found here:

https://github.com/syntheticpp/qt-creator
 (branch 2.6-cmake-shadow-user-file, based on the 2.6 branch)
https://github.com/syntheticpp/qt-creator/downloads

A procject name.qtcreator file will be created in the build directory
which should be opened instead of the original CMakeLists.txt file.

After associating .qtcreator with qtcreator.exe also opening the
project with a double click is possible.
When on Windows the association doesn't work removing the registry key
[HKEY_CURRENT_USER\Software\Classes\Applications\qtcreator.exe
and selecting the Qt Creator exe again helps.

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

Re: [Qt-creator] Add arbitrary file to cmake project

[Peter Kümmel]

On 20.10.2012 15:51, Uwe Fechner wrote:
 Hello,

 I have a cmake project that builds a library.

 I would like to add:
 1. a bash script file, that loads and executes the library
 2. a readme.txt file

 to the project in such a way that I can easily edit these
 files from within qt creator.

 Is there a way to add these files to the CMakeLists.txt file so that
 they are displayed by qt creator in the cmake project?

 Best regards:

 Uwe Fechner

Was discussed here:
http://lists.qt-project.org/pipermail/qt-creator/2012-August/001191.html

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

Re: [Qt-creator] Qt Creator 2.6 RC status and schedule

[Peter Kümmel]

On 10.10.2012 09:50, Ziller Eike wrote:
 Hello,

 the status of Qt Creator 2.6 looks almost good now, with a few installer 
 issues remaining (fixes in the works), and one and a half issues with the C++ 
 code model open (and in the works).

 So it looks like we'll be ready for RC release coming tuesday, 16.10.2012.
 If you find issues with the current RC builds (on 
 builds.qt-project.org/view/Qt%20Creator), please create bug reports on 
 bugreports.qt-project.org, and for serious ones please mark as P1 and/or 
 inform me and the corresponding maintainer (best simply through this list).

https://bugreports.qt-project.org/browse/QTCREATORBUG-8001


 Br, Eike

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

Re: [Qt-creator] Qt5 + CMake: qdeclarativefolderlistmodel.h(56): Error: Undefined interface

[Peter Kümmel]

On 26.09.2012 11:00, Loaden wrote:
 Patch in here: https://codereview.qt-project.org/#change,35697

...
 *moc_qdeclarativefolderlistmodel.cxx_parameters*

 -DUNICODE
 -D_CRT_SECURE_NO_WARNINGS
 -DQT_NO_CAST_TO_ASCII
 -DQT_DISABLE_DEPRECATED_BEFORE=0x040900
 -DQT_USE_FAST_OPERATOR_PLUS
 -DQT_USE_FAST_CONCATENATION
 -DWIN32
 -o


Have a look at the qmake generated Makefiles:
D:\qt4\_4.8.3_elf64\bin\moc.exe $(DEFINES) $(INCPATH) -D_MSC_VER=1700 -DWIN32 
e:\sandbox\creator\qt-creator\src\libs\qtcomponents\styleitem\qdeclarativefolderlistmodel.h
 -o 
tmp\moc_qdeclarativefolderlistmodel.cpp

DEFINES = -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DWITH_TESTS 
-DIDE_LIBRARY_BASENAME=\lib\ -DQT_NO_CAST_TO_ASCII 
-DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION 
-D_CRT_SECURE_NO_WARNINGS -DQT_DLL -DQT_PLUGIN 
-DQT_DECLARATIVE_LIB -DQT_TESTLIB_LIB -DQT_SCRIPT_LIB -DQT_GUI_LIB 
-DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW 
-DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT 
-DQT_DECLARATIVE_DEBUG


I could imagine -DQT_PLUGIN is important here.

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

Re: [Qt-creator] Branch 2.6: Can't catch the moc errors

[Peter Kümmel]

On 26.09.2012 15:27, Tobias Hunger wrote:
 On 26.09.2012 14:52, Loaden wrote:
 D:/qpSOFT/Projects/QtCreator/src/libs/qtcomponents/styleitem/qdeclarativefolderlistmodel.h(56):
 Error: Undefined interface
 For now QTC can't catch this error from moc.
 I can't double-click to jump to the file and the line.
 So, there should been some regex issue.
 Hello Loaden!

 Ah, now I get what you want! Why don't you file a bug report about stuff
 like that? Takes as long as writing a mail and actually gets something
 done:-)

 You are using ninja, aren't you? IIRC that redirect stdout to stderr,
 which does break the extraction of build issues in general.

 Best Regards,
 Tobias



It's not a redirecting problem, also the ninja build passes the line to

bool MsvcParser::processCompileLine(const QString line)
{
 sendQueuedTask();

 if (m_compileRegExp.indexIn(line)  -1) {


But the regex doesn't match. In a qmake based build the line looks like this:

..\..\..\..\qt-creator\src\plugins\cmakeprojectmanager\cmakeeditor.h(55): 
Error: Undefined interface

The ninja build prints an absolute path with slashes:

E:/sandbox/creator/loaden/src/libs/utils/iwelcomepage.h(54): Error: Undefined 
interface


https://bugreports.qt-project.org/browse/QTCREATORBUG-7932

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

Re: [Qt-creator] Branch 2.6: Can't catch the moc errors

[Peter Kümmel]

On 26.09.2012 17:57, Tobias Hunger wrote:
 On 26.09.2012 17:13, Peter Kümmel wrote:
 It's not a redirecting problem, also the ninja build passes the line to

 bool MsvcParser::processCompileLine(const QString line)
 {
sendQueuedTask();

if (m_compileRegExp.indexIn(line)  -1) {


 But the regex doesn't match. In a qmake based build the line looks like this:

 Actually that should match MSVC errors and not errors from moc... that
 is for the Qt parser to do. And it does: I just added a unit test with
 your output.

 Is that parser in the parser chain? I think CMake's makestep does not
 add it. Please feel free to test
   https://codereview.qt-project.org/35774

Great, this fixes the issue, Thanks!


 If I get enough reports that it works in all the types of projects
 touched, then I might be able to convince Eike to include it in 2.6
 (otherwise this is for master).

 Best Regards,
 Tobias

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

Re: [Qt-creator] Does any one interesting to help writting CMake Scripts for QtCreator?

[Peter Kümmel]

On 12.09.2012 12:39, Loaden wrote:
 ok, I will continue do it for myself.
 because cmake is great.

Please post a link of your fork.

Having cmake files makes it possible to build with ninja.
I'm looking forward to compare with qbs.

BTW if you maintain a shadow build system globbing for
files makes live easier (when the project is not full of
unused files)

Peter



 2012/9/12 eike.zil...@nokia.com


 On 11 Sep 2012, at 16:33, ext Loaden loa...@gmail.com wrote:

 For now QtCreator support qmake + qbs build system, but I think if there
 exist CMake build system, that's would be great.

 No, I think it wouldn't. What advantage would that have to add
 YetAnotherBuildSystem™ ?

 With all adding of the hassle of doing all the right resource copying,
 making it work on the different platforms etc (think e.g. Mac OS)?
 Already the additional qbs is a pain to keep in sync, and it's still not
 set up to actually do the right things.
 I really don't want bugreports from people complaining that something
 doesn't work, just to find out that they were using cmake to build Qt
 Creator and that missed to do something (like copying a resource).

 After several day work, I can build QtCreator's library using CMake
 scripts now.
 It's supported share Precompiled Header for both of MSVC / GCC, and for
 CLang there does not support yet (But it should work like gcc, just need
 some TODOs).
 So, does any one can help me to finished it?
 or review the code from here:
 https://codereview.qt-project.org/#change,34052
 I am newbie on CMake.
 I am really really need your helps / tips / points.
 Thanks!

 -- Forwarded message --
 From: Loaden loa...@gmail.com
 Date: 2012/9/11
 Subject: Does any one interesting to help writting CMake Scripts for
 QtCreator?
 To: cmake cm...@cmake.org, development developm...@qt-project.org,
 inter...@qt-project.org


 For now QtCreator support qmake + qbs build system, but I think if there
 exist CMake build system, that's would be great.
 After several day work, I can build QtCreator's library using CMake
 scripts now.
 It's supported share Precompiled Header for both of MSVC / GCC, and for
 CLang there does not support yet (But it should work like gcc, just need
 some TODOs).
 So, does any one can help me to finished it?
 or review the code from here:
 https://codereview.qt-project.org/#change,34052
 I am newbie on CMake.
 I am really really need your helps / tips / points.
 Thanks!



 --
 Best Regards
 Yuchen

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

 --
 Eike Ziller
 Principal Software Engineer

 Nokia, Qt Development Frameworks

 Nokia gate5 GmbH
 Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
 Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
 Umsatzsteueridentifikationsnummer: DE 812 845 193
 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori






 ___
 Qt-creator mailing list
 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

[Qt-creator] 2.6 frozen?

[Peter Kümmel]

Is 2.6 open for a new small feature?

Peter
___
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?

[Peter Kümmel]

On 06.09.2012 07:59, joerg.bornem...@nokia.com wrote:
 Diego,
 my recommendation for a free (as in beer) C++ toolchain on Windows is:

 - the Windows SDK, if you don't need an IDE or use Qt Creator. It comes with 
 everything you need to do C++ development: MSVC, Windows headers/libs, 
 documentation.

Are there differences to the compiler shipped with MSVC Express?

 - MSVC Express, if you need an IDE. This is the Windows SDK + a reduced but 
 very usable version of Visual Studio.

if you need an IDE  shouldn't you recommend QtCreator on this list ;)

 - MinGW if you need C++ features that MSVC doesn't support or you're porting 
 unixoid software to Windows.

 Coda,
 thanks for the interesting links! I know that gcc contains a great C++ 
 compiler. Its the quality of the whole package I'm bitching at.


 Cheers,

 Jörg
 ___
 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

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

[Peter Kümmel]

On 05.09.2012 12:34, Peter Kümmel wrote:
 I wonder how you build on Windows, or even care about MS's compiler:

 - jom breaks, bad path name:
 Error: dependent
 '..\..\..\lib\qtcreator\plugins\Nokia\e:\sandbox\creator\qt-creator\src\plugins\coreplugin\Core.pluginspec'
  does not exist.

 - nmake breaks: Makefile.Release(563) : fatal error U1033: Syntaxfehler: : 
 unerwartet

 - Studio -tp vc: didn't start because it can't find plugins


 2.5, Qt 4.8, msvc10, cmd.exe, shadow dir on different drive and on 
 checkout-dir level

I'm using qt/4.8 maybe that's the problem.


 Peter
 ___
 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

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

[Peter Kümmel]

On 05.09.2012 12:42, Joerg Bornemann wrote:
 On 05/09/2012 12:34, ext Peter Kümmel wrote:

 I wonder how you build on Windows, or even care about MS's compiler:

 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.


 - jom breaks, bad path name:
 Error: dependent
 '..\..\..\lib\qtcreator\plugins\Nokia\e:\sandbox\creator\qt-creator\src\plugins\coreplugin\Core.pluginspec'
  does not exist.

 Yeah this looks wrong. Note the e: in the middle of the path.
 You're not trying to build Qt Creator with MSVC using a MinGW Qt, do you?

It builds and links a lot before it breaks.



 Cheers,

 Jörg


___
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?

[Peter Kümmel]

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?

Peter
___
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?

[Peter Kümmel]

On 05.09.2012 14:04, eike.zil...@nokia.com wrote:

 On 5 Sep 2012, at 12:34, ext Peter Kümmel syntheti...@gmx.net wrote:

 I wonder how you build on Windows, or even care about MS's compiler:

 - jom breaks, bad path name:
 Error: dependent
 '..\..\..\lib\qtcreator\plugins\Nokia\e:\sandbox\creator\qt-creator\src\plugins\coreplugin\Core.pluginspec'
  does not exist.

 - nmake breaks: Makefile.Release(563) : fatal error U1033: Syntaxfehler: : 
 unerwartet

 - Studio -tp vc: didn't start because it can't find plugins


 2.5, Qt 4.8, msvc10, cmd.exe,


 shadow dir on different drive

 This is known to not be well supported (by qmake?) and may lead to funny 
 errors, if I remember correctly.

Once I reported a bug because the build directory was on the same level as 
sources.

Qt/QtCreator needs much more build bots, like CMake:
http://open.cdash.org/index.php?project=CMake
not only a hand full.


 and on checkout-dir level

 Peter
 ___
 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

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

[Peter Kümmel]

On 05.09.2012 14:47, eike.zil...@nokia.com wrote:

 On 5 Sep 2012, at 14:19, ext Peter Kümmel syntheti...@gmx.net wrote:

 On 05.09.2012 14:04, eike.zil...@nokia.com wrote:

 On 5 Sep 2012, at 12:34, ext Peter Kümmel syntheti...@gmx.net wrote:

 I wonder how you build on Windows, or even care about MS's compiler:

 - jom breaks, bad path name:
 Error: dependent
 '..\..\..\lib\qtcreator\plugins\Nokia\e:\sandbox\creator\qt-creator\src\plugins\coreplugin\Core.pluginspec'
  does not exist.

 - nmake breaks: Makefile.Release(563) : fatal error U1033: Syntaxfehler: 
 : unerwartet

 - Studio -tp vc: didn't start because it can't find plugins


 2.5, Qt 4.8, msvc10, cmd.exe,


 shadow dir on different drive

 This is known to not be well supported (by qmake?) and may lead to funny 
 errors, if I remember correctly.

 Once I reported a bug because the build directory was on the same level as 
 sources.

 Qt/QtCreator needs much more build bots, like CMake:
  http://open.cdash.org/index.php?project=CMake
 not only a hand full.

 builds.qt-project.org builds Qt Creator with Qt 4.8.2 and Visual Studio 2010, 
 so I don't see where your conclusion comes from.

No build with:
- nmake
- qmake -tp vc
- mingw
- clang
- intel
- latest 4.8 version
- Qt5
- different shadow folders
- qbs
- rebuilds after clean

and that's only on Windows.


 But of course you are invited to donate additional hardware to the Qt Project.

 and on checkout-dir level

 Peter
 ___
 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

___
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?

[Peter Kümmel]

On 05.09.2012 14:56, Joerg Bornemann wrote:
 On 05/09/2012 14:16, ext Peter Kümmel wrote:

 cd .\creator-build
 qmake -r ..\creator
 jom (or maybe jom release)

 Same here, but with a fresh qt/4.8 build

 Is your Qt Creator source tree clean?
 Try a git clean -dxf there.
 Qmake gets confused if you've build artifacts in there.

Yes, all is clean.

$ git status
# On master
nothing to commit (working directory clean)


But I found a way:

$ rm .gitignore
$ git clean -df

Seems .gitignore allows files which break the build,
git clean removed some .pluginspec files.

Peter

___
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?

[Peter Kümmel]

On 05.09.2012 15:30, Daniel Teske wrote:

 Try a git clean -dxf there.
 Yes, all is clean.
 Amazing, instead of actually trying the suggestion, you did what?


Ah, I didn't know the x option, and overread it and only used -df

 $ git status
 # On master
 nothing to commit (working directory clean)


 But I found a way:

 $ rm .gitignore
 $ git clean -df

 Seems .gitignore allows files which break the build,
 git clean removed some .pluginspec files.
 ___
 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

[Qt-creator] Open Source debugger ZeroBUGS

[Peter Kümmel]

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.

A git-svn checkout could be found at github:
 https://github.com/syntheticpp/zerobugs
License is Boost 1.0.

It's interesting to see that you don't need hundreds
of mean-years to write a debugger from scratch.

Peter



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

Re: [Qt-creator] Add OTHER_FILE function to CMake project

[Peter Kümmel]

On 22.08.2012 10:58, Stefano Cordibella wrote:
 I try to use add_library:
 ADD_LIBRARY(Other
   README Changelog
 )
 and the files appears in the Project tab, great!
 But when I run CMake I get this error:

 CMake Error: CMake can not determine linker language for target:Other

 CMake Error: Cannot determine link language for target Other.

 I try to add EXCLUDE_FROM_ALL flag in the add_library, but nothing change...

 Searching on google i found this other trick:
 SET(OTHER
   README
   Changelog)
 ADD_CUSTOM_TARGET(UtilityHeaders OTHER ${OTHER})
 This one don't generate error from CMake but the files are not displayed
 in project tab...

 Any other ideas?


Add the files to a real target and mark the files as headers:


macro(add_info_files)
 foreach(_it ${ARGN})
 if(NOT IS_DIRECTORY ${_it})
 get_filename_component(name ${_it} NAME)
 if(NOT ${_it} MATCHES ^/..*$;~$)
 set_source_files_properties(${_it} PROPERTIES HEADER_FILE_ONLY 
TRUE)
 endif()
 endif()
 endforeach()
endmacro()


set(info README Changelog)
add_info_files(${info})
add_library(foo ${real_source_files} ${info})


Peter

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

Re: [Qt-creator] Target refactoring

[Peter Kümmel]

On 22.04.2012 10:20, tobias.hun...@nokia.com wrote:
 Hi Peter!

 Great to see somebody working in that area:-)

 I am not sure having a build system is a necassary though since the 
 Project already
 needs to know a lot about of details about the build system used. It needs to 
 parse
 all the information we need to know out of the build system setup that 
 defines the project
 after all. On the other hand you can argue that the project needs to 
 understand the
 _configuration system_ used to decide which files belong to the project, 
 which defines are
 used, etc. and not the low level _build system_ that actually decides which
 compiler/linker/moc/whatever calls are required to get the binaries you 
 desire.

 So what do you want to archive with a new build system abstraction?

I wanted to add support for ninja, the 'make' replacement.
CMake now can generate ninja build files.

First I did it like it is done for jom, but this way looks like a hack,
so I tried to find a cleaner solution. As mentioned in the previous mail
the idea is to split out the code which defines the build command.

I also had a look at the qbs branch because supporting qbs and make
is similar support make/ninja but I only saw the same intermixing
of buildsystem/toolchain/makestep/project.

When the Project needs details about the build system we could add
an interface from which all the information could be get, it's better
than to hardcode all the details in several classes.

Maybe my proposal doesn't fit into the current design but maybe we
could find a solution which makes it strait forward to add a new
build system.

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

Re: [Qt-creator] Target refactoring

[Peter Kümmel]

On 20.04.2012 15:31, tobias.hun...@nokia.com wrote:
 Hello!

 I wanted to take the time to explain what I am currently working on for 
 post-2.5
 (targeting 2.6), hoping for some feedback...

 Note that all I describe here is work-in-progress(TM)!

 I am currently working on changing the target we have in Qt Creator. Since
 Targets were introduced they are used to group sets of build- and run
 configurations based on the platform a developer is targeting. I am currently
 changing this to have each Target in a project refer to one specific
 device/system configuration instead.

 To do so I am adding a Profile, which is basically a collection of settings
 describing one Target. The list of settings can be extended by plugins
 (via ProfileInformation objects). This Profile currently contains:
   * some data like a name, icon, etc.
   * a system root (from ProjectExplorer plugin)
   * a tool chain (from ProjectExplorer plugin)

I'm not sure if this fits into your redesign, but I've started [1] splitting up
tool chain into tool chain and build system because using
make/ninja/nmake/jom/scons/... is not completely defined by a specific tool 
chain.

Peter

[1] 
https://qt.gitorious.org/qt-creator/syntheticpps-qt-creator/commit/74bb7730e0aab589db46cb6cf7c7d844500ef616/diffs/8083513305034cfe6cc8a651d7790789cbe947f2
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator