from:"Loaden"

Re: [Development] Qt 5.0.1 RC -- Release Testing

2013-01-27 Thread Loaden

https://qtproject.cachefly.net/digia/5.0.1_rc1/qt-windows-opensource-5.0.1-msvc2010_64-x86_64-offline-rc1.exe
I just download it from https://qtproject.cachefly.net/qt5/5.0.1-rc1/
Right now it is gone.


2013/1/28 Ahumada Sergio 

>  that file does not even exist ... where did you find it ?
>
>   --
> Sergio Ahumada
> Release Engineer - Digia, Qt
> --
> *From:* 
> development-bounces+sergio.ahumada=digia@qt-project.org[development-bounces+sergio.ahumada=
> digia@qt-project.org] on behalf of Loaden [loa...@gmail.com]
> *Sent:* Monday, January 28, 2013 01:14
> *To:* Motyka Rafal
> *Cc:* development@qt-project.org; releas...@qt-project.org
> *Subject:* Re: [Development] Qt 5.0.1 RC -- Release Testing
>
>  qt-windows-opensource-5.0.1-msvc2010_64-x86_64-offline-rc1.exe
> The ICU binary is x86 arch. It's wrong.
> Simply replace the icu49*.dll with 64bit version, then the crash solved.
>
> https://bugreports.qt-project.org/browse/QTBUG-29344
>
>


-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.0.1 RC -- Release Testing

2013-01-27 Thread Loaden

qt-windows-opensource-5.0.1-msvc2010_64-x86_64-offline-rc1.exe
The ICU binary is x86 arch. It's wrong.
Simply replace the icu49*.dll with 64bit version, then the crash solved.

https://bugreports.qt-project.org/browse/QTBUG-29344

2013/1/25 Motyka Rafal 

>  Hello,
>
> Qt 5.0.1 RC release testing has been started. We would like to kindly ask
> the Qt Community for help by testing the new packages.
>
>1. Installer packages are available here:
>http://releases.qt-project.org/qt5/5.0.1-rc1/ 
> 
>
>2. Qt bug reports should be reported in JIRA:
>https://bugreports.qt-project.org/
>
>3. Could you please report your testing effort via
>http://testresults.qt-project.org/forms/release-testing/  ?
>
> Thank you.
>
> Best regards,
>
> /Rafal
>
>
>
> Rafal Motyka
> QE Engineer
> Digia, Qt
>
>
>
> Email: rafal.mot...@digia.com 
> Mobile: +47 95005389
> http://qt.digia.com
> Qt Blog: http://blog.qt.digia.com/
> Qt Facebook: www.facebook.com/qt
> Qt Twitter: www.twitter.com/qtcommercial
>
>  --
>
> PRIVACY AND CONFIDENTIALITY NOTICE
>
> This message and any attachments are intended only for use by the named
> addressee and may contain privileged and/or confidential information. If
> you are not the named addressee you should not disseminate, copy or take
> any action in reliance on it. If you have received this message in error,
> please contact the sender immediately and delete the message and any
> attachments accompanying it. Digia Plc does not accept liability for any
> corruption, interception, amendment, tampering or viruses occurring to this
> message.
>
> -
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.0.1 -- Release Testing

2013-01-25 Thread Loaden

After installed
qt-windows-opensource-5.0.1-msvc2010_64-x86_64-offline-2013-01-24-418.exe,
I can't running xmlpatterns.exe,assistant.exe,etc on Windows 7 64bit OS.


2013/1/18 Motyka Rafal 

>  Hello,
>
> Qt 5.0.1 release testing has been started. We would like to kindly ask
> the Qt Community for help by testing the new packages.
>
> 1. Installer packages are available here:
>http://releases.qt-project.org/digia/5.0.1/backups/2013-01-18-412/
>
>2. Qt bug reports should be reported in JIRA:
>https://bugreports.qt-project.org/
>
> Thank you.
>
> Best regards,
>
> /Rafal
>
>
>
> Rafal Motyka
> QE Engineer
> Digia, Qt
>
>
>
> Email: rafal.mot...@digia.com 
> Mobile: +47 95005389
> http://qt.digia.com
> Qt Blog: http://blog.qt.digia.com/
> Qt Facebook: www.facebook.com/qt
> Qt Twitter: www.twitter.com/qtcommercial
>
>  --
>
> PRIVACY AND CONFIDENTIALITY NOTICE
>
> This message and any attachments are intended only for use by the named
> addressee and may contain privileged and/or confidential information. If
> you are not the named addressee you should not disseminate, copy or take
> any action in reliance on it. If you have received this message in error,
> please contact the sender immediately and delete the message and any
> attachments accompanying it. Digia Plc does not accept liability for any
> corruption, interception, amendment, tampering or viruses occurring to this
> message.
>
> -
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
<>___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt5 Docs Bug: How to Create Qt Plugins

2013-01-13 Thread Loaden

hi, there!
After reading this topic:
http://qt-project.org/doc/qt-5.0/qtcore/plugins-howto.html
There seems have a bug, see the source:

For example, here's the definition of an interface class:

   * \snippet tools/plugandpaint/interfaces.h 2*

Here's the definition of a plugin class that implements that
interface:

   * \snippet tools/plugandpaintplugins/extrafilters/extrafiltersplugin.h 0*


*The bug: *the code snippet show nothing.

--
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5 RC Testing

2012-12-19 Thread Loaden

Why the 64bit for MSVC2010 weren't part of RC2.
I remember the Qt-Term promise will make both 32bit and 64bit package for
msvc2010 happen in Qt5 final release.
Am I wrong or missed something?

2012/12/19 Thiago Macieira 

> Because they weren't part of RC2.




-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5 RC Testing

2012-12-19 Thread Loaden

Why don't build an 64-bit package for Windows before the final release?


2012/12/18 Motyka Rafal 

>  Hello,
>
> There is new version available for testing:
> http://releases.qt-project.org/digia/5.0.0/backups/2012-12-18-389/
>
>
> Best regards,
>
> /Rafal
>
>
>
>
> Rafal Motyka
> QE Engineer
> Digia, Qt
>
>
>
> Email: rafal.mot...@digia.com 
> Mobile: +47 95005389
> http://qt.digia.com
> Qt Blog: http://blog.qt.digia.com/
> Qt Facebook: www.facebook.com/qt
> Qt Twitter: www.twitter.com/qtcommercial
>
>  --
>
> PRIVACY AND CONFIDENTIALITY NOTICE
>
> This message and any attachments are intended only for use by the named
> addressee and may contain privileged and/or confidential information. If
> you are not the named addressee you should not disseminate, copy or take
> any action in reliance on it. If you have received this message in error,
> please contact the sender immediately and delete the message and any
> attachments accompanying it. Digia Plc does not accept liability for any
> corruption, interception, amendment, tampering or viruses occurring to this
> message.
>
> -
>
>
>--
> *From:* Motyka Rafal
> *Sent:* Monday, December 17, 2012 1:44 PM
>
> *To:* development@qt-project.org; Digia Site Oslo Nydalen
> *Subject:* RE: Qt 5 RC Testing
>
>   Hello,
>
> Please make sure that the form:
> http://testresults.qt-project.org/forms/release-testing/
> is submitted after you finish testing.
>
> Best regards,
>
> /Rafal
>
>
>
>--
> *From:* Motyka Rafal
> *Sent:* Monday, December 17, 2012 10:52 AM
> *To:* development@qt-project.org; Digia Site Oslo Nydalen
> *Subject:* RE: Qt 5 RC Testing
>
>   Hello,
>
> New packages are available and ready for testing:
> http://releases.qt-project.org/digia/5.0.0/backups/2012-12-17-386/
> Please use it for testing. With this version we addressed remaining P0 and
> P1 issues.
>
> Here is the list of changes (at this moment under verification):
>   https://codereview.qt-project.org/42825
>   https://codereview.qt-project.org/42823
>   https://codereview.qt-project.org/42821
>   https://codereview.qt-project.org/42820
>   https://codereview.qt-project.org/42819
>   https://codereview.qt-project.org/42834
>   https://codereview.qt-project.org/42833
>   https://codereview.qt-project.org/42832
>   https://codereview.qt-project.org/42831
>   https://codereview.qt-project.org/42828
>   https://codereview.qt-project.org/42846
>   https://codereview.qt-project.org/42845
>   https://codereview.qt-project.org/42844
>   https://codereview.qt-project.org/42843
>   https://codereview.qt-project.org/42848
>   https://codereview.qt-project.org/42850
>   https://codereview.qt-project.org/42849
>
> Best regards,
>
> /Rafal
>
>
>
>
>
> -
>
>
>--
> *From:* Motyka Rafal
> *Sent:* Wednesday, December 05, 2012 12:36 PM
> *To:* development@qt-project.org
> *Subject:* Qt 5 RC Testing
>
>   Hello,
>
> New packages are available and ready for testing:
> http://releases.qt-project.org/digia/5.0.0_rc1/backups/2012-12-05-365/
>
> Best regards,
>
> /Rafal
>
>
>
> Rafal Motyka
> QE Engineer
> Digia, Qt
>
>
>
> Email: rafal.mot...@digia.com 
> Mobile: +47 95005389
> http://qt.digia.com
> Qt Blog: http://blog.qt.digia.com/
> Qt Facebook: www.facebook.com/qt
> Qt Twitter: www.twitter.com/qtcommercial
>
>  --
>
> PRIVACY AND CONFIDENTIALITY NOTICE
>
> This message and any attachments are intended only for use by the named
> addressee and may contain privileged and/or confidential information. If
> you are not the named addressee you should not disseminate, copy or take
> any action in reliance on it. If you have received this message in error,
> please contact the sender immediately and delete the message and any
> attachments accompanying it. Digia Plc does not accept liability for any
> corruption, interception, amendment, tampering or viruses occurring to this
> message.
>
> -
>
>
>--
> *From:* Motyka Rafal
> *Sent:* Tuesday, December 04, 2012 12:10 PM
> *To:* development@qt-project.org
> *Subject:* Qt 5 RC Testing
>
>   Hello,
>
> There are new packages available for testing on Linux and Mac. We're
> working on Windows installer package.
> http://releases.qt-project.org/digia/5.0.0_rc1/backups/2012-12-04-363/
>
> Please feel free to test them. We will appreciate your feedback.
>
> Known issues are to be found here:
> http://qt-project.org/wiki/Qt500RC1KnownIssues
>
>
> Best regards,
>
> /Rafal
>
>
>
>--
> *From:* Motyka Rafal
> *Sent:* Monday, December 03, 2012 12:34 PM
> *To:* development@qt-project.org
> *Subject:* Qt 5 RC Testing

Re: [Development] Heads up for Windows devs: ANGLE landing soon

2012-10-23 Thread Loaden

2012/10/23 Jason Barron 

> It works on MSVC and MinGW (both 32-bit and 64-bit).


Sounds great!
But I thought it should only work with mingw-w64 (support directx9), not
mingw.org, that right?


-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

2012-10-04 Thread Loaden

2012/10/4 Rafael Roquetto 

> Basically what you are doing is telling everyone there is no further
> discussion.
>
> My point is, it is not about leaving the users without the given changes.
> On
> the contrary, I even suggested that yet another super critical patch gets
> included (SSL), even though this means we are deviating from the standard
> release workflow. The main goal here is to benefit the users. As I said
> before, it's an excepcional case, but there is still the wrong way and the
> right way. The right way is naming it 4.8.4.
>
+1


-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Branching for Qt 5 repositories

2012-09-28 Thread Loaden

I think so, so I have to keep silent anymore.

2012/9/28 Stephen Kelly 

> Unfortunately there's no chance of changing it, I'm sure.




-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Branching for Qt 5 repositories

2012-09-27 Thread Loaden

At lease, I think the 'dev' is not a good name for remote branch.
Does it mean the other branch is in no--active-developing state?
I prefer using 'feature' instead. All the new feature should go 'feature'
branch.
and the 'stable' is only bug fix branch.

2012/9/28 Lincoln Ramsay 

> Luckily we use git so you can give the branches any name you want on your
> local repo :)
>



-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Branching for Qt 5 repositories

2012-09-27 Thread Loaden

I prefer:
dev -> next
stable -> master
release -> release

>next
-->master
-->release

2012/9/28 Laszlo Papp 

> > They are:
> >  - dev: unfrozen branch, containing alpha-quality[*] code that is ready
> to go
> >into beta testing at any time
>
> What is the reason for calling this "dev" instead of "master" which is
> more common for developers, and it would not have an impact on the
> submitted changes to gerrit even in a year or more.
>
> >  - stable: feature-frozen branch, containing beta-quality or better code
> >  - release: deep-frozen branch, for which only the release team should
> >approve changes, containing code about to be released
> >
> > [*] alpha quality is feature complete, working, documented, tested, etc.
>
> I think this is a bit excessive for an alpha quality description
> unless you do not mean "fully" before each of those qualifiers.
>
> > Note that there is no "master" branch any more. In addition, the default
> > branch  (the one that gets checked out on a new clone) will be either
> stable
> > or release, but definitely not dev. The intention is that new developers
> who
> > clone Qt repositories for the first time are presented with a stable
> codebase
> > they can begin working on, bugfixing and even developing new features
> for.
>
> This leaves me one question: what if someone would like to fix a bug
> or start working on a new feature no matter what the stable or release
> contains at that very moment? That person may miss:
>
> 1) Bug that was already fixed in the development branch.
> 2) Feature that may have been already put into the development branch,
> but it is not yet in the stable or release due to its current quality.
> However, a new developer should not reinvent that due to a mistake.
>
> I mean the workflow is that for many people, especially when bug
> found: clone, fix, and build in general. Perhaps this could be aided
> with a good documentation in the end. I do not know, this situation
> has just come up to my mind. :-)
>
> Laszlo
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
*Please don't ask where I come from, It's a shame!*
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Stepping down as maintainer

2012-09-20 Thread Loaden

I am so sad to heard this. and I am greatful for your past work.
God bless you!

2012/9/21 

> 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!
>
>
> Kind regards,
> Leandro T. C. Melo
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Digia acquisition closed

2012-09-18 Thread Loaden

Text Editors & Language Support


Germany — Text Editors & Language SupportC/C++

Germany — Congrats!
But seems we lost the C/C++ Language maintainer. :(

2012/9/18 Thorbjørn Martsum 

> +1 and thanks for the info :)
>
> Is there an official (and final) count of developers moved from Nokia to
> Digia?
> Is it assumable that the current maintainers keep their positions within
> Digia?
> (and in that case ... the maintainer list seems to need an update  
> http://qt-project.org/wiki/Maintainers )
>
>
>
> On Tue, Sep 18, 2012 at 1:19 PM, Knoll Lars  wrote:
>
>> Hi everybody,
>>
>> I wanted to let you all know that the acquisition of Qt by Digia has been
>> completed yesterday. Many Trolls in Oslo and Berlin have their first day
>> working for Digia today. In Oslo we had lots of champagne and cake in the
>> morning, giving us a pretty good start into the day ;-)
>>
>> You will from now on see all the developers that have transferred over to
>> Digia posting and submitting code with their brand new Digia email
>> addresses.
>>
>> This change should for the most part not have any effects on
>> qt-project.org, but there are a few formal and legal changes happening
>> now:
>>
>> 1. The CLA's of all contributors haven been assigned from Nokia to Digia.
>> This is mainly an FYI, as nobody who has signed a CLA will need to take any
>> explicit action here.
>>
>> 2. All traffic to qt.nokia.com will be redirected to qt.digia.com.
>>
>> 3. Digia has taken responsibility for the qt-project.org infrastructure
>> and committed itself to continue funding it.
>>
>> 4. Digia has entered into the KDE Free Qt foundation agreement and is
>> from now on bound by it.
>>
>> 5. With the acquisition, the Nokia copyrights on the Qt code base all
>> transfer to Digia. Because of this we will need to change the copyright
>> headers in all Qt source files from Nokia to Digia. In addition, we will
>> re-add a small clause about commercial licensing into the headers to list
>> all possible licensing variants there. The reason for adding the commercial
>> piece is mainly transparency (because these are the possible licensing
>> options). In addition, this change will enable us to avoid having to
>> rewrite licensing headers during the release creating in the future and
>> keep the same, unchanged source files in all releases (OSS and commercial).
>>
>> With these changes the new licensing header for QObject will look as
>> follows:
>>
>>
>> /
>> **
>> ** Copyright (C) 2012 Digia Plc and/or its subsidiary(-ies).
>> ** Contact: http://qt-project.org/legal
>> **
>> ** This file is part of the QtCore module of the Qt Toolkit.
>> **
>> ** $QT_BEGIN_LICENSE:LGPL$
>> ** Commercial License Usage
>> ** Licensees holding valid commercial Qt licenses may use this file in
>> ** accordance with the commercial license agreement provided with the
>> ** Software or, alternatively, in accordance with the terms contained in
>> ** a written agreement between you and Digia.  For licensing terms and
>> ** conditions see http://qt.digia.com/licensing.  For further information
>> ** use the contact form at http://qt.digia.com/contact-us.
>> **
>> ** GNU Lesser General Public License Usage
>> ** Alternatively, this file may be used under the terms of the GNU Lesser
>> ** General Public License version 2.1 as published by the Free Software
>> ** Foundation and appearing in the file LICENSE.LGPL included in the
>> ** packaging of this file.  Please review the following information to
>> ** ensure the GNU Lesser General Public License version 2.1 requirements
>> ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
>> **
>> ** In addition, as a special exception, Digia gives you certain additional
>> ** rights.  These rights are described in the Digia Qt LGPL Exception
>> ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
>> **
>> ** GNU General Public License Usage
>> ** Alternatively, this file may be used under the terms of the GNU
>> ** General Public License version 3.0 as published by the Free Software
>> ** Foundation and appearing in the file LICENSE.GPL included in the
>> ** packaging of this file.  Please review the following information to
>> ** ensure the GNU General Public License version 3.0 requirements will be
>> ** met: http://www.gnu.org/copyleft/gpl.html.
>> **
>> **
>> ** $QT_END_LICENSE$
>> **
>>
>> /
>>
>> As you can see, it's basically the same header as before, will all
>> occurrences of Nokia replaced by Digia, the section about "Commercial
>> License Usage" added and the contact page changed to qt-project.org/legalso 
>> that we have a better landing page for legal questions (that page is
>> being created right now…).
>>
>> Cheers,
>> Lars
>>
>> ___
>> Development mailing list
>> Development@qt-project.org

[Development] Does Digia plan to ship Qt5 for every module?

2012-09-15 Thread Loaden

