Snapshot of KDE 4.10 build environment (MinGW, 32bit)

[Patrick Spendrin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 05.05.2013 09:44, schrieb Thomas Friedrichsmeier:
> Hi!
> 
> At the moment, setting up a KDE 4.10 build environment using emerge
> should - probably - work rather well. Nonetheless, this might no
> longer be true in a few months (when various download links have
> moved, etc.), or perhaps you simply want a shortcut to setting up
> your KDE 4.10 build environment. Thus, here's a link to an archive
> of mine (including some details and instructions):
> 
> http://sourceforge.net/projects/rkwardextras/files/Windows/Development/
>
>  This is an emerge build of the 4.10 branch using MinGW4, on a
> 32bit WinXP. It does not include everything, but among others,
> kdelibs, kate, kde-runtime and all dependencies are already in the
> archive. Anything other packages you need, you can add yourself
> using emerge. Of course, if you want to use another compiler /
> architecture, this archive is not going to be of any use to you.
> 
> This archive was created shortly before the 4.10.2 release.
> Therefore, this _should_ be suitable for building binaries that
> will work with the released (MinGW4) binaries. (I have not found
> the time to test this, myself, yet).

Hm, the problem of these kind of setups is, as you noted, that you are
restricted to a certain specific setup and you add the builds themselves.
I propose a different solution for the future:
1) we somehow store the source files & make them downloadable as a
complete package (e.g. winkde-tools-4.10.2.7z +
winkde-win32libs-4.10.2.7z + ...) which you simply can unpack into
your download directory.
2) using those packages, one can make up ones own distribution by
simply making a csv file (like the ones in
emerge\server\serverconfig): rkward-4.10.2.txt which contains only
references to tarball targets.
The (re-)build process would look like that:
- - setup emerge (setting EMERGE_OFFLINE=True)
- - get the source & tool tarballs that were saved for that release.
- - run 'emerge --list-file=rkward-4.10.2.txt'
- - have the base for developing on top of KDE on Windows.

alternative solution: we make it possible that emerge can directly
rebuild from the source packages made for the installer; this is not
that easy since all patches are already applied, and some other
packages simply move stuff around etc. and we only get the resulting
packages.

regards,
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRhsgiAAoJELpJVkl28PNQxtoH/2J75jRdDhe16zVUhoOT4+np
QUb0CLHsfqbaOpOcDCoXihwtSnJt/ogbD88Zd6IiF3Vnol3iThgdRZbH50blbi8c
CLuNh874i0ggklF4gHk4VQ0nUK7nnmKyUiZhvSOgDX+vmVT4WIKyFxlY4WrwcnuN
be6FPdntSOxuBFkT3I+1aTUkrW9vmK7xzKcJDn3qM93jMeaHMJ2Oa0ZKxys+6fIo
h/1WjgiEzsCGr7NRkBuX/Qdb9YKeTZkgYssS/4eVbAPPEd/hPV6BtOgml2wqydrF
xdx5zRLZ8m3er6T2essU8/548UoNzVxwDPy/U4pYxiUh+Q7yqrvigpsm+m420k0=
=Kyyb
-----END PGP SIGNATURE-----