- 2Introduction
- 3Suggestions & Successes
Wine Winamp Reviews
Winamp supports music playback using MP3, MIDI, MOD, MPEG-1 audio layers 1 and 2, AAC, M4A, FLAC, WAV, and WMA. Winamp was one of the first widely used music players on Windows to support playback of Ogg Vorbis by default. It supports gapless playback for MP3 and AAC and ReplayGain for volume leveling across tracks.
- Winamp is the wine amongst music players: the longer it stays around, the better it impresses. This great application is now available for your tiny pocket devices. The developers took their time when converting Winamp for android devices. The app looks gorgeous and is perfectly compatible with the pc version.
- WACUP (which can be pronounced as wakeup or wac-up or however you prefer it in your native tongue) is designed to work only with the patched Winamp 5.666 release to provide bug fixes, updates of existing features and most importantly new features with the goal to eventually become it's own highly Winamp compatible media player. WACUP makes use of the benefits of Winamp being heavily based on.
- It's the best for professionalVSTplugins - setting winamp: in Shibatch mpg123 24 bits, out Otachan Asio (dll version), dsp VST Winamp Bridge with load 'Xlutop Chainer v1.03' and inside 1) input set Asio,2)T-Racks(Eq + Comp+ Limiter+ Clipper), 3)Analyzer Elemental Audio IXL Multimeter.Hardware: Xoner D2 + Z5500THE BEST SOUND!!!!Thank u Christian Budde.Winamp plays well again!!!!
- Winamp 5.666 Download: Official recommended Winamp 5.666 Build 3516 installers. Refer to the Winamp Forums for full info and changelog. Patched Installer Downloads. Winamp 5.666 Full (US English version) Winamp 5.666 Full (Multi-national installer) Winamp 5.666 Lite (basic 2.x-style mp3/cd player).
Motto: The journey of a thousand miles starts with a single step.
Theoretically, any Win32 app should be compilable out of the box under Wine. This, of course, is not the case. We have incompatible headers, and a bunch of other problems described in Winelib User's Guide. A good way to fix these is to try to compile applications for which we have the source under Winelib.
Why
But what do we hope to achieve? Well, the purpose of this project is four-fold:
- Document our experience on porting these applications to Winelib
- Improve Winelib based on the above such that the porting process becomes very simple
- Update the Winelib User's Guide to the latest porting process
- Fixing header and library problems in the process.
Where
There are many such apps around, and a lot of them are hosted at SourceForge. There are over 10,000 apps listed as running under Windows OS. All of the above have publicly available source code, and most are decent candidates for this project.
Obviously, we cannot start porting all these applications. We have to pick a few important ones, and work with those.
How
Compiling apps under Winelib should theoretically involve only makefile changes. In practice, you will encounter header problems, and the likes -- for these it is much better (and faster) to submit a patch, rather than document them. So for the remainder of the section, let's assume the Wine headers are good enough for the application in question.
We are now faced with adapting the build process to Wine's needs. As things stand today, we have to make another assumption: you aim at compiling the application using the GNU toolchain (gmake, gcc, ld, etc.). In theory, it should be possible to accomplish this with other tools, but at this point this is a rather unexplored territory. That being said, we now distinguish two large application classes:
Non-GNU tools build process
For these, winemaker does a decent job of generating a build system. I will not cover this type of applications here, for the time being. Please refer to the winemaker documentation for more information.
GNU tools based build process
Fortunately, most OSS applications have a build system based around the MinGW tool chain. Sometimes they have alternative build systems for the Borland and/or Microsoft tools, but more often than not they have to support the MinGW tools out of necessity.
What
If you know of an application that could be listed here, please add it.
Here is a list of programs that have been suggested for porting or already ported with Winelib
Suggested, No Active Worker
- CD-DA X-Tractor at [1]
- CDex at [2]
- DX SDK Examples at [3]
- Easy Code at [4]
- Gimp at [5]
- LibreOffice at [6]
- Ultimate++ at [7]
- VirtualDub at [8]
In Progress
- ATL
- Firefox at [9]
- TeXnicCenter at [10]
- WinAMP at [11]
Mostly Works
- MFC
- AbiWord at [12]
- CoolPlayer at [13]
- GNU Winboard at [14]
- WinVi at [15]
Done
- Petzold's Examples at [16]
- PuTTY at [17]
- Visual MinGW at [18]
- 2Introduction
- 3Suggestions & Successes
Motto: The journey of a thousand miles starts with a single step.
Theoretically, any Win32 app should be compilable out of the box under Wine. This, of course, is not the case. We have incompatible headers, and a bunch of other problems described in Winelib User's Guide. A good way to fix these is to try to compile applications for which we have the source under Winelib.
Why
But what do we hope to achieve? Well, the purpose of this project is four-fold:
- Document our experience on porting these applications to Winelib
- Improve Winelib based on the above such that the porting process becomes very simple
- Update the Winelib User's Guide to the latest porting process
- Fixing header and library problems in the process.
Where
There are many such apps around, and a lot of them are hosted at SourceForge. There are over 10,000 apps listed as running under Windows OS. All of the above have publicly available source code, and most are decent candidates for this project.
Obviously, we cannot start porting all these applications. We have to pick a few important ones, and work with those.
How
Compiling apps under Winelib should theoretically involve only makefile changes. In practice, you will encounter header problems, and the likes -- for these it is much better (and faster) to submit a patch, rather than document them. So for the remainder of the section, let's assume the Wine headers are good enough for the application in question.
We are now faced with adapting the build process to Wine's needs. As things stand today, we have to make another assumption: you aim at compiling the application using the GNU toolchain (gmake, gcc, ld, etc.). In theory, it should be possible to accomplish this with other tools, but at this point this is a rather unexplored territory. That being said, we now distinguish two large application classes:
Non-GNU tools build process
For these, winemaker does a decent job of generating a build system. I will not cover this type of applications here, for the time being. Please refer to the winemaker documentation for more information.
GNU tools based build process
Fortunately, most OSS applications have a build system based around the MinGW tool chain. Sometimes they have alternative build systems for the Borland and/or Microsoft tools, but more often than not they have to support the MinGW tools out of necessity.
What
If you know of an application that could be listed here, please add it.
Here is a list of programs that have been suggested for porting or already ported with Winelib
Suggested, No Active Worker
- CD-DA X-Tractor at [1]
- CDex at [2]
- DX SDK Examples at [3]
- Easy Code at [4]
- Gimp at [5]
- LibreOffice at [6]
- Ultimate++ at [7]
- VirtualDub at [8]
In Progress
- ATL
- Firefox at [9]
- TeXnicCenter at [10]
- WinAMP at [11]
Mostly Works
Wine Winamp Download
- MFC
- AbiWord at [12]
- CoolPlayer at [13]
- GNU Winboard at [14]
- WinVi at [15]
Done
- Petzold's Examples at [16]
- PuTTY at [17]
- Visual MinGW at [18]