After test the Qt5 beta1 package both on Windows and Linux, I have to
install all thing to hard disk.
But, I just interesting for few modules, e.g. qtbase, qtqml. I don't want
forced install other modules (e.g. qtwebkit...)
Please let's user can make a choice for install.
Thanks!

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] How to build Qt5's docs?

2012-09-15 Thread Loaden

Still not work on Windows (MSVC2010SP1) for curently master branch (today).


>  D:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qdoc.exe -installdir
> D:/qpSOFT/Projects/BuildQt5-x64/qtbase/doc
> D:/qpSOFT/Projects/Qt5/qtdeclarative/src/qml/doc/qtqml.qdocconf
> D:/qpSOFT/Projects/Qt5/qtdeclarative/src/qml/doc/qtqml.qdocconf:1: error:
> Cannot open file
> 'D:/qpSOFT/Projects/Qt5/qtdeclarative/src/qml/doc/global/qt-html-templates-offline.qdocconf':
> ???
> Cannot open file
> 'D:/qpSOFT/Projects/Qt5/qtdeclarative/src/qml/doc/global/qt-html-templates-offline.qdocconf':
> ???
> Aborting
> NMAKE : fatal error U1077:
> 'D:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qdoc.exe' : return code '0x1'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
>


2012/8/27 Alan Ezust 

> make qch_docs (on linux) works for me now too!
> thanks!
>
> On Fri, Aug 24, 2012 at 9:42 PM, Loaden  wrote:
> > I can using 'make docs' to create qt.qch for now.
> > Thanks!
> >
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 Cmake Scripts: wrong include path or Unnecessary?

2012-09-15 Thread Loaden

>
> It's probably the same. "default" is either a copy or a symlink to the
> mkspec
> Qt was compiled with.
>
On Windows, "default" not a copy neither symlink. It only include an
qmake.conf

> QMAKESPEC_ORIGINAL = D:/qpSOFT/MyDEV/sdk/qt/mkspecs/win32-msvc2010
> include(../win32-msvc2010/qmake.conf)
>


> For qplatformdefs.h.
>
Does we really need qplatformdefs.h for compile Qt-based application?
I guess it only used to compile Qt self.

> 2012/9/15 Thiago Macieira 

> >
> > I thought it should be:
> > list(APPEND Qt5Core_INCLUDE_DIRS
> > "${_qt5_corelib_install_prefix}/mkspecs/win32-msvc2010")
>
> It's probably the same. "default" is either a copy or a symlink to the
> mkspec
> Qt was compiled with.
>
> > Or, just remove it.
> > I don't know why we need this path for includes search?
>
> For qplatformdefs.h.
>
>


-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt5 Cmake Scripts: wrong include path or Unnecessary?

2012-09-14 Thread Loaden

See Qt5CoreConfigExtras.cmake


> LN34: list(APPEND Qt5Core_INCLUDE_DIRS
> "${_qt5_corelib_install_prefix}/mkspecs/default")
>

I thought it should be:
list(APPEND Qt5Core_INCLUDE_DIRS
"${_qt5_corelib_install_prefix}/mkspecs/win32-msvc2010")

Or, just remove it.
I don't know why we need this path for includes search?

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt5 Beta1: MSVC2010SP1_64bit + WSDK7.5, Using '-ltcg' lead all gui-tools crash!

2012-09-13 Thread Loaden

Only Crash on 64bit Library.
e.g.
assistant.exe
designer.exe

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 Beta1: Can't run assistant.exe / designer.exe / linguist.exe on Windows 7 64 bit OS

2012-09-13 Thread Loaden

Because I am using -ltcg configure option for MSVC 2010SP1 + Windows SDK
7.5.
Remove -ltcg then running well.
在 2012年9月12日 下午12:25，Loaden 写道：

> 64bit MSVC2010SP1+SDK7.5 + 64bit Qt library + 64bit OS:
> Application Error
> 0x01d
>
> 32bit MSVC2010SP1+SDK7.5 + 32bit Qt library + 64bit OS:
> Everything works well.
>
> Any comments?
>
> 问题签名:
>   问题事件名称: APPCRASH
>   应用程序名: designer.exe
>   应用程序版本: 1.0.0.0
>   应用程序时间戳: 504ec1a8
>   故障模块名称: QtGui5.dll
>   故障模块版本: 5.0.0.0
>   故障模块时间戳: 504eb30e
>   异常代码: c01d
>   异常偏移: 0028b790
>   OS 版本: 6.1.7601.2.1.0.256.1
>   区域设置 ID: 2052
>   其他信息 1: 14bd
>   其他信息 2: 14bd3a5532c8f045c550a0948d6875f1
>   其他信息 3: 0d05
>   其他信息 4: 0d054ff90c44a45eb3e7775c27bf9d3c
>
> 联机阅读隐私声明:
>   http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0804
>
> 如果无法获取联机隐私声明，请脱机阅读我们的隐私声明:
>   C:\Windows\system32\zh-CN\erofflps.txt
>
>
> --
> Best Regards
> Yuchen
>
>


-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt5 Beta1: Can't run assistant.exe / designer.exe / linguist.exe on Windows 7 64 bit OS

2012-09-11 Thread Loaden

64bit MSVC2010SP1+SDK7.5 + 64bit Qt library + 64bit OS:
Application Error
0x01d

32bit MSVC2010SP1+SDK7.5 + 32bit Qt library + 64bit OS:
Everything works well.

Any comments?

问题签名:
  问题事件名称: APPCRASH
  应用程序名: designer.exe
  应用程序版本: 1.0.0.0
  应用程序时间戳: 504ec1a8
  故障模块名称: QtGui5.dll
  故障模块版本: 5.0.0.0
  故障模块时间戳: 504eb30e
  异常代码: c01d
  异常偏移: 0028b790
  OS 版本: 6.1.7601.2.1.0.256.1
  区域设置 ID: 2052
  其他信息 1: 14bd
  其他信息 2: 14bd3a5532c8f045c550a0948d6875f1
  其他信息 3: 0d05
  其他信息 4: 0d054ff90c44a45eb3e7775c27bf9d3c

联机阅读隐私声明:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0804

如果无法获取联机隐私声明，请脱机阅读我们的隐私声明:
  C:\Windows\system32\zh-CN\erofflps.txt


-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Does any one interesting to help writting CMake Scripts for QtCreator?

2012-09-11 Thread Loaden

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
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] How to get all compile flags / definitions / include_directories of target?

2012-09-03 Thread Loaden

Hi, list!
I want write a PrecompiledHeader.cmake to support PCH for QtCreator.
For now, It works well use MSVC, see:
https://codereview.qt-project.org/#change,34052
I have some trouble with how to get GCC's compile flags / definitions /
include_directories.
My way (does not work yet):


> macro(get_gcc_compile_flags target flags)
> string(TOUPPER "CMAKE_CXX_FLAGS_${CMAKE_BUILD_TYPE}" name)
> set(flags "${${name}} ${CMAKE_CXX_FLAGS} ${CMAKE_CXX_COMPILER_ARG1}")
> get_target_property(value ${target} COMPILE_FLAGS)
> if (value)
> list(APPEND flags ${value})
> endif()
> get_target_property(value ${target} TYPE)
> get_target_property(value ${target} COMPILE_DEFINITIONS)
> if (value)
> foreach(item ${value})
> list(APPEND flags "-D${item}")
> endforeach()
> endif()
> STRING(TOUPPER "COMPILE_DEFINITIONS_${CMAKE_BUILD_TYPE}" name)
> get_target_property(value ${target} ${name})
> if (value)
> foreach(item ${value})
> list(APPEND flags "-D${item}")
> endforeach()
> endif()
> get_directory_property(value DEFINITIONS)
> if (value)
> list(APPEND flags ${value})
> endif()
> get_directory_property(value INCLUDE_DIRECTORIES)
> if (value)
> foreach(item ${value})
> list(APPEND flags "-I${item}")
> endforeach()
> endif()
> #separate_arguments(flags)
> endmacro()
>

Any help or comments are welcome!
Thanks!

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Mingw-w64-public] Fwd: Choosing a new MinGW for Qt 5

2012-08-31 Thread Loaden

2012/8/31 K. Frank 

> Also, I've had a problem with recent versions of mingw-w64 gdb.  It's slow
> as molasses loading up and/or initializing an application (minutes), but
> once the application starts, it seems to be fine. (I don't think that this
> is
> Qt specific.)
>
Because it's using python by default.

>
> Obviously, you need a stable enough and good enough version of gcc to
> get Qt built, but in general my preference would be for you to push up
> close to the mingw-w64 bleeding edge.  Getting Qt built is a good test
> for the compiler, so you'd be helping the mingw-w64 project.
>
Agree!
mingw-w64 is great / actively project, it's just need more help.
And it will support std::thread use win32 thread in the soon.
And it just works well. both native compiling Qt5 or cross compiling.

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CMake for Qt5: Cross Compilation for Windows using MinGW-w64

2012-08-30 Thread Loaden

It fixed the problem.
Thanks!

2012/8/31 Stephen Kelly 

> 5408225286dfdd4cd957c129db0873cbbab05bc0
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Choosing a new MinGW for Qt 5

2012-08-30 Thread Loaden

It's can be fixed just replace the mingw32-make.exe.
And it's the best choice to separate package for 32bit vs 64bit really.
-m32 and -m64 will possible can't works well on Windows.

2012/8/30 

> Rubens release is currently broken, and there shouldn't be a need for a
> separate package for 32bit vs 64bit really.
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CMake for Qt5: Cross Compilation for Windows using MinGW-w64

2012-08-30 Thread Loaden

Hi, there!
I am try to cross compilation qt5 apps on Linux.
By this wiki point: http://www.cmake.org/Wiki/CmakeMingw
I can make the simple qt5 demo works.

main.cpp

> #include 
> #include 
>
> int main(int argc, char *argv[])
> {
> QApplication a(argc, argv);
> QLabel *label = new QLabel("Hello World");
> label->show();
> int i;
> return a.exec();
> }
>

CMakeLists.txt

> cmake_minimum_required(VERSION 2.8.9 FATAL_ERROR)
>
> project(testproject)
>
> # Find includes in corresponding build directories
> set(CMAKE_INCLUDE_CURRENT_DIR ON)
> # Instruct CMake to run moc automatically when needed
> set(CMAKE_AUTOMOC ON)
>
> # Find the QtWidgets library
> find_package(Qt5Widgets)
>
> # Tell CMake to create the helloworld executable
> add_executable(helloworld main.cpp)
>
> # Use the Widgets module from Qt 5
> qt5_use_modules(helloworld Widgets)
>

loaden@qpsoft:~/qpSOFT/Projects/demo/m64$ cmake ..
> -DCMAKE_PREFIX_PATH=/home/loaden/qpSOFT/Projects/BuildQt5-m64/qtbase
> -DCMAKE_TOOLCHAIN_FILE=~/.mingw64.cmake
> -- The C compiler identification is GNU 4.7.1
> -- The CXX compiler identification is GNU 4.7.1
> -- Check for working C compiler: /opt/mingw64/bin/x86_64-w64-mingw32-gcc
> -- Check for working C compiler: /opt/mingw64/bin/x86_64-w64-mingw32-gcc
> -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /opt/mingw64/bin/x86_64-w64-mingw32-g++
> -- Check for working CXX compiler: /opt/mingw64/bin/x86_64-w64-mingw32-g++
> -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /home/loaden/qpSOFT/Projects/demo/m64
> loaden@qpsoft:~/qpSOFT/Projects/demo/m64$ make
> Scanning dependencies of target helloworld_automoc
> [ 33%] Automoc for target helloworld
> [ 33%] Built target helloworld_automoc
> Scanning dependencies of target helloworld
> [ 66%] Building CXX object CMakeFiles/helloworld.dir/main.cpp.obj
> [100%] Building CXX object
> CMakeFiles/helloworld.dir/helloworld_automoc.cpp.obj
> Linking CXX executable helloworld.exe
> [100%] Built target helloworld
>

When I try another demo, it's failed, and I can't find the reason.
CMakeLists.txt

> cmake_minimum_required(VERSION 2.8.9 FATAL_ERROR)
>
> project(testproject)
>
> # Find includes in corresponding build directories
> set(CMAKE_INCLUDE_CURRENT_DIR ON)
> # Instruct CMake to run moc automatically when needed
> set(CMAKE_AUTOMOC ON)
>
> # Find the QtWidgets library
> find_package(Qt5Widgets REQUIRED)
>
> # Tell CMake to create the helloworld executable
> add_executable(helloworld
> main.cpp
> mainwindow.cpp
> mainwindow.ui
> )
>
> # Use the Widgets module from Qt 5
> qt5_use_modules(helloworld Widgets)
>
> # Support UI files
> qt5_wrap_ui(ui_mainwindow.h mainwindow.ui)
>

I can sure this project can be build for Linux target.
It's just failed for cross build.

loaden@qpsoft:~/qpSOFT/Projects/qtdemo/m64$ cmake ..
> -DCMAKE_PREFIX_PATH=/home/loaden/qpSOFT/Projects/BuildQt5-m64/qtbase
> -DCMAKE_TOOLCHAIN_FILE=~/.mingw64.cmake
> -- The C compiler identification is GNU 4.7.1
> -- The CXX compiler identification is GNU 4.7.1
> -- Check for working C compiler: /opt/mingw64/bin/x86_64-w64-mingw32-gcc
> -- Check for working C compiler: /opt/mingw64/bin/x86_64-w64-mingw32-gcc
> -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /opt/mingw64/bin/x86_64-w64-mingw32-g++
> -- Check for working CXX compiler: /opt/mingw64/bin/x86_64-w64-mingw32-g++
> -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /home/loaden/qpSOFT/Projects/qtdemo/m64
> loaden@qpsoft:~/qpSOFT/Projects/qtdemo/m64$ make
> Scanning dependencies of target helloworld_automoc
> [ 20%] Automoc for target helloworld
> Generating moc_mainwindow.cpp
> No such file or directory
> AUTOMOC: error: process for
> /home/loaden/qpSOFT/Projects/qtdemo/m64/moc_mainwindow.cpp failed:
> No such file or directory
> moc failed...
> make[2]: *** [CMakeFiles/helloworld_automoc] Error 1
> make[1]: *** [CMakeFiles/helloworld_automoc.dir/all] Error 2
> make: *** [all] Error 2
>
>
-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CMake for Qt5: Does exist set(CMAKE_AUTOUIC ON) support? or plan?

2012-08-30 Thread Loaden

set(CMAKE_AUTOMOC ON) is great.
But for now I have to use qt5_wrap_ui macros.
e.g.

cmake_minimum_required(VERSION 2.8.9 FATAL_ERROR)
>
> project(testproject)
>
> # Find includes in corresponding build directories
> set(CMAKE_INCLUDE_CURRENT_DIR ON)
> # Instruct CMake to run moc automatically when needed
> set(CMAKE_AUTOMOC ON)
>
> # Find the QtWidgets library
> find_package(Qt5Widgets REQUIRED)
>
> # Tell CMake to create the helloworld executable
> add_executable(helloworld
> main.cpp
> mainwindow.cpp
> mainwindow.ui
> )
>
> # Use the Widgets module from Qt 5
> qt5_use_modules(helloworld Widgets)
>
> # Support UI files
> qt5_wrap_ui(ui_mainwindow.h mainwindow.ui)
>
> Any help? Thanks!

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Choosing a new MinGW for Qt 5

2012-08-30 Thread Loaden

I want to say, mingw-w64 is the best choice.
I am using ruben's personally build to compilation Qt5/QtCreator on both
Windows and Linux OS, and it works well!

2012/8/30 

> Hi,
>
> I'd like to get this on the table again: What is the MinGW package that we
> want to support officially? The matrix for Qt 5.0 right now says MinGW gcc
> 4.5 32 bit [1]. Note that when you're installing latest mingw from
> mingw.org it's already installing gcc 4.7, and I guess you'd need to dig
> into the archive to get gcc 4.5 ... But anyway, it's still 32 bit only.
>
> In the last days I gave the following packages that also support both 32
> bit and 64 bit a try:
>
> TDM-GCC: Nice installer, but somewhat stale (gcc 4.6.1 / gdb 7.3.1) + not
> much (visible) activity
> Mingw-64: last official 1.0 build is from a year ago (gcc 4.5.4). There
> are popular, 'semi-official' personal builds with 4.7.1 though ...
> Mingw-builds: gcc-4.7.1, gdb 7.4.1.  packages for gcc-7.4.2 are already in
> the prerelease directory ...
>
> One might think that the only difference in these packages is the gcc
> version, but this isn't the truth. They also deviate e.g. in the COM
> headers, which can easily lead to build breakages ... That's why I think
> it's important to promote _one_ mingw 64 bit package as the officially
> supported one, and ideally even get it CI tested.
>
> After trying all, I agree with Marius that mingw-builds seems a good
> choice. Qt 5 beta compiled out of the box for me with one minor patch [3]
> ...
>
> So, I think we have a couple of choices here:
>
>  * We could just add mingw-builds gcc 4.7.1 64 bit to the list of tier 1
> configurations, keeping mingw gcc 4.5 32 bit as reference platform.
> + no changes after beta for reference platforms
> - two different compilers are more work to test
>  * We could try to make both mingw-builds gcc 4.7.1 64 bit and 32 bit a
> tier one platform, and get rid of the Mingw from http://www.mingw.org/
> + The same toolchain can be tested for 32 bit and 64 bit
> - 5.0 beta is already out
> - gcc from mingw.org is probably more wide spread/better tested than
> mingw-builds
> * We could leave it as it is, with no recent mingw compiler to easily
> install, and no 64 bit one
>
> Opinions? Note that at the moment we don't test MinGW at all in the CI
> system [2].
>
> Regards
>
> Kai
>
> [1]: Official platform matrix:
> http://qt-project.org/wiki/Qt_5.0#ed49a36c4fd547e5e2ace11bef4f21cf
> [2]: CI system needs to build with MinGW on Windows:
> https://bugreports.qt-project.org/browse/QTQAINFRA-549
> [3]: Codecs: Fix compilation on MinGW if configure detects iconv:
> https://codereview.qt-project.org/#change,33936
>
>
> > -Original Message-
> > From: development-bounces+kai.koehne=nokia@qt-project.org
> > [mailto:development-bounces+kai.koehne=nokia@qt-project.org] On
> > Behalf Of Storm-Olsen Marius (Nokia-MP/Austin)
> > Sent: Friday, April 20, 2012 1:54 PM
> > To: pgqui...@elpauer.org
> > Cc: development@qt-project.org
> > Subject: Re: [Development] Choosing a new MinGW for Qt/Qt Creator/Qt SDK
> >
> > Now wait a minute, I never said such a thing.
> >
> > I said that the MinGW-w64 binaries are Cygwin-based now. Meaning, the
> > MinGW they release needs Cygwin DLLs to run.
> >
> > The output they generate is still native Win32 binaries, which does _not_
> > require Cygwin. (Anything else would be silly, since you could then just
> use
> > the normal Cygwin-provided gcc, and not MinGW.)
> >
> > Now, I do see that the latest "official release" actually comes from the
> > personal(!) build directory of a Ray Linn, and does not require Cygwin.
> > (I only noticed it when looking at the files page, and it says "Looking
> for the
> > latest version? Download mingw-w64-gcc-4.6.3-runtime-2.0.1-static-ada-
> > 20120321.7z (28.2 MB)", which happens to point to
> > http://sourceforge.net/projects/mingw-
> > w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/ray_linn/)
> >
> > But personally I much better like the structure, consistency, and
> variety of the
> > mingwbuilds project. You have to admit looking at
> > http://sourceforge.net/projects/mingwbuilds/files/windows-host/ it feels
> > much cleaner and professional. The MinGW-w64 project _feels_ as if it
> > doesn't have a clear mission. (I'm not saying they don't have one.)
> >
> > --
> > .marius
> >
> > On 20/04/2012 06:09, ext Pau Garcia i Quiles wrote:
> > > Hi,
> > >
> > > I'd say you are confusing "mingw-w64 is available in Cygwin" (like
> > > mingw.org is) with "mingw-w64-produced binaries need Cygwin DLLs".
> > >
> > > I've been using mingw-w64 for zsync on Windows (
> > > https://www.assembla.com/spaces/zsync-windows ) for quite some time
> > > and the zsync.exe and zysncmake.exe binaries work without Cygwin DLLs.
> > >
> > >
> > >
> > > On Fri, Apr 20, 2012 at 12:46 PM,
>  wrote:
> > >> Take another look. They haven't produced pure MinGW binary releases
> > >> since the end of 2011. The front page say

