Hello Tobias, Hello Orgad,
with your help, I was finally able to nail down the crash on my machine. Here’s
what is going wrong:
I have a crash in baseqtversion.cpp:1483 because this is 0x0.
See where this is called: QmakeBuildConfigurationFactory::createBuildInfo:
qmakebuildconfiguration.cpp:654
info->supportsShadowBuild = (version && version->supportsShadowBuilds()); //
Here version if checked for 0x0
// check if this project is in the source directory:
Utils::FileName projectFilePath = Utils::FileName::fromString(projectPath);
if (version->isInSourceDirectory(projectFilePath)) { // Here not
Why does this happen on my machine and not on yours? I guess because I have a
bare metal kit installed that does not have a Qt version attached to it.
Best regards,
Axel Jäger
Von: Orgad Shaneh [mailto:[email protected]]
Gesendet: Mittwoch, 4. März 2015 09:21
An: Axel Jäger
Cc: Hunger Tobias; qt-creator
Betreff: Re: [Qt-creator] Crash QtCreator using a simple json-based wizard
On Wed, Mar 4, 2015 at 12:48 AM, Axel Jäger <[email protected]
<mailto:[email protected]> > wrote:
Hello Tobias,
so in the end, I found another bug and I am no closer fighting my bug that
QtCreator crashes using my simple wizard. My goal is still compiling a
QtCreator from source to hopefully reproduce the crash and be able to debug the
crash then. Unfortunately, I had no longer success in compiling QtC from git.
Here is what I tried:
My setup:
- Windows 8.1
- Visual Studio 2013 Ultimate
- MinGW 4.9.1-2
Did fresh clone of the QtC-Repository and noticed that QBS was missing so I did
a clone of the QBS repo in qt-creator/src/shared/qbs.
In both repositories, MASTER was checked out.
You should checkout 3.4 in qtcreator.
Also, instead of manually cloning qbs, delete all its content (leave an empty
directory), then execute git submodule update --init in qt-creator root.
Approach 1: Build <http://qtcreator.pro> qtcreator.pro using Visual Studio
Compiler in stable QtCreator:
Build fails: QtSupport.mimetypes.xml is missing
Approach 2: Build <http://qtcreator.pro> qtcreator.pro using Visual Studio
Command Line:
Build fails:
link /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /DLL /SUBSYSTEM:WINDOWS
/DEF:C:\Users\axeljaeger\qt-creator\src\libs\qtcreatorcdbext\qtcreatorcdbext.def
/MANIFEST:embed /OUT:..\..\..\lib\qtcreatorcdbext32\qtcreatorcdbext.dll
@C:\Users\AXELJA~1\AppData\Local\Temp\nmC60E.tmp
Bibliothek "..\..\..\lib\qtcreatorcdbext32\qtcreatorcdbext.lib" und Objekt
"..\..\..\lib\qtcreatorcdbext32\qtcreatorcdbext.exp" werden erstellt.
extensioncontext.obj : error LNK2019: Verweis auf nicht aufgelöstes externes
Symbol "DebugCreate" in Funktion ""public: bool __cdecl
IInterfacePointer<struct IDebugClient5>::create(void)"
(?create@?$IInterfacePointer@UIDebugClient5@@@@QEAA_NXZ)".
gdbmihelpers.obj : error LNK2001: Nicht aufgelöstes externes Symbol
"DebugCreate".
..\..\..\lib\qtcreatorcdbext32\qtcreatorcdbext.dll : fatal error LNK1120: 1
nicht aufgelöste Externe
(Which means more or less: Undefined reference to „DebugCreate“
Looks like incompatibility of the cdb lib. Do you have Debugging Tools
installed?
To workaround this, you can comment out the following line in libs.pro
<http://libs.pro>
exists($$CDB_PATH):SUBDIRS += qtcreatorcdbext
Approach 3: Build qtcreator.qbs using stable QtCreator:
Build fails: You need qbs 1.4, only 1.3 is installed.
Approach 4: Build <http://qtcreator.pro> qtcreator.pro using MinGW compiler in
QtCreator
C:\Users\axeljaeger\qt-creator\src\plugins\qbsprojectmanager\qbsbuildstep.cpp:189:
Fehler: 'const class qbs::BuildOptions' has no member named 'showCommandLines'
return m_qbsBuildOptions.showCommandLines();
^
Using git submodule update should solve this.
I am wondering why I get 3 different errors compiling the same sourcecode. Do
you have any tipps on how to get the creator to compile? Is it really
neccessary to checkout qbs to some place in the source tree? Are chances better
that compiling works out of the box when using 3.4 branch? Is there an easy way
to update my qbs to 1.4? Is building using qmake still recomended or shall I go
with qbs?
I’d prefer a solution compiling QtCreator from stable QtCreator and not from
the command line so I would already have a working debugging environment.
Best regards,
Axel
Von: Hunger Tobias [mailto: <mailto:[email protected]>
[email protected]]
Gesendet: Montag, 2. März 2015 16:21
An: Axel Jäger
Cc: qt-creator
Betreff: Re: [Qt-creator] Crash QtCreator using a simple json-based wizard
Hi Axel,
the 3.3 wizards should load again in the 3.4 branch without any error. Thanks
for catching this!
Best Regards,
Tobias
Tobias Hunger, Senior Software Engineer - Digia, Qt
Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin. USt-IdNr: DE 286 306 868
Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
_____
From:
<mailto:[email protected]>
[email protected] <
<mailto:[email protected]>
[email protected]> on behalf of
Tobias Hunger < <mailto:[email protected]> [email protected]>
Sent: Monday, March 2, 2015 08:12
To: Axel Jäger
Cc: Stenger Christian; qt-creator
Subject: Re: [Qt-creator] Crash QtCreator using a simple json-based wizard
On Mar 2, 2015 12:14 AM, "Axel Jäger" < <mailto:[email protected]>
[email protected]> wrote:
> It is interesting to see that my template was not valid in the first place
> but only machine complained about it, even with a crash.
The Projects page taking a parameter is a recent addition. Looks like I need to
check for backward compatibility to make sure not to break existing wizards
with the 3.4 version.
Best Regards,
Tobias
_______________________________________________
Qt-creator mailing list
[email protected] <mailto:[email protected]>
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator
