Any reason why there isn't a windows build on qt4.6.1?
Bill
on:
QWebSettings::globalSettings()-
>setAttribute(QWebSettings::LocalContentCanAccessRemoteUrls, true);
QWebSettings::globalSettings()-
>setAttribute(QWebSettings::LocalStorageEnabled, true);
But I don't want to go through the pain of trying to build on windows
if there are issues with the latest qt.
Thanks.
Benjamin Meyer
-Benjamin Meyer
Alexandre Bique
> As simple as no one has done it. If you have Qt 4.6.1 on Windows would you be able to generate an install?
With mingw on linux it's doable no ?
--
Alexandre Bique
Jason McKillican
>
> With mingw on linux it's doable no ?
Probably. I haven't tried cross-compiling with mingw in linux, but it
can definitely be built with mingw in windows - I built a 4.6.1 build
of 0.10.2 with mingw last night. No installer though, so I can use it
on computers without admin privileges.
I noticed last night something that seems unique to 4.6.1 - it tries
to write the path to moc.exe in MAKEFILE.release with backslashes (C:
\qt\4.6.1\bin\moc.exe) -- you have to flip them to forward slashes
otherwise mingw will see the forward slashes as escape chars and flip
out. I haven't had this problem with any previous version of QT
though.
-Jason McKillican
Bill
On Feb 13, 6:34 pm, Jason McKillican <jasonplusp...@jazybones.com>
wrote:
> > > As simple as no one has done it. If you have Qt 4.6.1 on Windows would you be able to generate an install?
Jason, don't spose you could write up a little guide?
I can build it fine in linux, but really need to build this on windows
with my changes (dont need an installer) but I'm struggling following
the guide on the wiki using nmake etc.
I'd be very appreciative of any pointers.
Thanks.
Jason McKillican
On Feb 17, 4:00 pm, Bill <bill.hedwo...@gmail.com> wrote:
> Jason, don't spose you could write up a little guide?
Sorry to take so long in getting back to you; things have been a
little crazy here.
Here's my ground-up guide. I tested this on Win7 Professional, as I
had been doing my builds (the same way) in an XP Pro VM. Just used
this setup to build the latest Git pull (1386 82de949) of Arora. I
build against MingW instead of the MS Visual C runtime, so I can just
dump the DLLs to a folder and run Arora without installation on any
Win PC.
There's probably a good bit of redundancy in the initial build
environment setup. I didn't have much time to spend setting up MinGW/
MSYS so I just sort of threw everything I thought I'd need in.
*** Set up MSYS and MingW (based loosely off http://www.mingw.org/wiki/MSYS
and off trial & error) ***
1) Install the MSYS base system. I set my extract path to: 'C:\MSYS
\1.0\'
2) Install the MSYS DTK (dev toolkit). I installed it to: 'C:\MSYS
\1.0'
3) I then used the MinGW automated installer to grab MingW itself.
• In the installer, I chose: 'Latest' version
• I chose to install 'g++' & 'mingw make'
• installed to 'C:\msys\1.0\mingw'
4) I then went and grabbed the package for GCC4 (gcc-full from the
MingW SourceForge page -- http://sourceforge.net/projects/mingw/files/)
I did this because I later found my install had been missing some
files.
• Extract the archive to 'C:\msys\1.0\mingw'
5) Next, grab MSYS RXVT, BASH, CoreUtils, m4, make, & vim (or any
other text editor you'd like) from the MinGW sourceforge page.
• Extract to 'C:\MSYS\1.0'
6) I then installed MSYS GIT: http://msysgit.googlecode.com/files/Git-1.6.5.1-preview20091022.exe
*** First run of MSYS ***
Run MSYS: C:\msys\1.0\msys.bat
Ensure gcc 4.4.0 -- 'gcc -dumpversion'
Check your path to ensure the MinGW and MSYS paths were added -- 'echo
$PATH'
*** Install QT ***
Install QT; I used the LGPL version, framework only (MinGW build).
During the install, it will ask for an MinGW installation - point it
at 'C:\msys\1.0\mingw' & say yes to the error.
*** Set up ~.profile in MSYS so the build environment works in future
***
1) Open MSYS
2) 'export TERM=xterm'
3) 'export PATH=$PATH:/c/Program\ Files\ \(x86\)/Git/bin:/c/Qt/4.6.2/
bin'
(you can also click on the console window's icon, choose 'properties'
and check 'quick edit mode' to allow cut/paste - this is strictly a
Windows CLI thing)
'vim ~/.profile', add:
TERM=xterm
PATH=$PATH:/c/Program\ Files\ \(x86\)/Git/bin:/c/Qt/4.6.2/bin
(the TERM command is because VIM will barf if left with MSYS' default
TERM setting. You can leave this be if you're using another editor)
Finally, here are the meat & potatoes. Once you've done the initial
environment set-up, here's how to build and zip-package Arora:
*** Building Arora ***
1) Create a working directory (in this case, C:\build): 'mkdir /c/
build"
2) cd into the working directory and follow step 3 from the Beginner's
Instructions (GITing and building Arora):
http://code.google.com/p/arora/wiki/BeginnerStepByStepInstructions
• If you build as a release, there's a bug somewhere in the build
process (I think maybe with qmake) that causes Makefile.release to use
Windows backslash path separators (escape characters to the MinGW
utils) instead of forward slashes.
• 'make release' will fail; let it fail, then simply edit 'C:\build
\arora\src\Makefile.release"
>> replace all instances of 'C:\Qt\4.6.2\bin/moc.exe' with '/C/Qt/
4.6.2/bin/moc.exe'
• Restart 'make release'.
Once the build finishes, you should be able to run Arora from the
current folder using your MSYS terminal: './arora.exe'
*** Copying to a Folder / Making a Zip package *** (make sure you
check license compatibility issues if you distribute!)
1) Create a folder to dump everything into (say, for example: 'C:
\Program Files (x86)\arora\' as is my case)
Copy the following files into the folder:
• from C:\msys\1.0\mingw\bin:
libgcc_s_dw2-1.dll
mingwm10.dll
• from C:\qt\<version>\bin:
QtCLucene4.dll
QtCore4.dll
QtGui4.dll
QtMultimedia4.dll
QtNetwork4.dll
QtOpenGL4.dll
QtScript4.dll
QtScriptTools4.dll
QtSql4.dll
QtSvg4.dll
QtWebKit4.dll
QtXml4.dll
QtXmlPatterns4.dll
phonon4.dll
• from C:\qt\<version>\plugins:
codecs\
graphicssystems\
iconengines\
imageformats\
phonon_backend\
sqldrivers\
(you can delete all the files whose names are food.dll instead of
foo.dll -- these are debug versions)
• and from an existing arora install:
libeay32.dll & ssleay32.dll -- only because I haven't been able to get
openssl to compile yet in windows under mingw, and don't have Visual C
set up to build OpenSSL.
And there you go!
Jason McKillican
This guide comes in two main parts, the initial environment set-up and
then building/packaging Arora.
============== Initial MinGW/MSYS Environment Set-Up ============
*** Installing MSYS & MingW *** (This is based loosely off
http://www.mingw.org/wiki/MSYS and off trial & error. All packages
are downloaded from the MinGW/MSYS directory listing on SourceForge:
http://sourceforge.net/projects/mingw/files/)
1. Install the MSYS Base System; I extracted to 'C:\MSYS\1.0'
2. Install the MSYS DTK (Dev Tool Kit); I installed to ''C:\MSYS\1.0'
3. Using the MinGW Automated Installer
• When prompted for the version to use, choose 'Latest'
• For install options, choose 'g++' & 'mingw make'; install to
'C:\msys\1.0\mingw'
4. Download GCC version 4 (the gcc-full package); extract to 'C:\msys
\1.0\mingw'
5. The MSYS startup script seemed to want the following packages.
Just download & extract.
• MSYS RXVT, BASH, CoreUtils, m4, make, vim (or another editor of
your choosing); extract to 'C:\MSYS\1.0'
6. Next, install MSYS GIT: http://msysgit.googlecode.com/files/Git-1.6.5.1-preview20091022.exe
*** First run of MSYS ***
1. Run MSYS: ' C:\msys\1.0\msys.bat'
2. Ensure that you actually got gcc 4.4.0; I noticed the automated
installer still pushed v2 or v3
• 'gcc -dumpversion'
3. Check your path to ensure that MSYS and MinGW were added correctly
via the startup script
• 'echo $PATH'
*** Installing QT ***
You'll want to download the MinGW build of QT (http://qt.nokia.com).
I suppose you could use the entire SDK, but I just downloaded the
framework only. When installing, point it at 'C:\msys\1.0\mingw' and
say 'yes' to the error.
*** Save MSYS environment variables in ~/.profile***
If you installed VIM, it will not display properly given MSYS' default
TERM value. I set mine to xterm and it worked correctly.
• 'export TERM=xterm'
To avoid having to close/re-open the MSYS window after setting up
~/.profile, go ahead and add git and QT to the PATH. (In my case, I'm
using QT 4.6.2)
• 'export PATH=$PATH:/c/Program\ Files\ \(x86\)/Git/bin:/c/Qt/
4.6.2/bin'
You can also click on the console window's icon, choose 'properties'
and check 'quick edit mode' to allow cut/paste. This is just a
Windows command line interpreter trick.
Now, edit your ~/.profile and add:
TERM=xterm
PATH=$PATH:/c/Program\ Files\ \(x86\)/Git/bin:/c/Qt/4.6.2/bin
Finally, create a working build directory. (I used 'C:\build')
• 'mkdir /c/build'
*** Building Arora ***
1. cd into the working directory and follow step 3 of the Arora build
guide: http://code.google.com/p/arora/wiki/BeginnerStepByStepInstructions
• 'git clone git://github.com/Arora/arora.git'
• 'cd arora'
• 'qmake'
• 'make'
2. 'make release' will fail. This is due to a bug or
misconfiguration in (I believe) qmake that writes a Windows style path
to MOC.exe inside Makefile.release. To fix this, you'll need to edit
'c:\build\arora\src\makefile.release' to replace all instances of 'C:
\Qt\4.6.2\bin/moc.exe' with '/C/Qt/4.6.2/bin/moc.exe'
3. Now, restart 'make release' and all should be well.
4. Once Arora has built, you can launch it from the MSYS console or
copy files into a folder.
*** Copying to a folder / Making a compressed archive *** (make sure
to check licensing compatibility if you distribute!)
1. Create a destination folder: (in my case, I put it in 'C:\Program
Files (x86)\Arora')
2. From your MingW folder ('C:\msys\1.0\mingw\bin'), you'll need:
• libgcc_s_dw2-1.dll
• mingwm10.dll
3. From your QT folder ('C:\qt\<version>\bin') you'll need:
• QtCLucene4.dll
• QtCore4.dll
• QtGui4.dll
• QtMultimedia4.dll
• QtNetwork4.dll
• QtOpenGL4.dll
• QtScript4.dll
• QtScriptTools4.dll
• QtSql4.dll
• QtSvg4.dll
• QtWebKit4.dll
• QtXml4.dll
• QtXmlPatterns4.dll
• phonon4.dll
4. From 'C:\qt\<version>\plugins you'll need':
• codecs\
• graphicssystems\
• iconengines\
• imageformats\
• phonon_backend\
• sqldrivers\
(NOTE: for a release build, you can skip all the files whose names are
food.dll instead of foo.dll -- these are debug versions)
5. Finally, from an existing arora install:
• libeay32.dll
• ssleay32.dll
(This is because I haven't been able to get OpenSSL to compile yet in
Windows using MinGW. I also don't have Visual Studio installed to
build it using the instructions here: http://code.google.com/p/arora/wiki/BuildingOnWindows)
If you're making a portable version of Arora, you can also copy any
plugins into a 'plugins' folder in your Arora directory.
And there you have it. My Arora install guide. Just used my build
environment to build the latest Git pull (1386 82de949).
Jason McKillican
• 'export TERM=xterm'
On Mar 22, 6:56 pm, Jason McKillican <jasonplusp...@jazybones.com>
wrote:
> So I just wrote a nice install guide, and I'm not sure if it got eaten
> when I clicked 'Send' or not.
>
> On Feb 17, 4:00 pm, Bill <bill.hedwo...@gmail.com> wrote:
>
>
>