Re: [Development] Qt 5 beta

2012-08-30 Thread Loaden

Compilation should fine, but I can't build docs on Windows.
For a long time.

2012/8/30 

> The latest test of the windows source package was reported as a failure
> (by J-P Nurmi),
> so the beta might not even work for win32-msvc2010 mkspec.
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build Qt 5 with MinGW 4.7?

2012-08-26 Thread Loaden

You can add -std=c++11 in mkspecs/win32-g++/qmake.conf / CXXFLAGS by
yourself.
On Linux, These patchs should works well for support -std=c++11 using cross
compilation.
https://codereview.qt-project.org/#change,33044
https://codereview.qt-project.org/#change,33078


2012/8/26 Thiago Macieira 

> > Since it's indicated in this thread that we can still build C++11
> > executable with non-C++11 Qt library, so I will just go ahead and build
> > Qt 5 without it.
>
> Misfeature. The test is not implemented in the configure.exe because the
> standard MinGW we ship is 4.4 and doesn't benefit from C++11.




-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build Qt 5 with MinGW 4.7?

2012-08-25 Thread Loaden

Try MinGW-w64 4.7.1-2.
I can build qt5 on Windows or Linux (cross build). It's seems works well
except install on Windows.

2012/8/26 Stephen Chu 

> mingw32-make




-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] How to build Qt5's docs?

2012-08-25 Thread Loaden

Only works on Linux (ubuntu 12.04), not Windows 7 SP1 using MSVC2010SP1.
(shadow build)

>
> cd qtbase\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake.EXE
> d:\qpSOFT\Projects\Qt5\qtbase\qtbase.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  cd src\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\src.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  cd tools\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\tools.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  cd bootstrap\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\bootstrap\bootstrap.pro -o
> Makefile ) && D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile.Release
>  cd moc\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\moc\moc.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  cd rcc\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\rcc\rcc.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  cd qdoc\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\qdoc\qdoc.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile.Release
>  cd uic\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\uic\uic.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  cd corelib\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\corelib\corelib.pro -o Makefile ) &&
> D:\qpSOFT\MyDEV\bin\amd64\nmake.exe -f Makefile docs
>  d:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qdoc.exe -installdir
> D:/qpSOFT/Projects/BuildQt5-x64/qtbase/doc -indexdir ../../doc
> D:/qpSOFT/Projects/Qt5/qtbase/src/corelib/doc/qtcore.qdocconf
> Cannot find index directory ../../doc
> ASSERT: "&other != this" in file
> d:\qpsoft\projects\buildqt5-x64\qtbase\include\qtcore\../../../../Qt5/qtbase/src/corelib/tools/qstring.h,
> line 755
> NMAKE : fatal error U1077:
> 'd:\qpSOFT\Projects\BuildQt5-x64\qtbase\bin\qdoc.exe' : return code '0x1'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.



2012/8/25 Loaden 

> I can using 'make docs' to create qt.qch for now.
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build QtCreator failed use MSVC2010

2012-08-25 Thread Loaden

This build error still exist on Qt5 beta 1.

2012/7/17 Loaden 

> qmakeevaluator.obj : error LNK2019: unresolved external symbol
>> "__declspec(dllimport) public: static
>>  class QString __cdecl QString::fromWCharArray(unsigned short const
>> *,int)" (__imp_?fromWCharArray@Q
>> String@@SA?AV1@PBGH@Z) referenced in function "public: void __thiscall
>> QMakeEvaluator::loadDefaults(
>> void)" (?loadDefaults@QMakeEvaluator@@QAEXXZ)
>> D:\qpSOFT\Projects\QtCreator\build\x86-release\lib\qtcreator\plugins\Nokia\QtSupport.dll
>> : fatal err
>> or LNK1120: 1 unresolved externals
>>
>
> This patch can't solved the problem:
>
>
>> diff --git a/src/corelib/tools/qstring.h b/src/corelib/tools/qstring.h
>> index 2edfc04..249088b 100644
>> --- a/src/corelib/tools/qstring.h
>> +++ b/src/corelib/tools/qstring.h
>> @@ -818,7 +818,7 @@ inline int QString::toWCharArray(wchar_t *array) const
>>  }
>>  return toUcs4_helper(d->data(), size(), reinterpret_cast> *>(array));
>>  }
>> -inline QString QString::fromWCharArray(const wchar_t *string, int size)
>> +Q_CORE_EXPORT inline QString QString::fromWCharArray(const wchar_t
>> *string, int size)
>>  {
>>  return sizeof(wchar_t) == sizeof(QChar) ?
>> fromUtf16(reinterpret_cast(string), size)
>>  :
>> fromUcs4(reinterpret_cast(string), size);
>>
>
> --
> Please don't ask where I come from, It's a shame!
> Best Regards
> Yuchen
>
>


-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] How to build Qt5's docs?

2012-08-24 Thread Loaden

I can using 'make docs' to create qt.qch for now.
Thanks!

2012/8/22 Alan Ezust 

> I had that problem too. It was looking for qhelpgenerator in the wrong
> place - in qtbase/bin instead of my installed QT5 directory, where the
> executable was. I ended up having to do 1 of 2 things to work around
> this.
>
>   1. re-run installed qmake in the qtdocs directory
>   2. copy the qhelpgenerator executable into $QTBASE/bin
>
> I am not sure if i had a dirty build or what. I've been doing lots of
> what I thought were "clean" rebuilds from new git pulls but sometimes
> I miss something.
>
>
> On Wed, Aug 22, 2012 at 12:31 AM,   wrote:
> >
> > On Aug 22, 2012, at 9:16 AM, ext Äijälä Johanna <
> johanna.aij...@digia.com> wrote:
> >> /bin/sh:
> /home/joaijala/Work/qt5_srcpkg/doc-build/qt-everywhere-opensource-src-5.0.0/qtbase/bin/qhelpgenerator:
> not found
> >> make[1]: *** [qch_docs] Error 127
> >> make[1]: Leaving directory
> `/home/joaijala/Work/qt5_srcpkg/doc-build/qt-everywhere-opensource-src-5.0.0/qtdoc/doc'
> >> make: *** [sub-doc-qch_docs] Error 2
> >>
> >> Is there any other fixes still pending?
> >
> > qhelpgenerator is not there in your setup for some reason. Did you
> forget to build it?
> >
> > Lars
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Request: Mark classes with \module in documentation

2012-08-24 Thread Loaden

I can build docs to create qt.qch for now (today, master).

2012/8/25 

> You might be right in theory, but we are currently simply not able to
> build the docs in a modular way.




-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt JsonDB

2012-08-24 Thread Loaden

Sounds good choice!

2012/8/25 

> Hi,
>
> I've just pushed a patch to remove Qt JsonDB from qt5.git to codereview
> (see https://codereview.qt-project.org/#change,33524).
>
> The reason for this is that the project is not done and it also doesn't
> fit very well into the current scope for Qt 5. In addition, it will be
> difficult to maintain it properly at least in the near future. For anybody
> using it, the module will continue to be available on qt-project.
>
> Cheers,
> Lars
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [QBS] "qbs platforms ls" show nothing, "qbs-platforms ls" works well!

2012-08-24 Thread Loaden

using MinGW-w64 to build qbs has the same issue on Windows 7 SP1.

2012/6/27 Joerg Bornemann 

> So you mean in Qt5 QProcess:execute does not forward the output of the
> process on Windows? I can't reproduce this issue with Qt5 and MSVC2008.
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 Beta 1: Build all target on Windows, make release target in default

2012-08-24 Thread Loaden

I mean build Qt5 by myself, not the package.
For current master, -debug-and-release will use debug as default target.
After build finished, qdoc.exe / uic.exe ... will use debug version.

2012/8/24 Thiago Macieira 
>

> On sexta-feira, 24 de agosto de 2012 13.51.29, Loaden wrote:
> > There exist better way to solved the problem?
> > Please point out.
> >
> > Thanks a lot!
>
> By the way, please use the releas...@qt-project.org mailing list for
> discussing the status of the beta packages. And please include the date of
> the
> package that you downloaded.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>  Intel Sweden AB - Registration Number: 556189-6027
>  Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt5 Beta 1: Build all target on Windows, make release target in default

2012-08-23 Thread Loaden

For now user can add build_all in qconfig.pri / CONFIG on Windows
Change From: CONFIG += debug ... To: CONFIG += debug build_all ...
And using -debug-and-release config option.

It will build and install debug target first,
then build and install release target.

It make sure all execute files be release mode.
And with both of debut and release library.

See: https://codereview.qt-project.org/#change,33451


I tried make && make release, but it can't solved the install issue. After
install, the debug target will override the release target.

e.g. moc/uic/qdoc...

There exist better way to solved the problem?
Please point out.

Thanks a lot!

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 Beta 1: Install failed on Windows using MinGW-w64 4.7.1-2

2012-08-23 Thread Loaden

Still now work!

2012/8/23 Loaden 

> change the install root path from d:\qpSOFT\Projects\BuildQt5-m64\temp
> to d:/qpSOFT/Projects/BuildQt5-m64/temp ?
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 Beta 1: Install failed on Windows using MinGW-w64 4.7.1-2

2012-08-23 Thread Loaden

Do you mean I need change the install root path from
d:\qpSOFT\Projects\BuildQt5-m64\temp
to d:/qpSOFT/Projects/BuildQt5-m64/temp ?


2012/8/23 Oswald Buddenhagen 

> d:\qpSOFT\Projects\BuildQt5-m64\temp/
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt5 Beta 1: Install failed on Windows using MinGW-w64 4.7.1-2

2012-08-23 Thread Loaden

*mingw32-make --trace install INSTALL_ROOT=%INSTROOT% >>install.log 2>&1*
Error MSG:

> makefile:56: update target `module-qtbase-install_subtargets' due to: FORCE
> if not exist qtbase\ mkdir qtbase\
> cd qtbase\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\qtbase.pro -o Makefile ) && mingw32-make -f
> Makefile install
> mingw32-make[1]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase'
> Makefile:51: update target `sub-src-install_subtargets' due to: FORCE
> if not exist src\ mkdir src\
> cd src\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\src.pro -o Makefile ) && mingw32-make
> -f Makefile install
> mingw32-make[2]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src'
> Makefile:62: update target `sub-tools-install_subtargets' due to: FORCE
> if not exist tools\ mkdir tools\
> cd tools\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\tools.pro -o Makefile ) &&
> mingw32-make -f Makefile install
> mingw32-make[3]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools'
> Makefile:53: update target `sub-tools-bootstrap-install_subtargets' due
> to: FORCE
> if not exist bootstrap\ mkdir bootstrap\
> cd bootstrap\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\bootstrap\bootstrap.pro -o
> Makefile ) && mingw32-make -f Makefile install
> mingw32-make[4]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/bootstrap'
> Makefile:43: update target `release-install' due to: FORCE
> mingw32-make -f Makefile.Release install
> mingw32-make[5]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/bootstrap'
> mingw32-make[5]: Nothing to be done for `install'.
> mingw32-make[5]: Leaving directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/bootstrap'
> mingw32-make[4]: Leaving directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/bootstrap'
> Makefile:78: update target `sub-moc-install_subtargets' due to:
> sub-tools-bootstrap-install_subtargets FORCE
> if not exist moc\ mkdir moc\
> cd moc\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\moc\moc.pro -o Makefile ) &&
> mingw32-make -f Makefile install
> mingw32-make[4]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/moc'
> Makefile:43: update target `release-install' due to: FORCE
> mingw32-make -f Makefile.Release install
> mingw32-make[5]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/moc'
> Makefile.Release:1022: update target `install_target' due to: first FORCE
> if not exist
> d:\qpSOFT\Projects\BuildQt5-m64\temp\qpSOFT\Projects\BuildQt5-m64\qtbase\bin
> mkdir
> d:\qpSOFT\Projects\BuildQt5-m64\temp\qpSOFT\Projects\BuildQt5-m64\qtbase\bin
>
> copy /y "..\..\..\bin\moc.exe"
> "d:\qpSOFT\Projects\BuildQt5-m64\temp\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\moc.exe"
> 1 file(s) copied.
> mingw32-make[5]: Leaving directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/moc'
> mingw32-make[4]: Leaving directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/moc'
> Makefile:103: update target `sub-rcc-install_subtargets' due to:
> sub-tools-bootstrap-install_subtargets FORCE
> if not exist rcc\ mkdir rcc\
> cd rcc\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\rcc\rcc.pro -o Makefile ) &&
> mingw32-make -f Makefile install
> mingw32-make[4]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/rcc'
> Makefile:43: update target `release-install' due to: FORCE
> mingw32-make -f Makefile.Release install
> mingw32-make[5]: Entering directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/rcc'
> Makefile.Release:465: update target `install_target' due to: first FORCE
> if not exist
> d:\qpSOFT\Projects\BuildQt5-m64\temp\qpSOFT\Projects\BuildQt5-m64\qtbase\bin
> mkdir
> d:\qpSOFT\Projects\BuildQt5-m64\temp\qpSOFT\Projects\BuildQt5-m64\qtbase\bin
>
> copy /y "..\..\..\bin\rcc.exe"
> "d:\qpSOFT\Projects\BuildQt5-m64\temp\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\rcc.exe"
> 1 file(s) copied.
> mingw32-make[5]: Leaving directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/rcc'
> mingw32-make[4]: Leaving directory
> `D:/qpSOFT/Projects/BuildQt5-m64/qtbase/src/tools/rcc'
> Makefile:128: update target `sub-qdoc-install_subtargets' due to:
> sub-tools-bootstrap-install_subtargets FORCE
> if not exist qdoc\ mkdir qdoc\
> cd qdoc\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qpSOFT\Projects\Qt5\qtbase\src\tools\qdoc\qdoc.pro -o Makefile ) &&
> mingw32-make -f Makefile install
> mingw32-make[4]: Entering directory
> `D:/qpSOFT/Projects/Bu

Re: [Development] How to build Qt5's docs?

2012-08-21 Thread Loaden

It's can't fix the problem.

../src/ja_JP/examples/arrowpad.qdoc:28: [It also exists here]
> ../src/zh_CN/getting-started/how-to-learn-qt.qdoc:28: Can't create link to
> 'Qt Object Model'
> ../src/zh_CN/getting-started/how-to-learn-qt.qdoc:28: Can't create link to
> 'Examples and Demos Launcher'
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ??"
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ?? ? "
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ?? ? "
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ?? ? "
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> Error in line 29823: Missing attribute in keyword at line 29823.
> make[2]: *** [docs] Error 255
> make[2]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qtdoc/doc'
> make[1]: *** [sub-doc-docs] Error 2
> make[1]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qtdoc'
> make: *** [module-qtdoc-docs] Error 2
>

2012/8/21 

> Can you try cherry-picking https://codereview.qt-project.org/#change,32986 (or
> wait until it is integrated).
>
>  That should fix the rest of the problems. (I think)
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] How to build Qt5's docs?

2012-08-21 Thread Loaden

I can confirmed this change fixed the qt3d's docs issue.
But Still has a error with widgets-tutorial.qdoc.

../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ??"
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ?? ? "
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ?? ? "
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:152: This page exists in more
> than one file: "Widgets ?? ? "
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:94: [It also exists here]
> ../src/zh_CN/tutorials/widgets-tutorial.qdoc:28: [It also exists here]
> Error in line 14348: Missing attribute in keyword at line 14348.
> make[2]: *** [docs] Error 255
> make[2]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qtdoc/doc'
> make[1]: *** [sub-doc-docs] Error 2
> make[1]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qtdoc'
> make: *** [module-qtdoc-docs] Error 2
>

2012/8/21 

> I just fixed this in https://codereview.qt-project.org/#change,33170
> After that integrates the documentation should build properly.
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] How to build Qt5's docs?

2012-08-20 Thread Loaden

I have tried:

make -C qtdoc qmake >>doc.log 2>&1
> make docs >>doc.log 2>&1
>
It's still not work for me.

