Re: Arsenalsuite Windows build
Matthew Newell
hasn't merged the latest sip and PyQt from blur's repo. Arsenals
version only supports up to Qt 4.6.1 according to the configure.py
file, I don't know where the 4.7.0 version stuff is coming from in
your build. I'll see if i can get that working and if so i'll commit
it to a branch then barry can merge it to trunk(is that what's it's
called in murcurial?) after he tests. I'm quite busy today so i might
not get this done until tomorrow.
Matt
On Thu, Sep 22, 2011 at 1:04 PM, Justin Ream <justi...@gmail.com> wrote:
> Even after QTDIR is set, it seems it still wants to reference 4.7.0.
> I'm going to go ahead and compile 4.7.0 and give it a whirl.
>
> -Justin
>
> On Thu, Sep 22, 2011 at 10:52 AM, Matthew Newell <newe...@gmail.com> wrote:
>> Do you have QTDIR set as an env variable? Make sure it's set and that
>> %QTDIR%\bin is in the path. I would remove the sip:skip from the cmd
>> line unless you have already compiled and installed it(it compiles
>> quicky so I always let it). I've only compiled against 4.6.2 on
>> windows, but have compiled with the same sip/pyqt against 4.7.1 on
>> linux, so I'm pretty sure that should also work on windows.
>>
>> Matt
>>
>> On Thu, Sep 22, 2011 at 10:35 AM, Justin Ream <justi...@gmail.com> wrote:
>>> Hey guys -
>>>
>>> I started over on a Windows build after unsuccessfully trying to get
>>> the Linux rpms to run.
>>>
>>> Real quick - does the suite want to build against 4.6.2 or 4.7.0?
>>> Last notes I could find in the mailing list centered around 4.6.2, but
>>> when I attempt to compile PyQT it's looking for a mkspec in
>>> C:\Qt\4.7.0. Output from build.py follows:
>>>
>>> C:\arsenalsuite>build.py -color -command_only verbose clean build install releas
>>> e sip:skip pyqt
>>> C:\arsenalsuite\python/blur\build.py:7: DeprecationWarning: The popen2 module is
>>> deprecated. Use the subprocess module.
>>> import popen2
>>> Starting Build
>>> Targets: [sip, pyqt]
>>> Args: ['-color', '-command_only', 'verbose', 'clean', 'build', 'install', 'rele
>>> ase', 'sip:skip']
>>> Building: pyqt C:\arsenalsuite\cpp\lib\PyQt4
>>> Running Command: python configure.py -w
>>> Error: Unable to find the qmake configuration file
>>> C:\Qt\4.7.0\mkspecs\win32-msvc2008\qmake.conf. Use the QMAKESPEC environment
>>> variable to specify the correct platform.
>>> Determining the layout of your Qt installation...
>>> C:\Qt\4.6.2\bin\qmake.exe -o qtdirs.mk qtdirs.pro
>>> nmake -f qtdirs.mk release
>>>
>>> Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
>>> Copyright (C) Microsoft Corporation. All rights reserved.
>>>
>>> "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe" -f
>>> qtdirs.mk.Release
>>>
>>> Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
>>> Copyright (C) Microsoft Corporation. All rights reserved.
>>>
>>> cl -c -nologo -Zm200 -Zc:wchar_t- -O2 -MD -GR -EHsc -W3 -w34100 -w34189
>>> -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -D
>>> QT_THREAD_SUPPORT -I"..\..\..\..\Qt\4.6.2\include\QtCore" -I"..\..\..\..\Qt\4.6.
>>> 2\include" -I"..\..\..\..\Qt\4.6.2\include\ActiveQt" -I"release" -I"..\..\..\..\
>>> Qt\4.6.2\mkspecs\win32-msvc2008" -Forelease\ @C:\Users\ADMINI~1\AppData\Local\Te
>>> mp\nm7B5.tmp
>>> qtdirs.cpp
>>> link /LIBPATH:"c:\Qt\4.6.2\lib" /NOLOGO /INCREMENTAL:NO /MANIFEST /MANIF
>>> ESTFILE:"release\qtdirs.intermediate.manifest" /SUBSYSTEM:WINDOWS "/MANIFESTDEPE
>>> NDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' p
>>> ublicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /OUT:re
>>> lease\qtdirs.exe @C:\Users\ADMINI~1\AppData\Local\Temp\nm92D.tmp
>>> mt.exe -nologo -manifest "release\qtdirs.intermediate.manifest" -outputr
>>> esource:release\qtdirs.exe;1
>>> release\qtdirs.exe
>>> Error Building Target: pyqt, cmd was: python configure.py -w
>>>
>>> -Justin
>>>
>>> On Tue, Sep 20, 2011 at 3:01 PM, Justin Ream <justi...@gmail.com> wrote:
>>>> Matthew - thanks for the reply. I'll be getting more information to
>>>> you after I finish up at my client site.
>>>>
>>>> Sent from my mobile device.
>>>>
>>>> On Sep 20, 2011, at 2:59 PM, Matthew Newell <newe...@gmail.com> wrote:
>>>>
>>>>> Unfortunately I haven't actually built arsenal suite on windows. At
>>>>> blur we still maintain our own internal subversion repo, which is
>>>>> somewhat diverged from the arsenalsuite code, although barry does a
>>>>> good job of keeping the core stuff merged.
>>>>>
>>>>> I am extremely busy for the next few weeks, but I will do what I can
>>>>> to get arsenalsuite built on windows.
>>>>>
>>>>> Could you tell me what compiler, OS version, Qt version you have tried
>>>>> builting with, and what errors you have encountered so far?
>>>>>
>>>>> Matt
>>>>>
>>>>> On Tue, Sep 20, 2011 at 12:36 PM, Justin Ream <justi...@gmail.com> wrote:
>>>>>> Hi -
>>>>>>
>>>>>> Any possibility of getting a Windows installer? If it is, would be
>>>>>> much appreciated!
>>>>>>
>>>>>> -Justin
>>>>>>
>>>>>> On Tue, Sep 20, 2011 at 8:54 AM, Justin Ream <justi...@gmail.com> wrote:
>>>>>>> Thanks Barry! I'm at least trying to demo the Linux product atm.
>>>>>>> I'll post about some of my trials on the mailing list and will start
>>>>>>> figuring out patching after I get that done.
>>>>>>>
>>>>>>> -Justin
>>>>>>>
>>>>>>> On Mon, Sep 19, 2011 at 5:05 PM, Barry Robison <barry....@gmail.com> wrote:
>>>>>>>> Hey Justin,
>>>>>>>>
>>>>>>>> Unfortanately I do not have up to date Windows builds. I've cc'd another dev
>>>>>>>> who supports a large Windows shop, he might have some installers handy.
>>>>>>>>
>>>>>>>> We'd certainly welcome any contributions you could offer. If you need commit
>>>>>>>> access, please do let me know.
>>>>>>>>
>>>>>>>> cheers,
>>>>>>>> -barry
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Sep 20, 2011 at 1:44 AM, Justin Ream <justi...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi Barry -
>>>>>>>>>
>>>>>>>>> I've been having a lot of problems with building on Windows, some of
>>>>>>>>> which seems to be easily fixable in the build system. I'd like to
>>>>>>>>> start making contributions for that at some point, and if you need
>>>>>>>>> someone to produce a Windows binary installer build I'd be very much
>>>>>>>>> interested in doing that in the future.
>>>>>>>>>
>>>>>>>>> Would you happen to have a working Windows build I could have a look
>>>>>>>>> at in the meantime? I need to get a hold of something today so I can
>>>>>>>>> demo the system to a client, and he's not interested in seeing the
>>>>>>>>> Linux build (which I seem to get through OK).
>>>>>>>>>
>>>>>>>>> -Justin
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>
>>
>
Matthew Newell
in that version of PyQt4, not your setup. I had the same problem
whenever it would configure it would pop up a dialog with that error,
but continue after I hit okay. In the current version that arsenal
has it pops up that error then fails to generate the source code and
errors. That should all be fixed once i sync to the latest version
that I have in blur's repo.
Matt
Justin Ream
-Justin
Matthew Newell
adjust which .pyd files are packaged in the .nsi file depending on
your Qt build options. It's giong to take me some time, probably 30
minutes to an hour to get the new files added and make sure everything
is properly merged before I can commit to a branch. I might be able
to get that done tonight if not I'll do it first thing tomorrow
morning.
Matt
Matthew Newell
the libs to compile. So far I've fixed up stone and pystone, should
have the rest working soon and I'll push the changes.
Matt
On Thu, Sep 22, 2011 at 4:00 PM, Justin Ream <justi...@gmail.com> wrote:
> Awesome. If anyone thinks it's needed, I'll maintain a Windows build
> for upload. Also - I can try to flesh out some of the documentation
> to start so I can contribute till I get up to speed on the codebase.
>
> -Justin
Justin Ream
changes hit in Mercurial soon?
-Justin
Matthew Newell
windows. I haven't tested the functionality of anything, and the
graphviz support is not compiled in on windows, though that can easily
be fixed. I'm giong to let you(Justin) take it from here, just ask if
you have any questions.
Matt
On Fri, Sep 23, 2011 at 4:28 PM, Matthew Newell <newe...@gmail.com> wrote:
> I just got the burner to build. Pushing the changes to the murcurial
> repo now.
> I believe you need to do hg pull; hg branch sip_pyqt_updates; hg update
Justin Ream
After updating to the sip_pyqt_updates branch; I get to here on the
PyQT4 compile:
<snip ...>
Checking to see if the dbus support module should be built...
DBus v1 does not seem to be installed.
Qt v4.6.2 free edition is being used.
SIP 4.12.4-snapshot-bbe43a0bad78 is being used.
The Qt header files are in C:\Qt\4.7.0\include.
The shared Qt libraries are in C:\Qt\4.7.0\lib.
The Qt binaries are in C:\Qt\4.7.0\bin.
The Qt mkspecs directory is in C:\Qt\4.7.0.
These PyQt modules will be built: QtCore, QtGui, QtHelp, QtMultimedia,
QtNetwork, QtDeclarative, QtOpenGL, QtScript, QtScriptTools, QtSql, QtSvg,
QtTest, QtWebKit, QtXml, QtXmlPatterns, phonon, QtDesigner, QAxContainer.
The PyQt Python package will be installed in C:\Python26\Lib\site-packages.
PyQt is being built with generated docstrings.
The Designer plugin will be installed in C:\Qt\4.7.0\plugins\designer.
The PyQt .sip files will be installed in C:\Python26\sip\PyQt4.
pyuic4, pyrcc4 and pylupdate4 will be installed in C:\Python26.
Generating the C++ source for the QtCore module...
"C:\Python26\sip" -w -o -x VendorID -t WS_WIN -x PyQt_OpenSSL -x PyQt_NoPrintRan
geBug -t Qt_4_6_2 -x Py_v3 -g -a QtCore.api -c C:\Users\Administrator\arsenalsui
te\cpp\lib\PyQt4\QtCore -b QtCore\QtCore.sbf -I C:\Users\Administrator\arsenalsu
ite\cpp\lib\PyQt4\sip C:\Users\Administrator\arsenalsuite\cpp\lib\PyQt4/sip/QtCo
re/QtCoremod.sip
Creating the Makefile for the QtCore module...
Generating the C++ source for the QtDeclarative module...
"C:\Python26\sip" -w -o -x VendorID -t WS_WIN -x PyQt_OpenSSL -x PyQt_NoPrintRan
geBug -t Qt_4_6_2 -x Py_v3 -g -a QtDeclarative.api -c C:\Users\Administrator\ars
enalsuite\cpp\lib\PyQt4\QtDeclarative -b QtDeclarative\QtDeclarative.sbf -I C:\U
sers\Administrator\arsenalsuite\cpp\lib\PyQt4\sip C:\Users\Administrator\arsenal
suite\cpp\lib\PyQt4/sip/QtDeclarative/QtDeclarativemod.sip
Error Building Target: pyqt, cmd was: python configure.py -w
</snip>
-Justin
Justin Ream
It looks like if I step down in to the PyQT4 directory and build from
there, the compiler barfs on code in QtNetwork:
cl -c -nologo -Zm200 -Zc:wchar_t- -O2 -MD -W3 -w34100 -w34189 -DNDEBUG
DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_NETWORK_LIB
-DQT_CORE_LIB -I. -IC:\Python26\include -IC:\Qt\4.7.0\mkspecs\default -IC:\Qt\4
7.0\include\QtNetwork -IC:\Qt\4.7.0\include\QtCore -IC:\Qt\4.7.0\include -Fo @C
\Users\ADMINI~1\AppData\Local\Temp\nmBF73.tmp
sipQtNetworkcmodule.cpp
C:\arsenalsuite\cpp\lib\PyQt4/sip/QtNetwork/qabstractsocket.sip(46) : error C20
5: 'sipName_QNetworkConfigurationManager' : undeclared identifier
C:\arsenalsuite\cpp\lib\PyQt4/sip/QtNetwork/qabstractsocket.sip(46) : error C20
5: 'sipType_QNetworkConfigurationManager' : undeclared identifier
C:\arsenalsuite\cpp\lib\PyQt4/sip/QtNetwork/qabstractsocket.sip(62) : error C20
5: 'sipName_QNetworkSession' : undeclared identifier
C:\arsenalsuite\cpp\lib\PyQt4/sip/QtNetwork/qabstractsocket.sip(62) : error C20
5: 'sipType_QNetworkSession' : undeclared identifier
sipQtNetworkQList0100QNetworkProxy.cpp
sipQtNetworkQList0100QNetworkInterface.cpp
sipQtNetworkQList0100QNetworkAddressEntry.cpp
sipQtNetworkQList0100QNetworkCookie.cpp
sipQtNetworkQList0100QHostAddress.cpp
sipQtNetworkQPair0100QHostAddress1800.cpp
sipQtNetworkQUrlInfo.cpp
sipQtNetworkQUdpSocketBindMode.cpp
sipQtNetworkQUdpSocket.cpp
sipQtNetworkQTcpSocket.cpp
sipQtNetworkQTcpServer.cpp
sipQtNetworkQNetworkRequest.cpp
sipQtNetworkQNetworkReply.cpp
sipQtNetworkQNetworkProxyFactory.cpp
sipQtNetworkQNetworkProxyQuery.cpp
sipQtNetworkQNetworkProxyCapabilities.cpp
sipQtNetworkQNetworkProxy.cpp
sipQtNetworkQNetworkInterfaceInterfaceFlags.cpp
sipQtNetworkQNetworkInterface.cpp
Generating Code...
Compiling...
sipQtNetworkQNetworkAddressEntry.cpp
sipQtNetworkQNetworkDiskCache.cpp
sipQtNetworkQNetworkCookieJar.cpp
sipQtNetworkQNetworkCookie.cpp
sipQtNetworkQNetworkAccessManager.cpp
sipQtNetworkQLocalSocket.cpp
sipQtNetworkquintptr.cpp
sipQtNetworkQLocalServer.cpp
sipQtNetworkQHttp.cpp
sipQtNetworkQHttpRequestHeader.cpp
sipQtNetworkQHttpResponseHeader.cpp
sipQtNetworkQHttpHeader.cpp
sipQtNetworkQHostInfo.cpp
sipQtNetworkQHostAddress.cpp
sipQtNetworkQFtp.cpp
sipQtNetworkQAuthenticator.cpp
sipQtNetworkQAbstractSocket.cpp
sipQtNetworkQAbstractNetworkCache.cpp
sipQtNetworkQNetworkCacheMetaData.cpp
sipQtNetworkQHash0100QNetworkRequestAttribute0100QVariant.cpp
Generating Code...
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0
VC\BIN\cl.EXE"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0
VC\BIN\nmake.exe"' : return code '0x2'
Stop.
If I skip QtNetwork, everything else in PyQT builds correctly.
However, when I move on to the rest of the build with
C:\arsenalsuite>build.py -color -command_only verbose clean build
install release sip:skip pyqt:skip freezer burner pyabsubmit abscripts
I get this:
Building: pystonestatic C:\arsenalsuite\cpp\lib\stone
Running Command: python configure.py -k
sip: Unable to find file "QtSql/QtSqlmod.sip"
Error Building Target: pystonestatic, cmd was:
python configure.py -k
-Justin
On Mon, Sep 26, 2011 at 6:33 PM, Matthew Newell <newe...@gmail.com> wrote:
> yeah i misread the error. you don't need QtDeclarative for anything in the repo.
>
> On Mon, Sep 26, 2011 at 6:24 PM, Justin Ream <justi...@gmail.com> wrote:
>> Matt - ok, removed, got to same error. If QtDeclarative is not
>> needed, I'll figure out how to remove it from being configured; if you
>> have another tip I'll try that.
>>
>> -Justin
>>
>> On Mon, Sep 26, 2011 at 5:39 PM, Matthew Newell <newe...@gmail.com> wrote:
>>> try deleting cpp/lib/PyQt4/sip/QtAssistant/QtAssistantmod.sip and
>>> recompiling. I just googled the error and it looks like QtAssistant
>>> stuff was removed for 4.7, not sure why configure.py would barf on
>>> that. I'll try to get a proper fix in soon.
>>>
>>> Matt