Fedora 11 is nearly in beta, and thanks to some judicious cuts at the
end, we made it to 100% feature complete. Thanks to the many people
who helped out reviewing packages and testing.
What do we want to aim for in Fedora 12?
Some ideas - please add your own to this thread.
(1) Win64 support
(see: http://lists.fedoraproject.org/pipermail/fedora-mingw/2009-February/thread.… )
(2)? Use mingw-w64 project to build 32 bit w32api/runtime, since
mingw-w64 seems to be more active.
(3) Darwin / OS X support
(see: https://www.redhat.com/archives/fedora-devel-list/2009-March/msg00397.html )
(4) Get some of the issues resolved in the packaging guidelines:
http://fedoraproject.org/wiki/MinGW/Packaging_issues
(5) Expand active members, particularly packagers. I would like to
start by having a website which doesn't suck like our current one.
(6) Move educational materials to a single place.
(7) Have a FAQ.
(8) I'd like to have a reasonable Python story. I spent a lot of time
trying to get Python and Python libs to cross-compile, without any
success.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
Read my OCaml programming blog: http://camltastic.blogspot.com/
Fedora now supports 68 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
Hi all,
I'm pretty new to this packaging and cross-compiling, but I put
together a couple packages anyway:
http://jasonwoof.com/downloads/mingw32-SDL_image-1.2.6-1.fc11.src.rpmhttp://jasonwoof.com/downloads/mingw32-SDL_mixer-1.2.8-1.fc11.src.rpm
They seem to work quite well for me, but I don't really know what I'm
doing, so I'd appreciate more knowledgeable folk looking over my spec
files.
Here's what I did and where everything came from: (all in F11)
1) I set up my .rpmmacros so it would store sources in separate
directories by package name-version by adding this line:
%_sourcedir %{_topdir}/SOURCES/%{name}-%{version}
I was worried that multiple source rpms would have files in them with
the same name (which turned out to be the case) and I wanted to make
sure I could tell what packages what files came from.
2) I used yumdownloader to download source rpms for SDL SDL_mixer
SDL_image and SDL and installed them in my local rpmbuild tree
3) I duplicated SOURCES/SDL_image-1.2.6/ to SOURCES/mingw32-SDL_image-1.2.6/
4) I copied SPECS/mingw32-SDL-1.2.13.spec to SPECS/mingw32-SDL_image-1.2.6.spec
5) I edited that new spec file, mostly by looking at existing
SDL_image-1.2.6.spec and pulling useful parts from it. tweaking as
neccesary.
And basically did the same for SDL_mixer.
Some notes:
I didn't modify anything in the SOURCES folder (just copied whole
folders as described above).
I used all the patches that were used for the native versions.
I commented out lines to install (and build in one case) little
executable programs from both packages that I didn't understand the
point of.
I've cross-compiled my game (vor) which uses both of these libraries,
and it works great under wine. (Gets at least 40% better framerate
under wine than it does when compiled for linux.) Though I have not
tested them on Windows.
I have a fedoraproject.org account (so I can edit the wiki and such)
but don't have any connections or access or anything to get these into
the fedora distrobution. If/when they are ready, I'd love someone to
take care of this, or help me do it. Right now I don't even know what
the process is.
Looking forward to hearing your thoughts/feedback.
Take care, - Jason
Hi all,
In the last few weeks some issues have been raised which haven't been
resolved yet. As the development freeze for Fedora 12 is about to happen
in just over a month I want to propose a list of tasks which need to be
done before the Fedora 12 development freeze (the sooner the better). If
you think some items are missing from this list feel free to reply to
this message.
Update GCC
----------
Kalev Lember posted a message about this earlier today. The GCC version
which we currently use is a pre-release of GCC 4.4.0 so it's in
desperate need of an update. There's also a bugreport open about this at
[1].
Update to libjpeg 7
-------------------
At the moment we've got libjpeg-6 in the repository. This version of
libjpeg contains a typedef conflict as mentioned at [2]. Libjpeg-7 got
released recently and contains an (incomplete) fix for this problem. To
really solve this problem patches are required for libjpeg itself and
all dependent packages (libtiff, libjasper and gtk2). More about this in
the bugreport at [2].
Rename mingw32-pkg-config to i686-pc-mingw32-pkg-config
-------------------------------------------------------
Recently there was some discussion on this mailing list about improving
the compatibility with wine. One of the issues mentioned there was the
lack of a mingw-specific version of pkg-config. Right now we have a
script called mingw32-pkg-config, but this script doesn't get used when
using './configure --host=i686-pc-mingw32'. Therefore we need to rename
the mingw32-pkg-config script to i686-pc-mingw32-pkg-config. This change
shouldn't introduce any side effects. The corresponding bugreport about
this can be found at [3]. The bugreport at [4] may also be related to
this.
Debuginfo subpackages
---------------------
The discussion about this subject was done a while ago [5], but there
are still various mingw32 packages which lack debuginfo subpackages. For
packagers which didn't read that thread: In order to automatically
generate a -debuginfo subpackage you need to add 2 lines to your .spec
files:
%define __debug_install_post %{_mingw32_debug_install_post}
%{_mingw32_debug_package}
An example can be found at [6].
It should be doable to perform all these tasks this week. That should
give us enough time to test everything before the Fedora 12 development
freeze.
Regards,
Erik van Pienbroek
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=510949
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=497492
[3]: https://bugzilla.redhat.com/show_bug.cgi?id=513825
[4]: https://bugzilla.redhat.com/show_bug.cgi?id=509940
[5]:
http://lists.fedoraproject.org/pipermail/fedora-mingw/2009-June/001613.html
[6]:
http://cvs.fedoraproject.org/viewvc/rpms/mingw32-libsoup/devel/mingw32-libs…
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: .pc files for mingw32 library include the sysroot
https://bugzilla.redhat.com/show_bug.cgi?id=513826
Summary: .pc files for mingw32 library include the sysroot
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: mingw32-glib2
AssignedTo: rjones(a)redhat.com
ReportedBy: pbonzini(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: lfarkas(a)lfarkas.org, t.sailer(a)alumni.ethz.ch,
berrange(a)redhat.com, rjones(a)redhat.com,
fedora-mingw(a)lists.fedoraproject.org
Depends on: 513825
Classification: Fedora
Target Release: ---
Description of problem:
The paths in the .pc files for mingw32 include the
/usr/i686-pc-mingw32/sys-root component. This would prevent using them within
the MSYS shell, for example.
It would be more correct to install them without the path and, in a
i686-pc-mingw32-pkg-config (see bug 513825), provide the PKG_CONFIG_SYSROOT_DIR
variable. The script would work like this then:
#! /bin/sh
PKG_CONFIG_SYSROOT_DIR=`i686-pc-mingw32-gcc --print-sysroot`
prefix=$PKG_CONFIG_SYSROOT_DIR/mingw
PKG_CONFIG_LIBDIR=$prefix/lib/pkgconfig:$prefix/share/pkgconfig
export PKG_CONFIG_LIBDIR # PKG_CONFIG_SYSROOT_DIR
exec pkg-config "$@"
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: compiled mingw files include the sys-root path
https://bugzilla.redhat.com/show_bug.cgi?id=514187
Summary: compiled mingw files include the sys-root path
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: redhat-rpm-config
AssignedTo: jonathan(a)jonmasters.org
ReportedBy: pbonzini(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: lfarkas(a)lfarkas.org, t.sailer(a)alumni.ethz.ch,
berrange(a)redhat.com, pmatilai(a)redhat.com,
rjones(a)redhat.com, erik-fedora(a)vanpienbroek.nl,
jonathan(a)jonmasters.org,
fedora-mingw(a)lists.fedoraproject.org
Blocks: 513826
Classification: Fedora
Target Release: ---
Clone Of: 513826
+++ This bug was initially created as a clone of Bug #513826 +++
Description of problem:
The paths in the .pc files for mingw32 include the
/usr/i686-pc-mingw32/sys-root component. This would prevent using them within
the MSYS shell, for example.
It would be more correct to install them without the path and, in a
i686-pc-mingw32-pkg-config (see bug 513825), provide the PKG_CONFIG_SYSROOT_DIR
variable. The script would work like this then:
#! /bin/sh
PKG_CONFIG_SYSROOT_DIR=`i686-pc-mingw32-gcc --print-sysroot`
prefix=$PKG_CONFIG_SYSROOT_DIR/mingw
PKG_CONFIG_LIBDIR=$prefix/lib/pkgconfig:$prefix/share/pkgconfig
export PKG_CONFIG_LIBDIR # PKG_CONFIG_SYSROOT_DIR
exec pkg-config "$@"
--- Additional comment from pbonzini(a)redhat.com on 2009-07-26 15:15:36 EDT ---
To clarify: the paths work, but still they are not correct. Right now if I
want to install MSYS under Wine I have two choices:
1) I proceed as in bug 513819 so that the Fedora mingw root is visible under
MSYS. Then however I cannot use pkg-config under MSYS.
2) I copy everything from /usr/i686-pc-mingw32/sys-root/mingw under Wine's
c:/mingw, and then I lose all the updates that come through Fedora's package
manager. I also have to update the .pc files manually.
It's a lose-lose situation, and PKG_CONFIG_SYSROOT_DIR was meant exactly to
support this.
--- Additional comment from erik-fedora(a)vanpienbroek.nl on 2009-07-26 18:20:13
EDT ---
Why would you want to install MSYS under Wine? MSYS just provides some tools
which we already have native on Linux. The bash/sh from MSYS is also way slower
than native bash/sh
--- Additional comment from pbonzini(a)redhat.com on 2009-07-27 03:05:30 EDT ---
For testing. I want to make sure that there are no hidden bits in the
configure/make files that *only* work when crosscompiling (the typical example
is forgetting to quote a variable that could contain Windows \ paths).
Besides, the idea of a sysroot is to match *exactly* what would be on the
non-native system. I could take the Fedora sysroot and copy it to a real
Windows machine, and it should just work. Now instead if I do this and install
the Windows version of pkg-config, it will not work because the .pc files
contains pointers to the Fedora images.
This is not easy to fix (it is a "flag day" bug, you have to fix all packages
at once), so it may not have a high priority. But it is serious.
--- Additional comment from rjones(a)redhat.com on 2009-07-27 04:53:55 EDT ---
(In reply to comment #3)
> For testing. I want to make sure that there are no hidden bits in the
> configure/make files that *only* work when crosscompiling (the typical example
> is forgetting to quote a variable that could contain Windows \ paths).
>
> Besides, the idea of a sysroot is to match *exactly* what would be on the
> non-native system. I could take the Fedora sysroot and copy it to a real
> Windows machine, and it should just work. Now instead if I do this and install
> the Windows version of pkg-config, it will not work because the .pc files
> contains pointers to the Fedora images.
This isn't how we install on Windows at all. We use NSIS to
build installers.
And the aim of this project is to free developers from having to
use Windows at all, not to allow people to copy binaries onto a
Windows machine and continue development there.
The *.pc files contain the correct paths for cross-compiling
to a Windows host from a Fedora build system, which is precisely
the aim of this project.
--- Additional comment from pbonzini(a)redhat.com on 2009-07-28 04:36:53 EDT ---
Created an attachment (id=355373)
--> (https://bugzilla.redhat.com/attachment.cgi?id=355373)
redhat-rpm-config part of the patch
The remaining part is to change the packages to do a change similar to what the
patch does to %{_mingw32_makeinstall}.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502689
Jason Tibbitts <tibbs(a)math.uh.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag|fedora-cvs? |fedora-cvs+
--- Comment #11 from Jason Tibbitts <tibbs(a)math.uh.edu> 2009-08-31 19:15:53 EDT ---
CVS done.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502689
Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag| |fedora-cvs?
--- Comment #10 from Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> 2009-08-31 16:44:39 EDT ---
New Package CVS Request
=======================
Package Name: mingw32-cppunit
Short Description: MinGW Windows C++ unit testing framework
Owners: kwizart
Branches: devel F-11 EL-5
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502689
Kalev Lember <kalev(a)smartlink.ee> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag|fedora-review? |fedora-review+
--- Comment #9 from Kalev Lember <kalev(a)smartlink.ee> 2009-08-31 16:22:28 EDT ---
Adding a Requires line certainly counts as a change to the binary rpm. Anyway,
the package looks good now.
APPROVED
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=502689
--- Comment #8 from Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> 2009-08-31 11:36:10 EDT ---
Hi! I was just back from few days off this weekend...
I've updated the srpm/spec without bumping release because nothing was related
to the binary package itself.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.