> /home/loaden/qpSOFT/Projects/Qt5/qt3d/src/threed/doc/qt3d.qdocconf:1:
> error: Cannot open file
> '/home/loaden/qpSOFT/Projects/Qt5/qt3d/src/threed/doc/../../../doc/global/qt-html-templates-offline.qdocconf':
> No such file or directory
> Cannot open file
> '/home/loaden/qpSOFT/Projects/Qt5/qt3d/src/threed/doc/../../../doc/global/qt-html-templates-offline.qdocconf':
> No such file or directory
>
> Aborting
> make[3]: *** [docs] Error 1
> make[3]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qt3d/src/threed'
> make[2]: *** [sub-threed-docs_ordered] Error 2
> make[2]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qt3d/src'
> make[1]: *** [sub-src-docs] Error 2
> make[1]: Leaving directory `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qt3d'
> make: *** [module-qt3d-docs] Error 2


*I thought it's should be fixed before the Beta 1 released.*

2012/8/21 Lincoln Ramsay 

> make -C doc qmake




-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Cross compiling Qt 5

2012-08-19 Thread Loaden

I prefer use qbs instead of qmake.
qbs is a great build suite.

2012/8/19 Peter Kümmel 

> Qt could be compiled native or cross for a system
> different to the system on which Qt is build.
>
> But this is not how mkspecs/ is organized:
>
> linux-*native
> win32-*native
> wince* cross
> unsupported/*  cross and native
> device/*   cross
>
> also configure supports different options:
>   -xplatform
>   -device
>   -device-options
>   -sysroot
>
> In short, it is a mess.
>
>
> Couldn't we cleanup this by only having native specs
> in 'mkspecs' and cross specs in 'mkspecs/target'.
>
> A more configure like option would be 'target',
> not 'xplatform' or 'device':
>
> http://airs.com/ian/configure/configure_5.html
>When building cross compilation tools,
>there are two different systems involved:
>the system on which the tools will run,
>and the system for which the tools generate code.
>- The system on which the tools will run is called the host system.
>- The system for which the tools generate code is called the target
> system.
>
> Therefore I propose to cleanup this before the 5.0 release.
>
>
> AFAIK host != "system on which configure runs" is not supported by Qt,
> so we only need 'target' based options.
>
> We need at least these two options:
>   1. specify mkspec name
>   2. specify toolchain prefix
>
> maybe also (
> http://labs.qt.nokia.com/2012/04/13/cross-compiling-qt-for-the-masses/ )
>   3. sysroot
>   4. additional options
>
>
> Here a proposal:
>   1. -target-mkspec  : specify mkspec name
>   2. -target : specify toolchain prefix
>   3. isn't sysroot specified by the toolchain compiler?
>   4. not needed
>
>
> Or are we already in the "wait for 5 + N mode"?
>
> Peter
>
>
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] How to build Qt5's docs?

2012-08-18 Thread Loaden

I want to build Qt5's docs (qch), but failing always.

make docs >>doc.log 2>&1
>

Error Message:

> threed.pro -o Makefile ) && make -f Makefile docs
> make[3]: Entering directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qt3d/src/threed'
> /home/loaden/qpSOFT/Projects/BuildQt5-x64/qtbase/bin/qdoc -installdir
> /home/loaden/qpSOFT/Projects/BuildQt5-x64/qtbase/doc
> /home/loaden/qpSOFT/Projects/Qt5/qt3d/src/threed/doc/qt3d.qdocconf
> /home/loaden/qpSOFT/Projects/Qt5/qt3d/src/threed/doc/qt3d.qdocconf:1:
> error: Cannot open file
> '/home/loaden/qpSOFT/Projects/Qt5/qt3d/src/threed/doc/../../../doc/global/qt-html-templates-offline.qdocconf':
> No such file or directory
> Cannot open file
> '/home/loaden/qpSOFT/Projects/Qt5/qt3d/src/threed/doc/../../../doc/global/qt-html-templates-offline.qdocconf':
> No such file or directory
>
> Aborting
> make[3]: *** [docs] Error 1
> make[3]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qt3d/src/threed'
> make[2]: *** [sub-threed-docs_ordered] Error 2
> make[2]: Leaving directory
> `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qt3d/src'
> make[1]: *** [sub-src-docs] Error 2
> make[1]: Leaving directory `/home/loaden/qpSOFT/Projects/BuildQt5-x64/qt3d'
> make: *** [module-qt3d-docs] Error 2


Why?

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] How about the future of qbs after Nokia sells Qt to Digia?

2012-08-10 Thread Loaden

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!

-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Interest] Digia to acquire Qt from Nokia

2012-08-10 Thread Loaden

Best news! +best wishes!!

2012/8/9 Eric Landuyt 

> Hello ,
>
> seems like a very good news:
>
> http://www.digia.com/en/Home/Company/News/Digia-to-acquire-Qt-from-Nokia/
>
> --
> Eric Landuyt, Developer - mailto:e...@datarescue.be
> DataRescue sa/nv - http://www.datarescue.com
>
> ___
> Interest mailing list
> inter...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] state of Qt's Australia office

2012-07-31 Thread Loaden

Bad news!!

2012/8/1 

>
> On 01/08/2012, at 1:00 PM, "ext lorn.pot...@nokia.com" <
> lorn.pot...@nokia.com>
>  wrote:
>
> > Hi all,
> >
> > We have received word that the Brisbane Australia office, consisting of
> the teams working on Qt3D, QtDeclarative, QtMultimedia, QtSensors, and
> QtSystems modules, as well as the CI/QA team for Qt, will be shut down. Our
> last day is August 31.
>
> Forgot QtLocation. sorry guys.
>
> >
> > The individual developers still retain their status within the Qt
> Project. Whether they choose to remain working on Qt is up to them.
>  Personally, I will continue is possible because I still have
> plans/research I want to do.
> >
> > Except for the CI hardware. which still has employment in the EU.
> >
> >
> >
> > so… anyone hiring?
> >
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Build QtCreator failed use MSVC2010

2012-07-16 Thread Loaden

>
> qmakeevaluator.obj : error LNK2019: unresolved external symbol
> "__declspec(dllimport) public: static
>  class QString __cdecl QString::fromWCharArray(unsigned short const
> *,int)" (__imp_?fromWCharArray@Q
> String@@SA?AV1@PBGH@Z) referenced in function "public: void __thiscall
> QMakeEvaluator::loadDefaults(
> void)" (?loadDefaults@QMakeEvaluator@@QAEXXZ)
> D:\qpSOFT\Projects\QtCreator\build\x86-release\lib\qtcreator\plugins\Nokia\QtSupport.dll
> : fatal err
> or LNK1120: 1 unresolved externals
>

This patch can't solved the problem:


> diff --git a/src/corelib/tools/qstring.h b/src/corelib/tools/qstring.h
> index 2edfc04..249088b 100644
> --- a/src/corelib/tools/qstring.h
> +++ b/src/corelib/tools/qstring.h
> @@ -818,7 +818,7 @@ inline int QString::toWCharArray(wchar_t *array) const
>  }
>  return toUcs4_helper(d->data(), size(), reinterpret_cast *>(array));
>  }
> -inline QString QString::fromWCharArray(const wchar_t *string, int size)
> +Q_CORE_EXPORT inline QString QString::fromWCharArray(const wchar_t
> *string, int size)
>  {
>  return sizeof(wchar_t) == sizeof(QChar) ?
> fromUtf16(reinterpret_cast(string), size)
>  :
> fromUcs4(reinterpret_cast(string), size);
>

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Fixing the DLL/shared/static mess

2012-07-12 Thread Loaden

This changed broken qbs build on Windows (MSVC2010SP1):
96166fa56abb52157387c4911efbd4e5e6beee93
After change CONFIG += staticlib to CONFIG += static (src\lib\lib.pro) still
can't solved the build issue.
Any comments?


> commandexecutor.cpp
> transformer.cpp
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(65)
> : error C2470: 'Exception' : looks like a function definition, but there is
> no parameter list; skipping apparent body
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(72)
> : error C2470: 'UnhandledException' : looks like a function definition, but
> there is no parameter list; skipping apparent body
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(85)
> : error C2061: syntax error : identifier 'Exception'
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(89)
> : error C2143: syntax error : missing ';' before '*'
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(89)
> : error C4430: missing type specifier - int assumed. Note: C++ does not
> support default-int
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(89)
> : error C4430: missing type specifier - int assumed. Note: C++ does not
> support default-int
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(89)
> : warning C4183: 'exception': missing return type; assumed to be a member
> function returning 'int'
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentexception.h(94)
> : error C2470: 'ExceptionStore' : looks like a function definition, but
> there is no parameter list; skipping apparent body
> d:\qpsoft\projects\buildqt5-x86\qtbase\include\qtconcurrent\../../../../Qt5/qtbase/src/concurrent/qtconcurrentresultstore.h(82)
> : error C2470: 'ResultIteratorBase' : looks like a function definition, but
> there is no parameter list; skipping apparent body



2012/4/16 Thiago Macieira 

> On segunda-feira, 16 de abril de 2012 00.44.22, Stephen Kelly wrote:
> > > Static and shared in one build has never been supported.
> >
> > But you want to make it supported in one package? Has that been possible
> > before?
>
> Not right now. It's extremely unlikely we'll modify qmake to support it.
> But
> this might be possible in a new buildsystem.
>
> Either way, the point is that you might have two builds making one
> installation.
>
> > > It's far more likely that CMake and other buildsystems can accomplish
> > > this,
> > > even if qmake can't. In order to do that, we need to have a sane
> qconfig.h
> > > and export macros. That's what this proposal is about.
> >
> > Right. I might have to have another closer look at the proposal tomorrow
> > then. A solution that works for qmake can probably be adapted anyway, as
> > you note.
>
>  --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>  Intel Sweden AB - Registration Number: 556189-6027
>  Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 beta, MinGW: undefined reference to `WinMain@16'

2012-07-11 Thread Loaden

Try to build qbs or qbs's test demos.
Not build Qt5 self, but build an GUI based applications.

2012/7/12 Konstantin Ritt 

> E:\opt\Qt\5.0>gcc --version
> gcc (GCC) 4.6.2
> win32 (XP, SP2)
> builds ok
>
> Konstantin
>
>
> 2012/7/11 Loaden :
> > Both w32 and w64 have the same issue, MinGW 4.6.3. (platform: Ubuntu and
> > Windows).
> > B.T.W I can't build Qt5 use MinGW 4.7.1 under Windows, but MinGW 4.6.3
> can
> > build successful, except install failed.
> >
> > 2012/7/11 
> >
> >> Hi,
> >>
> >> Which GCC is this (both for w32 and w64)? For KDE I tried to use 4.6.4
> and
> >> we are having a lot of problems with that, so we are now waiting for a
> >> patched GCC 4.7.x
> >>
> >> Casper
> >>
> >> From: ext Loaden 
> >> Date: Wednesday, July 11, 2012 3:52 PM
> >> To: "shane.kea...@accenture.com" 
> >> Cc: "development@qt-project.org" 
> >> Subject: Re: [Development] Qt5 beta, MinGW: undefined reference to
> >> `WinMain@16'
> >>
> >> Does anyone care about mingw support?
> >> It's an qt5 issue, or an mingw issue?
> >> I don't sure anything, but it's real noise!
> >> Because I can't corss build for Windows use Qt5 now.
> >>
> >>
> >>
> http://sourceforge.net/tracker/?func=detail&atid=983354&aid=3539247&group_id=202880
> >>
> >> 2012/7/6 Loaden 
> >>>
> >>> I just create a bug report, and hope someone can take of.
> >>> It's only Qt5 issue, Qt4 works well!!
> >>>
> >>> 2012/7/5 Loaden 
> >>>>
> >>>> Yes, same problem happened when using qmake.
> >>>> for qbs, I made a patch for link to static library, see:
> >>>> https://codereview.qt-project.org/#change,29232
> >>>>
> >>>> 2012/7/5 
> >>>>
> >>>>> Does the same problem happen if using qmake instead of qbs?
> >>>>>
> >>>>> There is a qtmain.lib static library that should be added
> automatically
> >>>>> to windows executables, which provides the WinMain entry point.
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: development-bounces+shane.kearns=accenture@qt-project.org
> >>>>> [mailto:development-bounces+shane.kearns=
> accenture@qt-project.org] On
> >>>>> Behalf Of Loaden
> >>>>> Sent: 05 July 2012 04:15
> >>>>> To: development
> >>>>> Subject: [Development] Qt5 beta, MinGW: undefined reference to
> >>>>> `WinMain@16'
> >>>>>
> >>>>>
> >>>>>
> >>>>> main.cpp
> >>>>>
> >>>>> #include 
> >>>>>
> >>>>> int main(int argc, char **argv)
> >>>>> {
> >>>>> QCoreApplication app(argc, argv);
> >>>>> return app.exec();
> >>>>> }
> >>>>>
> >>>>> test.qbp
> >>>>>
> >>>>> import qbs.base 1.0
> >>>>>
> >>>>> Application {
> >>>>> name : "Test"
> >>>>>
> >>>>> Depends {
> >>>>> name: "Qt.widgets"
> >>>>> }
> >>>>>
> >>>>> files : [
> >>>>> "main.cpp"
> >>>>> ]
> >>>>> }
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>  MinGW-TDM32:
> >>>>>
> >>>>>
> >>>>>
> >>>>> Found project file D:\qpSOFT\Projects\Test\test.qbp
> >>>>> loading project took:  79 ms
> >>>>> build graph took:  14 ms
> >>>>> for t86-tdm-mingw32-release:
> >>>>>   - [hpp, application] Test as t86-tdm-mingw32-release
> >>>>>
> >>>>> compiling main.cpp
> >>>>> linking Test.exe
> >>>>> D:\qpSOFT\MinGW\TDM-MinGW32\bin/g++ -O2 -Wall -W
> >>>>> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-relea
> >>>>> s

Re: [Development] Qt5 beta, MinGW: undefined reference to `WinMain@16'

2012-07-11 Thread Loaden

Both w32 and w64 have the same issue, MinGW 4.6.3. (platform: Ubuntu and
Windows).
B.T.W I can't build Qt5 use MinGW 4.7.1 under Windows, but MinGW 4.6.3 can
build successful, except install failed.

2012/7/11 

>  Hi,
>
>  Which GCC is this (both for w32 and w64)? For KDE I tried to use 4.6.4
> and we are having a lot of problems with that, so we are now waiting for a
> patched GCC 4.7.x
>
>  Casper
>
>   From: ext Loaden 
> Date: Wednesday, July 11, 2012 3:52 PM
> To: "shane.kea...@accenture.com" 
> Cc: "development@qt-project.org" 
> Subject: Re: [Development] Qt5 beta, MinGW: undefined reference to
> `WinMain@16'
>
>  Does anyone care about mingw support?
> It's an qt5 issue, or an mingw issue?
> I don't sure anything, but it's real noise!
> Because I can't corss build for Windows use Qt5 now.
>
>
> http://sourceforge.net/tracker/?func=detail&atid=983354&aid=3539247&group_id=202880
>
> 2012/7/6 Loaden 
>
>> I just create a bug report, and hope someone can take of.
>> It's only Qt5 issue, Qt4 works well!!
>>
>>   2012/7/5 Loaden 
>>
>>> Yes, same problem happened when using qmake.
>>> for qbs, I made a patch for link to static library, see:
>>> https://codereview.qt-project.org/#change,29232
>>>
>>>  2012/7/5 
>>>
>>>   Does the same problem happen if using qmake instead of qbs?
>>>>
>>>> There is a qtmain.lib static library that should be added automatically
>>>> to windows executables, which provides the WinMain entry point.
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>>
>>>> *From:* 
>>>> development-bounces+shane.kearns=accenture@qt-project.org[mailto:
>>>> development-bounces+shane.kearns=accenture@qt-project.org] *On
>>>> Behalf Of *Loaden
>>>> *Sent:* 05 July 2012 04:15
>>>> *To:* development
>>>> *Subject:* [Development] Qt5 beta, MinGW: undefined reference to
>>>> `WinMain@16'
>>>>
>>>>
>>>>
>>>> main.cpp
>>>>
>>>> #include 
>>>>
>>>> int main(int argc, char **argv)
>>>> {
>>>> QCoreApplication app(argc, argv);
>>>> return app.exec();
>>>> }
>>>>
>>>>   test.qbp
>>>>
>>>>  import qbs.base 1.0
>>>>
>>>> Application {
>>>> name : "Test"
>>>>
>>>> Depends {
>>>> name: "Qt.widgets"
>>>> }
>>>>
>>>> files : [
>>>> "main.cpp"
>>>> ]
>>>> }
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>  MinGW-TDM32:
>>>>
>>>>
>>>>
>>>>  Found project file D:\qpSOFT\Projects\Test\test.qbp
>>>> loading project took:  79 ms
>>>> build graph took:  14 ms
>>>> for t86-tdm-mingw32-release:
>>>>   - [hpp, application] Test as t86-tdm-mingw32-release
>>>>
>>>> compiling main.cpp
>>>> linking Test.exe
>>>> D:\qpSOFT\MinGW\TDM-MinGW32\bin/g++ -O2 -Wall -W
>>>> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-relea
>>>> se/.obj/Test/main.o -o
>>>> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-release/Test.exe
>>>> -LD:/qpSOFT/Pr
>>>> ojects/BuildQt5-t86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>>>> d:/qpsoft/mingw/tdm-mingw32/bin/../lib/gcc/mingw32/4.6.1/../../../libmingw32.a(main.o):
>>>> In function
>>>> `main':
>>>> *C:\MinGW\msys\1.0\src\mingwrt/../mingw/main.c:73: undefined reference
>>>> to **`WinMain@16'* <%60WinMain@16%27>
>>>> collect2: ld returned 1 exit status
>>>>
>>>>
>>>>
>>>> MinGW-w64
>>>>
>>>>
>>>>
>>>>  D:\qpSOFT\MinGW\MinGW32\bin/g++ -m32 -O2 -Wall -W
>>>> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/
>>>> .obj/Test/main.o -o
>>>> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/Test.exe
>>>> -LD:/qpSOFT/Projects/
>>>> BuildQt5-m86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>>>>
>>>> d:/qpsoft/mingw/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../i686-w64-mingw32/lib/../li
>>>> b/libmingw32.a(lib32_libmingw32_a-crt0_c.o): In function `main':
>>>> */home/ruben/mingw-w64/toolchain/src/mingw-w64/tags/v2.0.3/mingw-w64-crt/crt/crt0_c.c:18:
>>>> undefined r**
>>>> eference to **`WinMain@16'* <%60WinMain@16%27>
>>>> collect2: ld returned 1 exit status
>>>>
>>>>   --
>>>>
>>>>
>>>>
>>>> Please don't ask where I come from, It's a shame!
>>>>
>>>> Best Regards
>>>>
>>>> Yuchen
>>>>
>>>>
>>>>
>>>> --
>>>> Subject to local law, communications with Accenture and its affiliates
>>>> including telephone calls and emails (including content), may be monitored
>>>> by our systems for the purposes of security and the assessment of internal
>>>> compliance with Accenture policy.
>>>>
>>>> __
>>>>
>>>> www.accenture.com
>>>>
>>>
>>>
>>>
>>> --
>>> Please don't ask where I come from, It's a shame!
>>> Best Regards
>>> Yuchen
>>>
>>>
>>
>>
>> --
>> Please don't ask where I come from, It's a shame!
>> Best Regards
>> Yuchen
>>
>>
>
>
> --
> Please don't ask where I come from, It's a shame!
> Best Regards
> Yuchen
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 beta, MinGW: undefined reference to `WinMain@16'

