hi, what's the plan about the mingw64 source selection? i mean there're a few source which can be choose as the base for the toolchain. - automated daily svn snapshot build (choosen by Erik for his repo) - or mingw64 releases with is still not too stable. - there are another branch cygwin which use some strange versions: 1.0b-svn4214-1 which i can't found in the svn (but this branch has a working d3d header files:-()
of course the best would be a stable 1.0 release...
Farkas Levente schreef op di 21-06-2011 om 16:28 [+0200]:
hi, what's the plan about the mingw64 source selection? i mean there're a few source which can be choose as the base for the toolchain.
- automated daily svn snapshot build (choosen by Erik for his repo)
- or mingw64 releases with is still not too stable.
- there are another branch cygwin which use some strange versions:
1.0b-svn4214-1 which i can't found in the svn (but this branch has a working d3d header files:-()
of course the best would be a stable 1.0 release...
Hi Levente,
Recently we already discussed about this subject on this mailing list. At first, I used the 1.0 branch of the mingw-w64 project. However, some packages, like wine-gecko (and you also mentioned gstreamer), depend on features only available in the trunk branch. The upstream mingw-w64 developers also indicated on this mailing list that the trunk branch should be stable as well. All major new development inside the mingw-w64 project seems to be done in an experimental branch and once features have stabilized, they're moved to the trunk branch. So with this statement, we decided to go with the trunk branch.
If you need to have certain features available for gstreamer I would suggest you to get in contact with the mingw-w64 developers and supply them with details what's missing to get gstreamer working. Once all required changes have been applied to the mingw-w64 trunk we can pull in a recent enough snapshot.
Kind regards,
Erik van Pienbroek