4:54 a.m.
Hello,
I'm Krita developer, which is KDE graphics program, it is part of KOffice. I
would like to use cross compiler from FC11 to cross-compile KOffice for Windows.
Mainly Krita, but I will try to compile full KOffice.
I would like to ask you for help. I'm pretty much newbie in this area.
I managed to cross-compile the tictactoe example from [1]
So far I noticed that there is Qt package in repositaries
mingw32-qt.noarch
mingw32-qt-qmake
So I suppose I don't have to build Qt.
I need to build:
kdelibs 4.2.x at least
kdebase/runtime 4.2.x
kdepimlibs 4.2.x
lcms 1.18
libeigen 2.0
libexiv 0.16
libqimageblitz
I'm using 32 bit system. Have you got idea how to build kdelibs and basically
any cmake based project?
Thanks
Lukas Tvrdy
[1] https://fedoraproject.org/wiki/Using_the_Windows_cross-
compiler_Classroom_(20090308)
4:21 a.m.
On Tue, Aug 18, 2009 at 11:54:13AM +0200, LukasT.dev(a)gmail.com wrote:
Hello,
I'm Krita developer, which is KDE graphics program, it is part of KOffice. I
would like to use cross compiler from FC11 to cross-compile KOffice for Windows.
Mainly Krita, but I will try to compile full KOffice.
I would like to ask you for help. I'm pretty much newbie in this area.
I managed to cross-compile the tictactoe example from [1]
So far I noticed that there is Qt package in repositaries
mingw32-qt.noarch
mingw32-qt-qmake
So I suppose I don't have to build Qt.
I need to build:
kdelibs 4.2.x at least
kdebase/runtime 4.2.x
kdepimlibs 4.2.x
lcms 1.18
libeigen 2.0
libexiv 0.16
libqimageblitz
I'm using 32 bit system. Have you got idea how to build kdelibs and
basically any cmake based project?
cmake-based projects should just work. We have a %{_mingw32_cmake}
RPM macro and a mingw32-cmake program (in sufficiently new releases).
You're better off trying to build them and seeing what errors you get.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 75 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
9:42 a.m.
On Wednesday 19 August 2009 11:21:44 Richard W.M. Jones wrote:
On Tue, Aug 18, 2009 at 11:54:13AM +0200, LukasT.dev(a)gmail.com
wrote:
> Hello,
>
> I'm Krita developer, which is KDE graphics program, it is part of
> KOffice. I would like to use cross compiler from FC11 to cross-compile
> KOffice for Windows. Mainly Krita, but I will try to compile full
> KOffice.
>
> I would like to ask you for help. I'm pretty much newbie in this area.
> I managed to cross-compile the tictactoe example from [1]
> So far I noticed that there is Qt package in repositaries
>
> mingw32-qt.noarch
> mingw32-qt-qmake
>
> So I suppose I don't have to build Qt.
>
> I need to build:
> kdelibs 4.2.x at least
> kdebase/runtime 4.2.x
> kdepimlibs 4.2.x
> lcms 1.18
> libeigen 2.0
> libexiv 0.16
> libqimageblitz
>
> I'm using 32 bit system. Have you got idea how to build kdelibs and
> basically any cmake based project?
cmake-based projects should just work. We have a %{_mingw32_cmake}
RPM macro and a mingw32-cmake program (in sufficiently new releases).
Where can I get them? Are they somewhere in testing repos?
How those rpms are named?
Can you give me an example how to cross-compile with cmake?
Lukas
10:15 a.m.
with a fedora 10, 11 or rawhide
try
yum -y install mingw32\*
mingw32-configure
mingw32-make
Where can I get them? Are they somewhere in testing repos?
How those rpms are named?
Can you give me an example how to cross-compile with cmake?
Lukas
--
------------
Itamar Reis Peixoto
e-mail/msn: itamar(a)ispbrasil.com.br
sip: itamar(a)ispbrasil.com.br
skype: itamarjp
icq: 81053601
+55 11 4063 5033
+55 34 3221 8599
11:36 a.m.
On Wednesday 19 August 2009 17:15:58 Itamar Reis Peixoto wrote:
with a fedora 10, 11 or rawhide
try
yum -y install mingw32\*
mingw32-configure
mingw32-make
CMake is not configure.
Just to ensure you, I tried what you suggested in kdelibs-4.3.0/
I thought that there will be something like mingw32-cmake but there is not..
Any idea?
./mingw32-configure
getopt: unrecognized option '--cache-file=mingw32-config.cache'
getopt: unrecognized option '--host=i686-pc-mingw32'
getopt: unrecognized option '--build=i686-pc-linux-gnu'
getopt: unrecognized option '--target=i686-pc-mingw32'
getopt: unrecognized option '--exec-prefix=/usr/i686-pc-mingw32/sys-root/mingw'
getopt: unrecognized option '--localstatedir=/usr/i686-pc-mingw32/sys-
root/mingw/var'
getopt: unrecognized option '--sharedstatedir=/usr/i686-pc-mingw32/sys-
root/mingw/com'
KDE4 uses the CMake (http://www.cmake.org) buildsystem instead of configure.
CMake uses different options than configure, but some have direct equivalents:
<srcdir> : the source directory
--prefix=<dir> : -DCMAKE_INSTALL_PREFIX:PATH=<dir>
--bindir=<dir> : -DBIN_INSTALL_DIR:PATH=<dir>
--includedir=<dir> : -DINCLUDE_INSTALL_DIR:PATH=<dir>
--libdir=<dir> : -DLIB_INSTALL_DIR:PATH=<dir>
Once CMake has run successfully, you can use "make edit_cache" to view and
modify all settings.
For more information visit
"http://techbase.kde.org/Development/Tutorials/CMake#Run_CMake"
Your current configure options translate more or less to:
cmake -DCMAKE_INSTALL_PREFIX:PATH='/usr/i686-pc-mingw32/sys-root/mingw' -
DBIN_INSTALL_DIR:PATH='/usr/i686-pc-mingw32/sys-root/mingw/bin' -
DLIB_INSTALL_DIR:PATH='/usr/i686-pc-mingw32/sys-root/mingw/lib' -
DINCLUDE_INSTALL_DIR:PATH='/usr/i686-pc-mingw32/sys-root/mingw/include' . ;
make ; make install
5:01 a.m.
On Thu, Aug 20, 2009 at 06:36:46PM +0200, LukasT.dev(a)gmail.com wrote:
On Wednesday 19 August 2009 17:15:58 Itamar Reis Peixoto wrote:
> with a fedora 10, 11 or rawhide
>
> try
>
>
> yum -y install mingw32\*
>
> mingw32-configure
> mingw32-make
>
CMake is not configure.
Yes - the above advice is wrong. Just use the macros that I
suggested in my earlier reply.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
9:34 a.m.
Yes - the above advice is wrong. Just use the macros that I
suggested in my earlier reply.
Rich.
Rich, the macros are for RPM. I'm not packager nor I have experiences with
packaging or RPM.
Can you give me exact command or show me example how to use that macro or the
program you mentioned in the first replay?
Thanks
2:39 a.m.
LukasT.dev(a)gmail.com wrote:
On Wednesday 19 August 2009 11:21:44 Richard W.M. Jones wrote:
> On Tue, Aug 18, 2009 at 11:54:13AM +0200, LukasT.dev(a)gmail.com wrote:
>> I'm using 32 bit system. Have you got idea how to build kdelibs and
>> basically any cmake based project?
> cmake-based projects should just work. We have a %{_mingw32_cmake}
> RPM macro and a mingw32-cmake program (in sufficiently new releases).
Where can I get them? Are they somewhere in testing repos?
mingw32-cmake script was introduced to mingw32-filesystem starting from
version 51-1, which is only available in rawhide. I am afraid you are
out of luck for F-10 and F-11 installations at this time.
How those rpms are named?
Can you give me an example how to cross-compile with cmake?
On a rawhide installation you probably need to do something like that:
sudo yum install mingw32-gcc-c++ mingw32-qt
cd <your_app_dir>
mkdir build
cd build
mingw32-cmake ..
make
However I haven't tried to actually crosscompile anything using
mignw32-cmake myself, so there might be some more tricks involved.
Compiling qt apps with qmake need QT_LIBINFIX=4 set [1], and for that
reason cmake might not be able to find Qt out of the box.
[1]
https://fedoraproject.org/wiki/MinGW/Tips#Compiling_QT_applications_and_l...
--
Kalev
3:57 p.m.
LukasT.dev(a)gmail.com wrote:
So far I noticed that there is Qt package in repositaries
mingw32-qt.noarch
mingw32-qt-qmake
So I suppose I don't have to build Qt.
Unfortunately, the current mingw32-qt is built without some components
required by KDE (notably QtDBus, we also don't have a mingw32-dbus yet), so
you'll need your own.
I've had success in the past (I haven't tried it for a while, but it should
still work) with filling a buildroot with the MinGW binaries from the kdewin
project and using that.
1. Fetch the ZIP files you need from:
http://www.winkde.org/pub/kde/ports/win32/releases/stable/4.3.0/
AFAIK, the difference between the "mingw" and "mingw4" packages is
that
mingw uses SJLJ exceptions (and GCC 3.4, but that's binary-compatible with
GCC 4.x), mingw4 uses DWARF2 exceptions.
2. Mass-unzip them to an empty directory.
3. Set up your cross toolchain to look in that directory for libraries etc.
Kevin Kofler
5359
days inactive
5371
days old
8 comments
5 participants
participants (5)
-
itamar -
Kalev Lember -
Kevin Kofler -
LukasT.dev＠gmail.com -
Richard W.M. Jones