2012-07-11 Thread Loaden

Does anyone care about mingw support?
It's an qt5 issue, or an mingw issue?
I don't sure anything, but it's real noise!
Because I can't corss build for Windows use Qt5 now.

http://sourceforge.net/tracker/?func=detail&atid=983354&aid=3539247&group_id=202880

2012/7/6 Loaden 

> I just create a bug report, and hope someone can take of.
> It's only Qt5 issue, Qt4 works well!!
>
> 2012/7/5 Loaden 
>
>> Yes, same problem happened when using qmake.
>> for qbs, I made a patch for link to static library, see:
>> https://codereview.qt-project.org/#change,29232
>>
>> 2012/7/5 
>>
>>   Does the same problem happen if using qmake instead of qbs?
>>>
>>> There is a qtmain.lib static library that should be added automatically
>>> to windows executables, which provides the WinMain entry point.
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> *From:* 
>>> development-bounces+shane.kearns=accenture@qt-project.org[mailto:
>>> development-bounces+shane.kearns=accenture@qt-project.org] *On
>>> Behalf Of *Loaden
>>> *Sent:* 05 July 2012 04:15
>>> *To:* development
>>> *Subject:* [Development] Qt5 beta, MinGW: undefined reference to
>>> `WinMain@16'
>>>
>>>
>>>
>>> main.cpp
>>>
>>> #include 
>>>
>>> int main(int argc, char **argv)
>>> {
>>> QCoreApplication app(argc, argv);
>>> return app.exec();
>>> }
>>>
>>>  test.qbp
>>>
>>>  import qbs.base 1.0
>>>
>>> Application {
>>> name : "Test"
>>>
>>> Depends {
>>> name: "Qt.widgets"
>>> }
>>>
>>> files : [
>>> "main.cpp"
>>> ]
>>> }
>>>
>>>
>>>
>>>
>>>
>>>  MinGW-TDM32:
>>>
>>>
>>>
>>>  Found project file D:\qpSOFT\Projects\Test\test.qbp
>>> loading project took:  79 ms
>>> build graph took:  14 ms
>>> for t86-tdm-mingw32-release:
>>>   - [hpp, application] Test as t86-tdm-mingw32-release
>>>
>>> compiling main.cpp
>>> linking Test.exe
>>> D:\qpSOFT\MinGW\TDM-MinGW32\bin/g++ -O2 -Wall -W
>>> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-relea
>>> se/.obj/Test/main.o -o
>>> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-release/Test.exe
>>> -LD:/qpSOFT/Pr
>>> ojects/BuildQt5-t86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>>> d:/qpsoft/mingw/tdm-mingw32/bin/../lib/gcc/mingw32/4.6.1/../../../libmingw32.a(main.o):
>>> In function
>>> `main':
>>> *C:\MinGW\msys\1.0\src\mingwrt/../mingw/main.c:73: undefined reference
>>> to **`WinMain@16'* <%60WinMain@16%27>
>>> collect2: ld returned 1 exit status
>>>
>>>
>>>
>>> MinGW-w64
>>>
>>>
>>>
>>>  D:\qpSOFT\MinGW\MinGW32\bin/g++ -m32 -O2 -Wall -W
>>> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/
>>> .obj/Test/main.o -o
>>> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/Test.exe
>>> -LD:/qpSOFT/Projects/
>>> BuildQt5-m86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>>>
>>> d:/qpsoft/mingw/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../i686-w64-mingw32/lib/../li
>>> b/libmingw32.a(lib32_libmingw32_a-crt0_c.o): In function `main':
>>> */home/ruben/mingw-w64/toolchain/src/mingw-w64/tags/v2.0.3/mingw-w64-crt/crt/crt0_c.c:18:
>>> undefined r**
>>> eference to **`WinMain@16'* <%60WinMain@16%27>
>>> collect2: ld returned 1 exit status
>>>
>>>  --
>>>
>>>
>>>
>>> Please don't ask where I come from, It's a shame!
>>>
>>> Best Regards
>>>
>>> Yuchen
>>>
>>>
>>>
>>> --
>>> Subject to local law, communications with Accenture and its affiliates
>>> including telephone calls and emails (including content), may be monitored
>>> by our systems for the purposes of security and the assessment of internal
>>> compliance with Accenture policy.
>>>
>>> __
>>>
>>> www.accenture.com
>>>
>>
>>
>>
>> --
>> Please don't ask where I come from, It's a shame!
>> Best Regards
>> Yuchen
>>
>>
>
>
> --
> Please don't ask where I come from, It's a shame!
> Best Regards
> Yuchen
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 beta, MinGW: undefined reference to `WinMain@16'

2012-07-06 Thread Loaden

I just create a bug report, and hope someone can take of.
It's only Qt5 issue, Qt4 works well!!

2012/7/5 Loaden 

> Yes, same problem happened when using qmake.
> for qbs, I made a patch for link to static library, see:
> https://codereview.qt-project.org/#change,29232
>
> 2012/7/5 
>
>   Does the same problem happen if using qmake instead of qbs?
>>
>> There is a qtmain.lib static library that should be added automatically
>> to windows executables, which provides the WinMain entry point.
>>
>>
>>
>> --
>>
>>
>>
>> *From:* development-bounces+shane.kearns=accenture@qt-project.org[mailto:
>> development-bounces+shane.kearns=accenture@qt-project.org] *On
>> Behalf Of *Loaden
>> *Sent:* 05 July 2012 04:15
>> *To:* development
>> *Subject:* [Development] Qt5 beta, MinGW: undefined reference to
>> `WinMain@16'
>>
>>
>>
>> main.cpp
>>
>> #include 
>>
>> int main(int argc, char **argv)
>> {
>> QCoreApplication app(argc, argv);
>> return app.exec();
>> }
>>
>>  test.qbp
>>
>>  import qbs.base 1.0
>>
>> Application {
>> name : "Test"
>>
>> Depends {
>> name: "Qt.widgets"
>> }
>>
>> files : [
>> "main.cpp"
>> ]
>> }
>>
>>
>>
>>
>>
>>  MinGW-TDM32:
>>
>>
>>
>>  Found project file D:\qpSOFT\Projects\Test\test.qbp
>> loading project took:  79 ms
>> build graph took:  14 ms
>> for t86-tdm-mingw32-release:
>>   - [hpp, application] Test as t86-tdm-mingw32-release
>>
>> compiling main.cpp
>> linking Test.exe
>> D:\qpSOFT\MinGW\TDM-MinGW32\bin/g++ -O2 -Wall -W
>> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-relea
>> se/.obj/Test/main.o -o
>> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-release/Test.exe
>> -LD:/qpSOFT/Pr
>> ojects/BuildQt5-t86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>> d:/qpsoft/mingw/tdm-mingw32/bin/../lib/gcc/mingw32/4.6.1/../../../libmingw32.a(main.o):
>> In function
>> `main':
>> *C:\MinGW\msys\1.0\src\mingwrt/../mingw/main.c:73: undefined reference
>> to **`WinMain@16'* <%60WinMain@16'>
>> collect2: ld returned 1 exit status
>>
>>
>>
>> MinGW-w64
>>
>>
>>
>>  D:\qpSOFT\MinGW\MinGW32\bin/g++ -m32 -O2 -Wall -W
>> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/
>> .obj/Test/main.o -o
>> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/Test.exe
>> -LD:/qpSOFT/Projects/
>> BuildQt5-m86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>>
>> d:/qpsoft/mingw/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../i686-w64-mingw32/lib/../li
>> b/libmingw32.a(lib32_libmingw32_a-crt0_c.o): In function `main':
>> */home/ruben/mingw-w64/toolchain/src/mingw-w64/tags/v2.0.3/mingw-w64-crt/crt/crt0_c.c:18:
>> undefined r**
>> eference to **`WinMain@16'* <%60WinMain@16'>
>> collect2: ld returned 1 exit status
>>
>>  --
>>
>>
>>
>> Please don't ask where I come from, It's a shame!
>>
>> Best Regards
>>
>> Yuchen
>>
>>
>>
>> --
>> Subject to local law, communications with Accenture and its affiliates
>> including telephone calls and emails (including content), may be monitored
>> by our systems for the purposes of security and the assessment of internal
>> compliance with Accenture policy.
>>
>> __
>>
>> www.accenture.com
>>
>
>
>
> --
> Please don't ask where I come from, It's a shame!
> Best Regards
> Yuchen
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 beta, MinGW: undefined reference to `WinMain@16'

2012-07-05 Thread Loaden

Yes, same problem happened when using qmake.
for qbs, I made a patch for link to static library, see:
https://codereview.qt-project.org/#change,29232

2012/7/5 

>  Does the same problem happen if using qmake instead of qbs?
>
> There is a qtmain.lib static library that should be added automatically to
> windows executables, which provides the WinMain entry point.
>
>
>
> --
>
>
>
> *From:* development-bounces+shane.kearns=accenture@qt-project.org[mailto:
> development-bounces+shane.kearns=accenture@qt-project.org] *On Behalf
> Of *Loaden
> *Sent:* 05 July 2012 04:15
> *To:* development
> *Subject:* [Development] Qt5 beta, MinGW: undefined reference to
> `WinMain@16'
>
>
>
> main.cpp
>
> #include 
>
> int main(int argc, char **argv)
> {
> QCoreApplication app(argc, argv);
> return app.exec();
> }
>
>  test.qbp
>
>  import qbs.base 1.0
>
> Application {
> name : "Test"
>
> Depends {
> name: "Qt.widgets"
> }
>
> files : [
> "main.cpp"
> ]
> }
>
>
>
>
>
>  MinGW-TDM32:
>
>
>
>  Found project file D:\qpSOFT\Projects\Test\test.qbp
> loading project took:  79 ms
> build graph took:  14 ms
> for t86-tdm-mingw32-release:
>   - [hpp, application] Test as t86-tdm-mingw32-release
>
> compiling main.cpp
> linking Test.exe
> D:\qpSOFT\MinGW\TDM-MinGW32\bin/g++ -O2 -Wall -W
> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-relea
> se/.obj/Test/main.o -o
> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-release/Test.exe
> -LD:/qpSOFT/Pr
> ojects/BuildQt5-t86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
> d:/qpsoft/mingw/tdm-mingw32/bin/../lib/gcc/mingw32/4.6.1/../../../libmingw32.a(main.o):
> In function
> `main':
> *C:\MinGW\msys\1.0\src\mingwrt/../mingw/main.c:73: undefined reference to
> **`WinMain@16'* <%60WinMain@16'>
> collect2: ld returned 1 exit status
>
>
>
> MinGW-w64
>
>
>
>  D:\qpSOFT\MinGW\MinGW32\bin/g++ -m32 -O2 -Wall -W
> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/
> .obj/Test/main.o -o
> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/Test.exe
> -LD:/qpSOFT/Projects/
> BuildQt5-m86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>
> d:/qpsoft/mingw/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../i686-w64-mingw32/lib/../li
> b/libmingw32.a(lib32_libmingw32_a-crt0_c.o): In function `main':
> */home/ruben/mingw-w64/toolchain/src/mingw-w64/tags/v2.0.3/mingw-w64-crt/crt/crt0_c.c:18:
> undefined r**
> eference to **`WinMain@16'* <%60WinMain@16'>
> collect2: ld returned 1 exit status
>
>  --
>
>
>
> Please don't ask where I come from, It's a shame!
>
> Best Regards
>
> Yuchen
>
>
>
> --
> Subject to local law, communications with Accenture and its affiliates
> including telephone calls and emails (including content), may be monitored
> by our systems for the purposes of security and the assessment of internal
> compliance with Accenture policy.
>
> __
>
> www.accenture.com
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt5 beta, MinGW: undefined reference to `WinMain@16'

2012-07-04 Thread Loaden

main.cpp

> #include 
> int main(int argc, char **argv)
> {
> QCoreApplication app(argc, argv);
> return app.exec();
> }
>
> test.qbp

>  import qbs.base 1.0
> Application {
> name : "Test"
> Depends {
> name: "Qt.widgets"
> }
> files : [
> "main.cpp"
> ]
> }
>


 MinGW-TDM32:


> Found project file D:\qpSOFT\Projects\Test\test.qbp
> loading project took:  79 ms
> build graph took:  14 ms
> for t86-tdm-mingw32-release:
>   - [hpp, application] Test as t86-tdm-mingw32-release
> compiling main.cpp
> linking Test.exe
> D:\qpSOFT\MinGW\TDM-MinGW32\bin/g++ -O2 -Wall -W
> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-relea
> se/.obj/Test/main.o -o
> D:/qpSOFT/Projects/Test/build/t86-tdm-mingw32-release/Test.exe
> -LD:/qpSOFT/Pr
> ojects/BuildQt5-t86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
> d:/qpsoft/mingw/tdm-mingw32/bin/../lib/gcc/mingw32/4.6.1/../../../libmingw32.a(main.o):
> In function
> `main':
> *C:\MinGW\msys\1.0\src\mingwrt/../mingw/main.c:73: undefined reference to
> **`WinMain@16'* <%60WinMain@16'>
> collect2: ld returned 1 exit status
>

MinGW-w64


> D:\qpSOFT\MinGW\MinGW32\bin/g++ -m32 -O2 -Wall -W
> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/
> .obj/Test/main.o -o
> D:/qpSOFT/Projects/Test/build/m86-mingw32-release/Test.exe
> -LD:/qpSOFT/Projects/
> BuildQt5-m86/qtbase/lib -lqtmain -lQtCore5 -lQtGui5 -lQtWidgets5
>
> d:/qpsoft/mingw/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../i686-w64-mingw32/lib/../li
> b/libmingw32.a(lib32_libmingw32_a-crt0_c.o): In function `main':
> */home/ruben/mingw-w64/toolchain/src/mingw-w64/tags/v2.0.3/mingw-w64-crt/crt/crt0_c.c:18:
> undefined r
> eference to **`WinMain@16'* <%60WinMain@16'>
> collect2: ld returned 1 exit status
>
 --
>

Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] buildsystem branches (about to be) integrated

2012-07-01 Thread Loaden

Still can't build on Windows + MinGW-w64.
QtWidgets: created headers.pri file
QtTest: created fwd-include header(s) for /src/testlib/ {
qabstracttestlogger_p.h (1), qbenchmark.h (1), qbenchmark_p.h (1),
qbenchmarkevent_p.h (1), qbenchmarkmeasurement_p.h (1), qbenchmarkmetric.h
(1), qbenchmarkmetric_p.h (1), qbenchmarkvalgrind_p.h (1),
qplaintestlogger_p.h (1), qsignaldumper_p.h (1), qsignalspy.h (2), qtest.h
(2), qtest_global.h (1), qtest_gui.h (2), qtest_widgets.h (2),
qtestaccessible.h (2), qtestassert.h (1), qtestcase.h (1),
qtestcoreelement_p.h (1), qtestcorelist_p.h (1), qtestdata.h (2),
qtestelement_p.h (1), qtestelementattribute_p.h (1), qtestevent.h (7),
qtesteventloop.h (2), qtestkeyboard.h (1), qtestlog_p.h (1), qtestmouse.h
(1), qtestresult_p.h (1), qtestspontaneevent.h (3), qtestsystem.h (1),
qtesttable_p.h (1), qtesttouch.h (1), qtestxunitstreamer_p.h (1),
qxmltestlogger_p.h (1), qxunittestlogger_p.h (1) }
QtTest: created fwd-include header(s) for /src/testlib/ {
qttestversion.h (2) }
QtTest: created fwd-include header(s) for /src/testlib/3rdparty/ {
callgrind_p.h (1), cycle_p.h (1), valgrind_p.h (1) }
QtTest: created headers.pri file
QtDBus: created fwd-include header(s) for /src/dbus/ {
qdbus_symbols_p.h (1), qdbusabstractadaptor.h (2), qdbusabstractadaptor_p.h
(1), qdbusabstractinterface.h (3), qdbusabstractinterface_p.h (1),
qdbusargument.h (2), qdbusargument_p.h (1), qdbusconnection.h (2),
qdbusconnection_p.h (1), qdbusconnectioninterface.h (2),
qdbusconnectionmanager_p.h (1), qdbuscontext.h (2), qdbuscontext_p.h (1),
qdbuserror.h (2), qdbusextratypes.h (4), qdbusintegrator_p.h (1),
qdbusinterface.h (2), qdbusinterface_p.h (1), qdbusintrospection_p.h (1),
qdbusmacros.h (1), qdbusmessage.h (2), qdbusmessage_p.h (1),
qdbusmetaobject_p.h (1), qdbusmetatype.h (2), qdbusmetatype_p.h (1),
qdbuspendingcall.h (3), qdbuspendingcall_p.h (1), qdbuspendingreply.h (3),
qdbusreply.h (2), qdbusserver.h (2), qdbusservicewatcher.h (2),
qdbusthreaddebug_p.h (1), qdbusunixfiledescriptor.h (2), qdbusutil_p.h (1),
qdbusvirtualobject.h (2), qdbusxmlparser_p.h (1) }
QtDBus: created fwd-include header(s) for /src/dbus/ {
qtdbusversion.h (2) }
QtDBus: created headers.pri file

> g++ -x c++-header -c -fno-rtti -fno-exceptions -mthreads -Wall -Wextra
> -DUNICODE -DQT_NO_DATASTREAM -DQT_NO_CODECS -DQT_NO_TEXTCODEC
> -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_COMPRESS -DQT_NO_THREAD
> -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -D_CRT_SECURE_NO_DEPRECATE
> -DQT_BOOTSTRAPPED -DCOMMERCIAL_VERSION -I"../../include"
> -I"../../include/QtCore" -I"../../include/QtCore/5.0.0"
> -I"../../include/QtCore/5.0.0/QtCore"
> -I"D:/qpSOFT/Projects/Qt5/qtbase/tools/shared"
> -I"D:/qpSOFT/Projects/Qt5/qtbase/mkspecs/win32-g++" -o
> configure_pch.h.gch/c++
> D:/qpSOFT/Projects/Qt5/qtbase/tools/configure/configure_pch.h
> g++ -include configure_pch.h -fno-rtti -fno-exceptions -mthreads -Wall
> -Wextra -DUNICODE -DQT_NO_DATASTREAM -DQT_NO_CODECS -DQT_NO_TEXTCODEC
> -DQT_NO_UNICODETABLES -DQT_LITE_COMPONENT -DQT_NO_COMPRESS -DQT_NO_THREAD
> -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -D_CRT_SECURE_NO_DEPRECATE
> -DQT_BOOTSTRAPPED -DCOMMERCIAL_VERSION -I"../../include"
> -I"../../include/QtCore" -I"../../include/QtCore/5.0.0"
> -I"../../include/QtCore/5.0.0/QtCore"
> -I"D:/qpSOFT/Projects/Qt5/qtbase/tools/shared"
> -I"D:/qpSOFT/Projects/Qt5/qtbase/mkspecs/win32-g++"   -c -o
> qsystemlibrary.o
> /qpSOFT/Projects/Qt5/qtbase/src/corelib/plugin/qsystemlibrary.cpp
> g++.exe: error: *D:/Program 
> Files/Git/qpSOFT/Projects/Qt5*/qtbase/src/corelib/plugin/qsystemlibrary.cpp:
> No such file or directory
> g++.exe: fatal error: no input files
> compilation terminated.
> mingw32-make: *** [qsystemlibrary.o] Error 1
> *** qtbase/configure exited with non-zero status.
>

*D:/Program Files/Git/qpSOFT/Projects/Qt5*
*It should be:*
*D:/qpSOFT/Projects/Qt5*
2012/7/1 Loaden 

> I can cross build use wingw-w64 now, but still have a problem.
> the: lrelease.exe lupdate.exe and xmlpatterns.exe 's host platform should
> be Linux, not Windows.
> Just like jom and qmake, It's should be: lrelease lupdate and xmlpatterns
> Thanks! great work!!
>
>
> 2012/6/19 Oswald Buddenhagen 
>
>> moin,
>>
>> the buildsystem branch of qtbase is currently being integrated. this is
>> ~120 commits worth of qmake & project file fixes and cleanups. there are
>> some changes to how modularization (in particular configure tests) is
>> handled, and cross-building should be supported without hacks finally.
>>
>> the immediate impact:
>> - lots of build scripts which employ various hacks will instantly
>>   break. don't panic and (mostly) just delete some code from them.
>>

Re: [Development] buildsystem branches (about to be) integrated

2012-06-30 Thread Loaden

I can cross build use wingw-w64 now, but still have a problem.
the: lrelease.exe lupdate.exe and xmlpatterns.exe 's host platform should
be Linux, not Windows.
Just like jom and qmake, It's should be: lrelease lupdate and xmlpatterns
Thanks! great work!!

2012/6/19 Oswald Buddenhagen 

> moin,
>
> the buildsystem branch of qtbase is currently being integrated. this is
> ~120 commits worth of qmake & project file fixes and cleanups. there are
> some changes to how modularization (in particular configure tests) is
> handled, and cross-building should be supported without hacks finally.
>
> the immediate impact:
> - lots of build scripts which employ various hacks will instantly
>   break. don't panic and (mostly) just delete some code from them.
>   use
>   configure -xplatform  -sysroot 
>   make
>   as you would intuitively expect. don't play tricks with funny qmake
>   and make invocations.
> - the other modules will spit out lots of warnings now.
>   *DON'T* do anything about them for now. i have patches prepared for
>   all modules already. i will explicitly add the module owners to the
>   reviews. *don't* stage anything yourself.
>   once my patches are through, there will be still some warnings left.
>   you'll be invited to fix them at this point.
> - some build configurations will work even worse than before until
>   everything is integrated. the only variants which are expected to be
>   safe are developer builds without -prefix and module-by-module builds
>   with -prefix.
>
> catch me on IRC if something breaks for you and no obvious solution
> seems to help. but remember that not every breakage is due to this
> branch being integrated. ;)
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [QBS] "qbs platforms ls" show nothing, "qbs-platforms ls" works well!

2012-06-27 Thread Loaden

Yes, that what's I mean. and I use *MSVC2010SP1 (from Windows SDK 7.1 +
VCSP1_update)*, on Windows 7 SP1 x64 or Windows 7 SP1 x86 both has the
problem.

2012/6/27 Joerg Bornemann 

> On 26/06/2012 01:37, ext Loaden wrote:
>
>  Of cause, It's only Qt5 issue. and only happened on Windows. (As I know
>> on Linux everything works well)
>> See:
>>
> [...]
>
>  If re-direct to some log, like this: "qbs platforms ls > output.log &&
>> output.log", Then you can see what you want.
>> Any comments?
>>
>
> So you mean in Qt5 QProcess:execute does not forward the output of the
> process on Windows? I can't reproduce this issue with Qt5 and MSVC2008.
>
>
> BR,
>
> Jörg
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] "qbs platforms ls" show nothing, "qbs-platforms ls" works well!

2012-06-25 Thread Loaden

Of cause, It's only Qt5 issue. and only happened on Windows. (As I know on
Linux everything works well)
See:

> const QString subProcess = subProcessArgs.takeFirst();
> if (!subProcess.startsWith('-')) {
> *const int exitCode = QProcess::execute("qbs-" + subProcess,
> subProcessArgs);
> *if (exitCode != -2)
> return exitCode;
> }
>

If re-direct to some log, like this: "qbs platforms ls > output.log &&
output.log", Then you can see what you want.
Any comments?

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] It should be a moc error for the specified file to not exist.

2012-06-23 Thread Loaden

See: 6649171ddc2b7cfa93f9f38169cb307f3289dc85

Author: Stephen Kelly   2012-06-14 01:31:18
> Committer: Qt by Nokia   2012-06-14 16:11:24
> Parent: 6da6845f078e419ccb555fe1dd152e0ba82a7e88 (Disable hinting for
> scaled glyphs in FreeType)
> Child:  a85d15259ce2ce9371ad832bdd7becf256362c20 (Fix
> QListView::scrollTo() when there are hidden rows)
> Branches: master, remotes/origin/buildsystem, remotes/origin/master
> Follows: qt-v5.0.0-alpha1
> Precedes:
>
> It should be a moc error for the specified file to not exist.
>
> Currently the missing file is ignored and plugin data is created
> anyway.
>
> Change-Id: I118fd57b7d05a135e3ff58c0298b25e67cd12587
> Reviewed-by: Lars Knoll 
>

It's broken build of QtCreator.

> /home/loaden/qpSOFT/Projects/QtCreator/src/plugins/coreplugin/coreplugin.h:48:
> Error: Plugin Metadata file "Core.json" does not exist. Declaration will be
> ignored
>
> ERROR: Process failed with exit code 1.

Any comments are welcome!

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Creator build failed of latest Qt5

2012-06-19 Thread Loaden

>
> D:\qpSOFT\MyDEV\sdk\qt\bin\amd64\moc.exe -DUNICODE -DWIN32
> -DQT_LARGEFILE_SUPPORT -DCORE_LIBRARY -DIDE_LIBRARY_BASENAME=\"lib\"
> -DQT_NO_CAST_TO_ASCII -DQT_USE_FAST_OPERATOR_PLUS
> -DQT_USE_FAST_CONCATENATION -D_CRT_SECURE_NO_WARNINGS
> -DQT_DISABLE_DEPRECATED_BEFORE=0x040900 -DQT_HELP_LIB -DQT_DLL
> -DQT_NO_DEBUG -DQT_PLUGIN -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB
> -DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_SCRIPT_LIB -DQT_NETWORK_LIB
> -DQT_GUI_LIB -DQT_CORE_LIB -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtCore"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtGui\5.0.0"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtGui\5.0.0\QtGui"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtGui"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtNetwork"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtScript"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtSql"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtConcurrent"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtWidgets"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtPrintSupport"
> -I"..\..\..\..\..\MyDEV\sdk\qt\include\QtHelp" -I"..\..\..\src"
> -I"..\..\..\..\QtCreator\src\libs" -I"d:\qpSOFT\Projects\QtCreator\tools"
> -I"..\..\..\..\QtCreator\src\plugins"
> -I"..\..\..\..\QtCreator\src\shared\scriptwrapper"
> -I"..\..\..\..\QtCreator\src\plugins\coreplugin\dialogs"
> -I"..\..\..\..\QtCreator\src\plugins\coreplugin\actionmanager"
> -I"..\..\..\..\QtCreator\src\plugins\coreplugin\editormanager"
> -I"..\..\..\..\QtCreator\src\plugins\coreplugin\progressmanager"
> -I"..\..\..\..\QtCreator\src\plugins\coreplugin\scriptmanager" -I"release"
> -I"." -I"..\..\..\..\QtCreator\src\plugins\coreplugin" -I"."
> -I"..\..\..\..\..\MyDEV\sdk\qt\mkspecs\win32-msvc2010" -D_MSC_VER=1600
> -DWIN32 ..\..\..\..\QtCreator\src\plugins\coreplugin\coreplugin.h -o
> release\moc_coreplugin.cpp
> *..\..\..\..\QtCreator\src\plugins\coreplugin\coreplugin.h(48): Error:
> Plugin Metadata file "Core.json" does not exist. Declaration will be ignored
> *NMAKE : fatal error U1077: 'D:\qpSOFT\MyDEV\sdk\qt\bin\amd64\moc.exe' :
> return code '0x1'
> Stop.
> NMAKE : fatal error U1077: 'D:\qpSOFT\MyDEV\bin\amd64\nmake.exe' : return
> code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.


But qbs can't catch the useful error information:
*coreplugin.h(48): Error: Plugin Metadata file "Core.json" does not exist.
Declaration will be ignored*

> ils -o
> D:/qpSOFT/Projects/QtCreator/build/x64-release/GeneratedFiles/Core/moc_coreplugin.cpp
> D:/qpSO
> FT/Projects/QtCreator/src/plugins/coreplugin/coreplugin.h
> ERROR: Process failed with exit code 1.
> ERROR: The following products could not be built: qtcreator,
> QmlEditorWidgets, GenericProjectManager


Any comments?

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] True death of Nokia's Qt? How about Qt's future?

2012-06-15 Thread Loaden

Hello, everybody, I heard some thing about Nokia's Qt from Google.
And I noticed the Nokia's people seems stop work on
codereview.qt-project.org.
Any news? comments? Please let's we know.
Thanks!

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] buildsystem branch: broke cross build for Windows

2012-06-15 Thread Loaden

That's the problem.
Sorry, I forgot upload the attachment.
Same build script, works well for master branch.
So, This is only buildsystem issue.


> #!/bin/bash
> rm -rf bin
> mkdir bin
> ln -s /usr/bin/i686-w64-mingw32-gcc ./bin/i686-pc-mingw32-gcc
> ln -s /usr/bin/i686-w64-mingw32-g++ ./bin/i686-pc-mingw32-g++
> ln -s /usr/bin/i686-w64-mingw32-ar ./bin/i686-pc-mingw32-ar
> ln -s /usr/bin/i686-w64-mingw32-strip ./bin/i686-pc-mingw32-strip
> ln -s /usr/bin/i686-w64-mingw32-windres ./bin/i686-pc-mingw32-windres
> ln -s /usr/bin/i686-w64-mingw32-pkg-config ./bin/i686-pc-mingw32-pkg-config
> export LANG=C
> unset QTDIR
> export PATH="$PWD/qtbase/bin:$PWD/bin:$PATH"
> ../Qt5/configure -prefix $PWD/qtbase -xplatform
> unsupported/win32-g++-cross -opensource -confirm-license -release -fast
> -force-pkg-config -nomake examples >>config.log 2>&1
> read -n1 -p "Press any key to continue..."
>

2012/6/15 Thiago Macieira 

> Are you sure you ran the right qmake? That the mkspec setting was correct?
> Note this in your output:
>
> > -I/home/loaden/qpSOFT/Projects/Qt5/qtbase/mkspecs/linux-g++-64
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen


BuildQt5-w32.tar.gz
Description: GNU Zip compressed data
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] buildsystem branch: broke cross build for Windows

2012-06-14 Thread Loaden

*The g++ should be i686-pc-mingw32-g++*
 The master branch doesn't have this issue.

*g++* -c -m64 -pipe -O2 -fno-exceptions -Wall -W -DQT_NO_LIBUDEV
-DQT_NO_EVDEV -DQT_NO_XCB -DQT_BOOTSTRAPPED -DQT_LITE_UNICODE
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_CODECS
-DQT_NO_DATASTREAM -DQT_NO_LIBRARY -DQT_NO_QOBJECT -DQT_NO_SYSTEMLOCALE
-DQT_NO_THREAD -DQT_NO_UNICODETABLES -DQT_NO_USING_NAMESPACE
-DQT_NO_DEPRECATED -DQT_NODLL -DQT_NO_EXCEPTIONS
-I/home/loaden/qpSOFT/Projects/Qt5/qtbase/mkspecs/linux-g++-64
-I/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/tools/bootstrap
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/5.0.0
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/5.0.0/QtCore
-I/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/3rdparty/zlib -I. -o
.obj/release-static/qfilesystemengine_win.o
/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/corelib/io/qfilesystemengine_win.cpp
In file included from
/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/qt_windows.h:1:0,
 from
/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/corelib/io/qfilesystemengine_win.cpp:55:
/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/../../../../Qt5/qtbase/src/corelib/global/qt_windows.h:66:21:
fatal error: windows.h: No such file or directory
compilation terminated.
*g++* -c -m64 -pipe -O2 -fno-exceptions -Wall -W -DQT_NO_LIBUDEV
-DQT_NO_EVDEV -DQT_NO_XCB -DQT_BOOTSTRAPPED -DQT_LITE_UNICODE
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_CODECS
-DQT_NO_DATASTREAM -DQT_NO_LIBRARY -DQT_NO_QOBJECT -DQT_NO_SYSTEMLOCALE
-DQT_NO_THREAD -DQT_NO_UNICODETABLES -DQT_NO_USING_NAMESPACE
-DQT_NO_DEPRECATED -DQT_NODLL -DQT_NO_EXCEPTIONS
-I/home/loaden/qpSOFT/Projects/Qt5/qtbase/mkspecs/linux-g++-64
-I/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/tools/bootstrap
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/5.0.0
-I/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/5.0.0/QtCore
-I/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/3rdparty/zlib -I. -o
.obj/release-static/qfilesystemiterator_win.o
/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/corelib/io/qfilesystemiterator_win.cpp
make[4]: *** [.obj/release-static/qfilesystemengine_win.o] Error 1
make[4]: *** Waiting for unfinished jobs
In file included from
/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/qt_windows.h:1:0,
 from
/home/loaden/qpSOFT/Projects/Qt5/qtbase/src/corelib/io/qfilesystemiterator_win.cpp:51:
*/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/include/QtCore/../../../../Qt5/qtbase/src/corelib/global/qt_windows.h:66:21:
fatal error: windows.h: No such file or directory
compilation terminated.
*make[4]: *** [.obj/release-static/qfilesystemiterator_win.o] Error 1
make[4]: Leaving directory
`/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/src/tools/bootstrap'
make[3]: *** [sub-tools-bootstrap-make_first] Error 2
make[3]: Leaving directory
`/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/src/tools'
make[2]: *** [sub-tools-make_first] Error 2
make[2]: Leaving directory
`/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase/src'
make[1]: *** [sub-src-make_first-ordered] Error 2
make[1]: Leaving directory
`/home/loaden/qpSOFT/Projects/BuildQt5-w32/qtbase'
make: *** [module-qtbase-make_first] Error 2

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] What is the best way to use msys-git's perl for MSVC2010?

2012-06-13 Thread Loaden

Yes, It's doesn't work for me.

>  D:\qpSOFT\Projects\BuildQt5-x64>perl -v
> This is perl, v5.8.8 built for msys
> Copyright 1987-2006, Larry Wall
> Perl may be copied only under the terms of either the Artistic License or
> the
> GNU General Public License, which may be found in the Perl 5 source kit.
> Complete documentation for Perl, including FAQ lists, should be found on
> this system using "man perl" or "perldoc perl".  If you have access to the
> Internet, point your browser at http://www.perl.org/, the Perl Home Page.
>
> D:\qpSOFT\Projects\BuildQt5-x64>..\Qt5\configure -h
> */d/qpSOFT/Projects/BuildQt5-x64/qtbase/configure* not found. Did you
> forget to run "init-repository"?
>  at D:\qpSOFT\Projects\Qt5\configure line 88.
> D:\qpSOFT\Projects\BuildQt5-x64>
>

*/d/qpSOFT/Projects/BuildQt5-x64/qtbase/configure*
*Should be:*
*/d/qpSOFT/Projects/Qt5/qtbase/configure*
2012/6/13 

> What do you mean "how to make it work"? What doesn't work for you?
> Its actually quite independent of the MSVC version.
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] What is the best way to use msys-git's perl for MSVC2010?

2012-06-12 Thread Loaden

https://codereview.qt-project.org/27136
I noticed this review merged into master, and I wan't know how to make it
works for MSVC2010?
Thanks!

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 packages for Ubuntu

2012-06-10 Thread Loaden

Another way:

> sudo update-alternatives --install /usr/bin/qmake qmake /opt/qt5/bin/qmake
> 30
> sudo update-alternatives --config qmake
> update-alternatives --display qmake


2012/6/8 Zoltán Balogh 

> Remember to add the /opt/qt5/bin to the $PATH in order to use the Qt5
> binaries without problems.
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] 'assistant' should goto qtdoc-module, and 'linguist' should move to qttranslations-module

2012-06-04 Thread Loaden

Which plugin?
I am try to remove the qtquick1 depend, and find it's build fine.

> diff --git a/qt.pro b/qt.pro
> index 862e8a7..dcb1e5f 100644
> --- a/qt.pro
> +++ b/qt.pro
> @@ -42,7 +42,7 @@ module_qtwebkit_examples_and_demos.depends =
> module_qtwebkit
>
>  module_qttools.subdir = qttools
>  module_qttools.target = module-qttools
> -module_qttools.depends = module_qtbase module_qtquick1
> module_qtdeclarative
> +module_qttools.depends = module_qtbase module_qtdeclarative
>
>  module_qttranslations.subdir = qttranslations
>  module_qttranslations.target = module-qttranslations
>

2012/6/4 

> There's exactly one
> small designer plugin depending on QtQuick1 (and pulling in qtscript), so
> what we should rather do is to move that plugin out of qttools and into
> qtquick1.
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] 'assistant' should goto qtdoc-module, and 'linguist' should move to qttranslations-module

2012-06-04 Thread Loaden

Good idea!!

2012/6/4 

> so
> what we should rather do is to move that plugin out of qttools and into
> qtquick1.
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] 'assistant' should goto qtdoc-module, and 'linguist' should move to qttranslations-module

2012-06-03 Thread Loaden

For now the 'assistant'  and  'linguist' are both placed in 'qttools'
module.
I think it's not a good idea.
e.g.
I just want use qtbase-module + qch docs from assistant.
But now I have to build qtquick1, qtscript,...many depends.
If we move 'assistant' from qttools to qtdoc, then the issue should gone.
Any commens?

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] doc: need rename qdoc3 -> qdoc

2012-06-02 Thread Loaden

See the diff show below.
Any comments?

Entering 'qlalr'
> Entering 'qt3d'
> Entering 'qtactiveqt'
> Entering 'qtbase'
> Entering 'qtconnectivity'
> diff --git a/doc/doc.pri b/doc/doc.pri
> index 459e9ba..3cd0b30 100644
> --- a/doc/doc.pri
> +++ b/doc/doc.pri
> @@ -3,10 +3,10 @@ OTHER_FILES += \
>  $$PWD/qt5-dita.qdocconf
>
>  docs_target.target = docs
> -docs_target.commands = qdoc3 $$PWD/qt5.qdocconf
> +docs_target.commands = qdoc $$PWD/qt5.qdocconf
>
>  ditadocs_target.target = ditadocs
> -ditadocs_target.commands = qdoc3 $$PWD/qt5-dita.qdocconf
> +ditadocs_target.commands = qdoc $$PWD/qt5-dita.qdocconf
>
>  QMAKE_EXTRA_TARGETS = docs_target ditadocs_target
>  QMAKE_CLEAN += \
> Entering 'qtdeclarative'
> diff --git a/doc/config/qtdeclarative_doc.pri
> b/doc/config/qtdeclarative_doc.pri
> index 51f2fce..d8a3a33 100644
> --- a/doc/config/qtdeclarative_doc.pri
> +++ b/doc/config/qtdeclarative_doc.pri
> @@ -2,12 +2,12 @@ OTHER_FILES += \
> $$PWD/qtquick.qdocconf \
> $$PWD/qtquick-dita.qdocconf
>
> -online_docs.commands = qdoc3 $$PWD/qtquick.qdocconf
> +online_docs.commands = qdoc $$PWD/qtquick.qdocconf
>
> -dita_docs.commands = qdoc3 $$PWD/qtquick-dita.qdocconf
> +dita_docs.commands = qdoc $$PWD/qtquick-dita.qdocconf
>
>  docs.depends = dita_docs online_docs
>  QMAKE_EXTRA_TARGETS = docs dita_docs online_docs
>  QMAKE_CLEAN += \
> "-r $$PWD/html" \
> -   "-r $$PWD/ditaxml"
> \ No newline at end of file
> +   "-r $$PWD/ditaxml"
> Entering 'qtdoc'
> Entering 'qtdocgallery'
> Entering 'qtfeedback'
> Entering 'qtgraphicaleffects'
> Entering 'qtimageformats'
> diff --git a/doc/doc.pri b/doc/doc.pri
> index e87ab19..3e401df 100644
> --- a/doc/doc.pri
> +++ b/doc/doc.pri
> @@ -3,10 +3,10 @@ OTHER_FILES += \
> $$PWD/qtimageformats-dita.qdocconf
>
>  docs_target.target = docs
> -docs_target.commands = qdoc3 $$PWD/qtimageformats.qdocconf
> +docs_target.commands = qdoc $$PWD/qtimageformats.qdocconf
>
>  ditadocs_target.target = ditadocs
> -ditadocs_target.commands = qdoc3 $$PWD/qtimageformats-dita.qdocconf
> +ditadocs_target.commands = qdoc $$PWD/qtimageformats-dita.qdocconf
>
>  QMAKE_EXTRA_TARGETS = docs_target ditadocs_target
>  QMAKE_CLEAN += \
> Entering 'qtjsbackend'
> Entering 'qtjsondb'
> Entering 'qtlocation'
> diff --git a/doc/config/qtlocation_doc.pri b/doc/config/qtlocation_doc.pri
> index a2e2bab..feae9eb 100644
> --- a/doc/config/qtlocation_doc.pri
> +++ b/doc/config/qtlocation_doc.pri
> @@ -7,7 +7,7 @@ win32:!win32-g++ {
>  unixstyle = true
>  }
>
> -QDOC = $$QT.core.bins/qdoc3
> +QDOC = $$QT.core.bins/qdoc
>
>  ONLINE_CONF = $$PWD/qtlocation.qdocconf
>  DITA_CONF = $$PWD/qtlocation-dita.qdocconf
> @@ -15,7 +15,6 @@ QCH_CONF = #nothing yet
>
>  $$unixstyle {
>  } else {
> -QDOC = $$replace(QDOC, "qdoc", "qdoc3.exe")
>  ONLINE_CONF = $$replace(ONLINE_CONF, "/", "\\")
>  DITA_DOCS = $$replace(ONLINE_CONF, "/", "\\")
>  }
> Entering 'qtmultimedia'
> diff --git a/doc/config/qtmultimedia_doc.pri
> b/doc/config/qtmultimedia_doc.pri
> index 8aab323..9f36439 100644
> --- a/doc/config/qtmultimedia_doc.pri
> +++ b/doc/config/qtmultimedia_doc.pri
> @@ -7,15 +7,7 @@ win32:!win32-g++ {
>  unixstyle = true
>  }
>
> -system(which qdoc) {
> -QDOC = qdoc
> -} else {
> -exists($$QT.core.bins/qdoc3) {
> -QDOC = $$QT.core.bins/qdoc3
> -} else {
> -warning("No qdoc executable found.")
> -}
> -}
> +QDOC = $$QT.core.bins/qdoc
>
>  ONLINE_CONF = $$PWD/qtmultimedia.qdocconf
>  DITA_CONF = $$PWD/qtmultimedia-dita.qdocconf
> @@ -23,7 +15,6 @@ QCH_CONF = #nothing yet
>
>  $$unixstyle {
>  } else {
> -QDOC = $$replace(QDOC, "qdoc", "qdoc3.exe")
>  ONLINE_CONF = $$replace(ONLINE_CONF, "/", "\\")
>  DITA_DOCS = $$replace(ONLINE_CONF, "/", "\\")
>  }
> Entering 'qtphonon'
> Entering 'qtpim'
> Entering 'qtqa'
> Entering 'qtquick1'
> Entering 'qtrepotools'
> Entering 'qtscript'
> Entering 'qtsensors'
> diff --git a/doc/config/qtsensors_doc.pri b/doc/config/qtsensors_doc.pri
> index 4c91758..9ce9913 100644
> --- a/doc/config/qtsensors_doc.pri
> +++ b/doc/config/qtsensors_doc.pri
> @@ -7,7 +7,7 @@ win32:!win32-g++ {
>  unixstyle = true
>  }
>
> -QDOC = $$QT.core.bins/qdoc3
> +QDOC = $$QT.core.bins/qdoc
>
>  ONLINE_CONF = $$PWD/qtsensors.qdocconf
>  DITA_CONF = $$PWD/qtsensors-dita.qdocconf
> @@ -15,7 +15,6 @@ QCH_CONF = #nothing yet
>
>  $$unixstyle {
>  } else {
> -QDOC = $$replace(QDOC, "qdoc", "qdoc3.exe")
>  ONLINE_CONF = $$replace(ONLINE_CONF, "/", "\\")
>  DITA_DOCS = $$replace(ONLINE_CONF, "/", "\\")
>  }
> Entering 'qtsvg'
> Entering 'qtsystems'
> Entering 'qttools'
> Entering 'qttranslations'
> Entering 'qtwayland'
> Entering 'qtxmlpatterns'
> diff --git a/.gitignore b/.gitignore
> index 6e178a2..5cbefb5 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -67,8 +67,7 @@ bin/moc*
>  bin/makeqpf*
>  bin/pixeltool*
>  bin/qmake*
> -bin/qdoc3*
> -bin/qt3

Re: [Development] FW: Alpha 2 this week or skip it

2012-06-01 Thread Loaden

If it realy wrong, we should rename win32-msvc2010 -> win32-msvc10,
msvc2008 -> win32-msvc9 ...

2012/6/1 Thiago Macieira 

> Right. We've been doing it wrong all along, then: our mkspecs say "msvc"
> which
> is the compiler, but give the year as the complement.
>
> Maybe we should then start correcting this by keeping "msvc11".
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Quick2 and Directx11 backend (Angle)

2012-05-31 Thread Loaden

I hope we can add ANGLE project as the third party.
Just for easy develop and build.

2012/5/31 Friedemann Kleint 

> add the library to our 3rd-Party folder.
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build broke on Windows 7 64bit, whatever out-of-source or in-source-tree

2012-05-30 Thread Loaden

You are right. I just made a patch to fix this issue.
See: https://codereview.qt-project.org/#change,27431

2012/5/29 Rohan McGovern 

>  LIBS += -L../../3rdparty/poly2tri -lpoly2tri
>  win32:LIBS += -L../../3rdparty/poly2tri/release
> -L../../3rdparty/poly2tri/debug
>
> Unless I've missed something, there's nothing here which ensures the
> debug version of declarative_location is linked with the debug version
> of the poly2tri static library.




-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Regression: comapp.exe crashes when building Qt use nmake

2012-05-30 Thread Loaden

I find this bug report:
https://bugreports.qt-project.org/browse/QTCREATORBUG-6578
And now Qt5 have the same build issue.
And many times crash about idc.exe.
Windows 7 64bit & MSVC2010SP1.

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 binary installers

2012-05-28 Thread Loaden

A workround: You can change qtbase\mkspecs\qconfig.pri after configure is
done.
From:

> CONFIG+= debug shared rtti sse2 qpa

To:

> CONFIG+= debug *build_all* shared rtti sse2 qpa

Then everything should build well. I am using this hack for a long time.
After the build done, you can change to back, just remove 'build_all'
because we don't realy wan't it.

2012/5/26 qtnext 

> I have tryed windows version sdk : the install works but :
> - plugins and import qml have only debug dll ... there is no release
> version (all normal dll have release version) .. I have the same issue
> building from git on windows.
>

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build broke on Windows 7 64bit, whatever out-of-source or in-source-tree

2012-05-28 Thread Loaden

>
> Generating Code...
>  link /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib"
> /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib"
> /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib" /NOLOGO /DYNAMICBASE
> /NXCOMPAT /DEBUG /DLL /MANIFEST
> /MANIFESTFILE:"debug\declarative_locationd.intermediate.manifest"
> /OUT:d:\qpSOFT\Projects\BuildQt5-x64\qtbase\imports\QtLocation\declarative_locationd.dll
> @C:\Users\loaden\AppData\Local\Temp\nmAC70.tmp
> poly2tri.lib(cdt.obj) : error LNK2038: mismatch detected for
> '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
> qdeclarativeposition.obj
> poly2tri.lib(sweep_context.obj) : error LNK2038: mismatch detected for
> '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
> qdeclarativeposition.obj
> poly2tri.lib(sweep.obj) : error LNK2038: mismatch detected for
> '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
> qdeclarativeposition.obj
> poly2tri.lib(advancing_front.obj) : error LNK2038: mismatch detected for
> '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
> qdeclarativeposition.obj
> poly2tri.lib(shapes.obj) : error LNK2038: mismatch detected for
> '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
> qdeclarativeposition.obj
>Creating library
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\imports\QtLocation\declarative_locationd.lib
> and object
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\imports\QtLocation\declarative_locationd.exp
> LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other
> libs; use /NODEFAULTLIB:library
> d:\qpSOFT\Projects\BuildQt5-x64\qtbase\imports\QtLocation\declarative_locationd.dll
> : fatal error LNK1319: 5 mismatches detected
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio 10.0\VC\Bin\amd64\link.EXE"' : return code '0x527'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio 10.0\VC\Bin\amd64\nmake.exe"' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'cd' : return code '0x2'
> Stop.
>
> Build broke after re-install Windows SDK 7.1.
Any comments?
2012/5/28 Loaden 

> :(
> The erroe message:
>
>> QtDBus: created headers.pri file
>> No suitable compiler found in PATH. Aborting.
>> *** qtbase/configure exited with non-zero status.
>>
>>
> 2012/5/28 Thiago Macieira 
>
>>  On segunda-feira, 28 de maio de 2012 14.57.44, Loaden wrote:
>> > Sorry, I make a big mistake, because I don't install .NET 4.0 first,
>> Then
>> > Windows SDK 7.1 don't install the MSVC compiler, It's disabled becasue
>> miss
>> > .NET 4.
>> > I will feedback after Re-install SDK 7.1.
>> > Sorry for the noise.
>>
>> So the error was:
>>
>> cl.exe: Bad command or file name ?
>>
>> --
>> Thiago Macieira - thiago.macieira (AT) intel.com
>>  Software Architect - Intel Open Source Technology Center
>> Intel Sweden AB - Registration Number: 556189-6027
>> Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
>>
>> ___
>> Development mailing list
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>>
>>
>
>
> --
> Please don't ask where I come from, It's a shame!
> Best Regards
> Yuchen
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build broke on Windows 7 64bit, whatever out-of-source or in-source-tree

2012-05-28 Thread Loaden

:(
The erroe message:

> QtDBus: created headers.pri file
> No suitable compiler found in PATH. Aborting.
> *** qtbase/configure exited with non-zero status.
>
>
2012/5/28 Thiago Macieira 

> On segunda-feira, 28 de maio de 2012 14.57.44, Loaden wrote:
> > Sorry, I make a big mistake, because I don't install .NET 4.0 first, Then
> > Windows SDK 7.1 don't install the MSVC compiler, It's disabled becasue
> miss
> > .NET 4.
> > I will feedback after Re-install SDK 7.1.
> > Sorry for the noise.
>
> So the error was:
>
> cl.exe: Bad command or file name ?
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> Intel Sweden AB - Registration Number: 556189-6027
> Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build broke on Windows 7 64bit, whatever out-of-source or in-source-tree

2012-05-27 Thread Loaden

Sorry, I make a big mistake, because I don't install .NET 4.0 first, Then
Windows SDK 7.1 don't install the MSVC compiler, It's disabled becasue miss
.NET 4.
I will feedback after Re-install SDK 7.1.
Sorry for the noise.
2012/5/28 Thiago Macieira 

>  On segunda-feira, 28 de maio de 2012 14.57.03, Rohan McGovern wrote:
> > Loaden said:
> > > Windows SDK 7.1 & ActivePerl 64bit & Python 2.7.3
> > > Any comments?
> >
> > Maybe some comments if you share the build log :)
>
> Also, please let us know whether you tried 32-bit too. When you say "I had
> an
> error when I built on 64-bit", people might search for something specific
> to
> 64-bit.
>
> Other useful information is the SHA-1 of the commit you tried and the
> configure
> line.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> Intel Sweden AB - Registration Number: 556189-6027
> Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Build broke on Windows 7 64bit, whatever out-of-source or in-source-tree

2012-05-27 Thread Loaden

Windows SDK 7.1 & ActivePerl 64bit & Python 2.7.3
Any comments?

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Quick2 and Directx11 backend (Angle)

2012-05-26 Thread Loaden

I thought MinGW-w64 should work, It's can worked with DirectX 9/10 apis.
But I didn't have a try.

2012/5/20 Corentin Jabot 

> Limitations:
> * I thought of including ANGLE in the Qt sources, so it
> can automatically be build via some configure option, but sadly ANGLE is
> not designed to compile with MINGW.
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Interest] Warining about: Project WARNING: QtGui cannot have a QT of gui

2012-05-22 Thread Loaden

It's only related with Windows. It's should be qmake's problem / issue.
Hope to be fixed before the release coming.

2012/5/22 Thiago Macieira 

> > I am building the Qt5, but could somebody point out what's the possible
> > cause of: Project WARNING: QtGui cannot have a QT of gui
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Quick2 and Directx11 backend (Angle)

2012-05-20 Thread Loaden

It's great if it work. I am very glad to hear even it's only a beginning.
That It's possible Nokia qt-term take and improve it?
It's a new hope from Windows side. (from Star War IV :))
Well done!

2012/5/20 Corentin Jabot 

> So, There is the patch.
>
> * First, checkout and build ANGLE as explain here
> http://code.google.com/p/angleproject/wiki/DevSetup ( require directx sdk
> &  visual studio )
> * Then, edit qtbase/mkspecs/features/win32/opengl.prf and change the
> include and library path of angle ( or just build angle in C:\\angle)
> * Run configure.exe with the option "-opengl es2"
> * Build qtbase, it should works fine.
> * Build and test some examples.
>
> examples\opengl\hellowindow work just fine.
> The others do not : black screen, crash, etc.
> I'm not so sure where the problem really is, that is why I seek help
>
> How does it work ?
> When configured with -opengl es2,  the windows QPA will use an EGL
> contexts and surfaces instead of opengl. the EGL calls are
> converted transparently by ANGLE into directx calls.
>
> Remaining work :
> * Try and fixes the black screen, crashes, and others issues ( like
> ui unresponsiveness)
> * Clean the code
> * Integrate nicely with QSurfaceFormat and find optimal options.
> * Ensure QtDeclarative and other modules works fine on top of angle
>
> Limitations:
> * I thought of including ANGLE in the Qt sources, so it
> can automatically be build via some configure option, but sadly ANGLE is
> not designed to compile with MINGW.
> * ANGLE provide an OpenGL ES 2.0 API, not an Opengl API. So examples,
> applications or features that specifically require a full opengl api are
> not supposed to work.
>
>
> I'm convinced that this kind of work is really important for QML adoption
> since a lot of final Windows users do not have a working opengl support  -
> mostly because they use outdated drivers, and they can be hard to update,
> especially on laptops.
> The ultimate solution would be to use ANGLE as a fallback if
> the initialization of a classic opengl context fail, but that seems a
> really laborious task.
> Also, Thiago mentioned a cpu-rasterization project, I guess that would
> make ANGLE useless, but I'm not sure there is people working on that.  And
> the performance of such solution wouldn't be so great.
>
>
>
> Please note that patch is very unstable and experimental. The patch is
> quite ugly, I put some code in place it does not belong (see
> QEGLPlatformContext constructor ) and added a lot of logs to figure what go
> wrong.
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build failed use MinGW-TDM or MinGW-w64 on Windows

2012-05-18 Thread Loaden

Build failed with the same errors.

2012/5/18 

> Just try to do
>  %QTSOURCE%\configure -opensource
> -prefix D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase -confirm-license
> -platform win32-g++ -debug-and-release -fast -nomake examples >>config.log
> 2>&1
>  Instead, and see if that helps.
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build failed use MinGW-TDM or MinGW-w64 on Windows

2012-05-18 Thread Loaden

What is the time to merge the origin/buildsystem into origin/master?
When it's ready? or have a plan?

I am do not set the QTDIR env value as the wiki says.
The mean the 'QTDIR' env does not exist.

The configure command on Windows:

> %QTSOURCE%\configure -opensource -prefix %CD%\qtbase -confirm-license
> -platform win32-g++ -debug-and-release -fast -nomake examples >>config.log
> 2>&1


Here is the 'qmake -query' print log:

>  D:\qpSOFT\Projects\BuildQt5-x86-tdm>qmake -query
> QT_SYSROOT:
> QT_INSTALL_PREFIX:D:\qpSOFT\Projects\BuildQt5-x86-tdm\qtbase
> QT_INSTALL_DATA:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase
> QT_INSTALL_DOCS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/doc
> QT_INSTALL_HEADERS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/include
> QT_INSTALL_LIBS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/lib
> QT_INSTALL_BINS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/bin
> QT_INSTALL_TESTS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/tests
> QT_INSTALL_PLUGINS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/plugins
> QT_INSTALL_IMPORTS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/imports
>
> QT_INSTALL_TRANSLATIONS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/translations
> QT_INSTALL_CONFIGURATION:
> QT_INSTALL_EXAMPLES:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/examples
> QT_INSTALL_DEMOS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/examples
> QT_HOST_PREFIX:D:\qpSOFT\Projects\BuildQt5-x86-tdm\qtbase
> QT_HOST_DATA:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase
> QT_HOST_BINS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/bin
> QMAKE_MKSPECS:D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase/mkspecs
> QMAKE_VERSION:2.01a
> QT_VERSION:5.0.0


2012/5/18 

> QTDIR




-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Build failed use MinGW-TDM or MinGW-w64 on Windows

2012-05-17 Thread Loaden

1. It successful use MSVC2010 for shadow (out-of-source) , no need 'make
install' things
2. In-Source-Build also failed with MinGW-TDM

2012/5/15 

> You need to make install after building each module to copy the output to
> the prefix directory you specified in configure.
>
> The top level makefile only works for in-source developer builds.
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Build failed use MinGW-TDM or MinGW-w64 on Windows

2012-05-15 Thread Loaden

Hi, All!
I am just try to build Qt5 under Windows, use MinGW-TDM or MinGW-w64
(32bit), but both failed with the same log.
I don't know how to fix the problem.
Any comments?

> cd svg\ && mingw32-make -f Makefile
>
> mingw32-make[3]: Entering directory
>> `D:/qpSOFT/Projects/BuildQt5-TDM/qtsvg/src/svg'
>
> mingw32-make -f Makefile.Debug all
>
> mingw32-make[4]: Entering directory
>> `D:/qpSOFT/Projects/BuildQt5-TDM/qtsvg/src/svg'
>
> g++ -c -fno-keep-inline-dllexport -g -Wall -frtti -fexceptions -mthreads
>> -DQT_SHARED -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_BUILD_SVG_LIB
>> -DQT_NO_USING_NAMESPACE -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII
>> -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER
>> -DQT_DEPRECATED_WARNINGS -D_USE_MATH_DEFINES -DQT_DLL -DQT_HAVE_SSE2
>> -I"d:\qpSOFT\Projects\BuildQt5-TDM\qtbase\include"
>> -I"..\..\include\QtSvg\5.0.0" -I"..\..\include\QtSvg\5.0.0\QtSvg"
>> -I"..\..\include" -I"..\..\include\QtSvg" -I"..\..\include" -I"tmp"
>> -I"d:\qpSOFT\Projects\Qt5\qtbase\src\3rdparty\harfbuzz\src"
>> -I"d:\qpSOFT\Projects\Qt5\qtsvg\src\3rdparty\zlib"
>> -I"d:\qpSOFT\Projects\Qt5\qtbase\mkspecs\win32-g++" -I"debug"
>> -I"d:\qpSOFT\Projects\Qt5\qtsvg\src\svg" -I"."
>> -I"d:\qpSOFT\Projects\BuildQt5-TDM\qtbase\mkspecs\default" -o
>> debug\qsvggraphics.o d:\qpSOFT\Projects\Qt5\qtsvg\src\svg\qsvggraphics.cpp
>
> In file included from
>> d:\qpSOFT\Projects\Qt5\qtsvg\src\svg\qsvgnode_p.h:56:0,
>
>  from
>> d:\qpSOFT\Projects\Qt5\qtsvg\src\svg\qsvggraphics_p.h:56,
>
>  from
>> d:\qpSOFT\Projects\Qt5\qtsvg\src\svg\qsvggraphics.cpp:42:
>
> d:\qpSOFT\Projects\Qt5\qtsvg\src\svg\qsvgstyle_p.h:65:20: fatal error:
>> qdebug.h: No such file or directory
>
> compilation terminated.
>
> mingw32-make[4]: *** [debug/qsvggraphics.o] Error 1
>
> mingw32-make[4]: Leaving directory
>> `D:/qpSOFT/Projects/BuildQt5-TDM/qtsvg/src/svg'
>
> mingw32-make[3]: *** [debug-all] Error 2
>
> mingw32-make[3]: Leaving directory
>> `D:/qpSOFT/Projects/BuildQt5-TDM/qtsvg/src/svg'
>
> mingw32-make[2]: *** [sub-svg-make_default-ordered] Error 2
>
> mingw32-make[2]: Leaving directory
>> `D:/qpSOFT/Projects/BuildQt5-TDM/qtsvg/src'
>
> mingw32-make[1]: *** [module-qtsvg-src-make_default] Error 2
>
> mingw32-make[1]: Leaving directory `D:/qpSOFT/Projects/BuildQt5-TDM/qtsvg'
>
> mingw32-make: *** [module-qtsvg-make_default] Error 2
>
> mingw32-make: *** Waiting for unfinished jobs
>
> Project MESSAGE: Warning: unknown QT module: network
>
> Project MESSAGE: Warning: unknown QT module: core
>
> Project MESSAGE: This project is using private headers and will therefore
>> be tied to this specific Qt module build version.
>
> Project MESSAGE: Running this project against other versions of the Qt
>> modules may crash at any arbitrary point.
>
> Project MESSAGE: This is not a bug, but a result of using Qt internals.
>> You have been warned!
>
> Project MESSAGE: Warning: unknown QT module: network
>
> Project MESSAGE: Warning: unknown QT module: core
>
> Project MESSAGE: Warning: unknown QT module: network
>
> Project MESSAGE: Warning: unknown QT module: core
>
> cd xmlpatterns\ && mingw32-make -f Makefile
>
> mingw32-make[3]: Entering directory
>> `D:/qpSOFT/Projects/BuildQt5-TDM/qtxmlpatterns/src/xmlpatterns'
>
> mingw32-make -f Makefile.Debug all
>
> mingw32-make[4]: Entering directory
>> `D:/qpSOFT/Projects/BuildQt5-TDM/qtxmlpatterns/src/xmlpatterns'
>
> g++ -c -fno-keep-inline-dllexport -g -Wall -fexceptions -mthreads -frtti
>> -DQT_SHARED -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_BUILD_XMLPATTERNS_LIB
>> -DQT_NO_USING_NAMESPACE -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII
>> -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER
>> -DQT_DEPRECATED_WARNINGS -D_USE_MATH_DEFINES -DQT_DLL -DQT_HAVE_SSE2
>> -I"d:\qpSOFT\Projects\BuildQt5-TDM\qtbase\include"
>> -I"..\..\include\QtXmlPatterns\5.0.0"
>> -I"..\..\include\QtXmlPatterns\5.0.0\QtXmlPatterns" -I"..\..\include"
>> -I"..\..\include\QtXmlPatterns" -I"..\..\include" -I"tmp"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\acceltree"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\data"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\api"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\environment"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\expr"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\functions"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\iterators"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\janitors"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\parser"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\schema"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\type"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns\utils"
>> -I"d:\qpSOFT\Projects\Qt5\qtbase\mkspecs\win32-g++" -I"debug"
>> -I"d:\qpSOFT\Projects\Qt5\qtxmlpatterns\src\xmlpatterns" -I"."
>> -I"d:\qpSOFT\Projects\BuildQt5-TDM\qtbase\mkspecs\

Re: [Development] Crosscompile on Debian stable targeting MS Windows

2012-05-14 Thread Loaden

Hi, kb, could you share us what you using of the build script? or command?
I can't find a wiki to point me how to cross build for windows.
So, I don't know I am doing is or not is correct.
Thanks again!

2012/5/14 Loaden 

> Oh, Thanks! I will test it on Ubuntu.
>
>
> 2012/5/14 k blammo 
>
>> On 14/05/2012 12:29, Loaden wrote:
>>
>>> I just sent a code review to:
>>> https://codereview.qt-project.**org/#change,26120<https://codereview.qt-project.org/#change,26120>
>>> Please have a look.
>>>
>>
>> That will not be necessary after this has landed:
>> https://codereview.qt-project.**org/#change,25617<https://codereview.qt-project.org/#change,25617>
>>
>>
>
>
> --
> Please don't ask where I come from, It's a shame!
> Best Regards
> Yuchen
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Crosscompile on Debian stable targeting MS Windows

2012-05-14 Thread Loaden

Oh, Thanks! I will test it on Ubuntu.

2012/5/14 k blammo 

> On 14/05/2012 12:29, Loaden wrote:
>
>> I just sent a code review to:
>> https://codereview.qt-project.**org/#change,26120<https://codereview.qt-project.org/#change,26120>
>> Please have a look.
>>
>
> That will not be necessary after this has landed:
> https://codereview.qt-project.**org/#change,25617<https://codereview.qt-project.org/#change,25617>
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Crosscompile on Debian stable targeting MS Windows

2012-05-14 Thread Loaden

Sorry, It shoud be:

> make -j 2 >>build.log 2>&1
>

2012/5/14 Loaden 

> -nomake examples >>config.log 2>&1
>> make module-qt3d -j 2 >>build.log 2>&1
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Crosscompile on Debian stable targeting MS Windows

2012-05-14 Thread Loaden

I just sent a code review to:
https://codereview.qt-project.org/#change,26120
Please have a look.

Here is the build script for Ubuntu-mingw-w64:

> #!/bin/sh
>
> rm -rf bin
> mkdir bin
> ln -s /usr/bin/i686-w64-mingw32-gcc ./bin/i686-pc-mingw32-gcc
> ln -s /usr/bin/i686-w64-mingw32-g++ ./bin/i686-pc-mingw32-g++
> ln -s /usr/bin/i686-w64-mingw32-ar ./bin/i686-pc-mingw32-ar
> ln -s /usr/bin/i686-w64-mingw32-strip ./bin/i686-pc-mingw32-strip
> ln -s /usr/bin/i686-w64-mingw32-windres ./bin/i686-pc-mingw32-windres
>
> export LANG=C
> unset QTDIR
> export PATH="$PWD/../Qt5/qtbase/bin:$PWD/bin:$PATH"
>
> ../Qt5/configure -prefix $PWD/qtbase -xplatform
> unsupported/win32-g++-cross -opensource -confirm-license -release -fast
> -nomake examples >>config.log 2>&1
> make module-qt3d -j 2 >>build.log 2>&1
>
> read -p "Press any key to continue..." nothing
>

Any comments or tips are welcome!

2012/5/14 Loaden 

> Are you sure you can build all module use '-xplatform
> unsupported/win32-g++-corss'?
> In Ubuntu 12.04, It's only build qtbase module if use 'make -j 2'.
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Crosscompile on Debian stable targeting MS Windows

2012-05-14 Thread Loaden

#include of  not needed on Ubuntu 12.04 (mingw-w64).
Are you sure you can build all module use '-xplatform
unsupported/win32-g++-corss'?
In Ubuntu 12.04, It's only build qtbase module if use 'make -j 2'.
2012/5/4 kb 

> #include of 




-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] How to build Qt5 out-of-source?

2012-05-13 Thread Loaden

In out-of-source build, I have to copy the 'build' and 'build.dependencies'
from source directory into the build directory.
Then these command lead failed with the log show below.

#!/bin/bash
>
> export LANG=C
> unset QTDIR
> export PATH="$PWD/../Qt5/qtbase/bin:$PATH"
>
> ../Qt5/configure -prefix $PWD/qtbase -opensource -confirm-license -fast
> -nomake examples >>config.log 2>&1
> ./build -j 2 >>build.log 2>&1
>
> read -n1 -p "Press any key to continue..."


The error message:

> Missing module qtlocation, ignored
> Missing module qtwebkit, ignored
> Missing module qtpim, ignored
> Missing module qtimageformats, ignored
> Missing module qtdeclarative, ignored
> Missing module qlalr, ignored
> Missing module qtquick1, ignored
> Missing module qttranslations, ignored
> Missing module qtwayland, ignored
> Missing module qtqa, ignored
> Missing module qtscript, ignored
> Missing module qtfeedback, ignored
> Missing module qtwebkit-examples-and-demos, ignored
> Missing module qtconnectivity, ignored
> Missing module qtxmlpatterns, ignored
> Missing module qtsensors, ignored
> Missing module qtdoc, ignored
> Missing module qtmultimedia, ignored
> Missing module qtdocgallery, ignored
> Missing module qtgraphicaleffects, ignored
> Missing module qtsvg, ignored
> Missing module qt3d, ignored
> Missing module qtjsbackend, ignored
> Missing module qtjsondb, ignored
> Missing module qtphonon, ignored
> Missing module qttools, ignored
> Missing module qtsystems, ignored
> OS Name  linux
> Verbose  no
> Continue ... no
> Force qmake. no
> Jobs ... 2
> PATH
> /home/loaden/qpSOFT/Projects/BuildQt5-2/qtbase/bin:/home/loaden/qpSOFT/Projects/BuildQt5-2/../Qt5/qtbase/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> Modules to build:
> qtbase
> build qtbase...
> + cd qtbase && make -j 2
>

 It seems we can't use 'build' script, just only use make stuff.
e.g.

> #!/bin/bash
>
> export LANG=C
> unset QTDIR
> export PATH="$PWD/../Qt5/qtbase/bin:$PATH"
>
> ../Qt5/configure -prefix $PWD/qtbase -opensource -confirm-license -fast
> -nomake examples >>config.log 2>&1
> make -j 2 >>build.log 2>&1
>
> read -n1 -p "Press any key to continue..."
>
> Should works well for shadow build.

2012/5/12 Thiago Macieira 

> On sábado, 12 de maio de 2012 15.28.16, Loaden wrote:
> > Hi, all!
> > I want build Qt5 use out-of-source like this way, and final failed.
>
> What is this final that failed?
>
> Out-of-source buiding works for me, though not all the time. Sometimes
> there
> are issues that need fixing.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> Intel Sweden AB - Registration Number: 556189-6027
> Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>


-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] How to build Qt5 out-of-source?

2012-05-12 Thread Loaden

Hi, all!
I want build Qt5 use out-of-source like this way, and final failed.

#!/bin/bash
>
> unset QTDIR
> export PATH="$PWD/../Qt5/qtbase/bin:$PATH"
>
> ../Qt5/configure -prefix $PWD/qtbase -opensource -confirm-license -fast
> -nomake examples
> ../Qt5/build -j 1
>
> read -n1 -p "Press any key to continue..."
>
> Any comments and tips are very welcome!

-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] important: upcoming rename of _qpa.h to _p.h

2012-05-10 Thread Loaden

Not work for "nmake install INSTALL_ROOT=...", missed 'qba' headers in
QtGui.

> progressmanager_win.cpp
> Header  is deprecated. Please include
>  instead.
> ..\..\..\..\Qt5\qtbase\include\QtGui\QPlatformNativeInterface(8) : fatal
> error C1083: Cannot open include file: 'qpa/qplatformnativeinterface.h': No
> such file or directory
> NMAKE : fatal error U1077: 'D:\qpSOFT\DEVx86\bin\cl.EXE' : return code
> '0x2'
> Stop.
> NMAKE : fatal error U1077: 'D:\qpSOFT\DEVx86\bin\nmake.exe' : return code
> '0x2'


2012/5/9 Girish Ramakrishnan 

> On Tue, May 8, 2012 at 5:31 PM, Girish Ramakrishnan
>  wrote:
> > On Tuesday, May 8, 2012, Girish Ramakrishnan 
> wrote:
> >> Hi,
> >>
> >> On Tue, May 8, 2012 at 3:07 AM, Girish Ramakrishnan
> >>  wrote:
> >>> The change landed. For some reason, the ci is failing compile in all
> >>> other modules. Works locally with shadow builds but not on CI. I am on
> >>> it.
> >>>
> >>
> >> Fix is integrating: https://codereview.qt-project.org/#change,25570.
> >> Sorry for blocking the CI.
> >> Girish
> >>
> >
> > Ci is unblocked. fixes for wayland, qtmm and declarative have landed.
> > https://codereview.qt-project.org/#change,23444 is needed for complete
> > source compat.
> >
>
> That's the wrong change :) I meant
> https://codereview.qt-project.org/#change,25654
>
> Girish
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [QT5] System fonts are not loaded in ubuntu 12.04

2012-05-05 Thread Loaden

Same issue in Chara.

2012/5/5 liang jian 

>I have built Qt 5 in ubuntu 12.04, The simplified chinese
> character can't be displayed.
>I found that in QBaseFontDatabase::popluateFontDatabase() the font
> path returned by fontDir() is "/mnt/sda8/liang/qt5/qtbase/lib/fonts/"
> which is the path I built my Qt5, there are several fonts file in this
> directory but there are no chinese font files. As a result of this,
> the system font installed on my ubuntu 12.04 was not loaded and the
> simplified chinese character can't be displayed.
>In Qt5 Windows platform, there is a classe named
> QWindowsFontDatabase which is a subclass of QPlatformFontDatabase
> which will search Windows Font using Windows API, I there any way to
> search system fonts in XCB?
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] When it coming about qbs plugin in Creator

2012-04-30 Thread Loaden

It does not work.
Show me a error message: "Unknown property:qt.core.qtPath"


> D:\qpSOFT\DEVx64>qbs config --list
> local variables:
> global variables:
> defaults.platform: WinSDK7.1.7600.0.30514
> modules.qbs.platform: WinSDK7.1.7600.0.30514
> profile: qt4
> profiles.qt4.qt.core.path: D:\qpSOFT\DEVx64\qt
> profiles.qt5.qt.core.path: D:\qpSOFT\DEVx64\qt5
> profiles.qt5.qt.core.version: 5.0.0
> D:\qpSOFT\DEVx64>qbs platforms list
> Platforms:
> - WinSDK7.1.7600.0.30514 (default)
>

Any commens?
2012/4/30 Joerg Bornemann 

> Status of the thing is: It can
>   - load a qbs project and display the project tree in the side bar
>   - build a project
>   - run a project
>



-- 
Please don't ask where I come from, It's a shame!
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

1 2 >

1 - 100 of 151 matches

Mail list logo