mirrors/winamp
Archived
1
0
Fork 0
Code
Iconic media player. Llama group was wide-publicly shamed for OSI licenses violations in this source code, disgusting very own strongly restrictive WPL and disrespect of open-source community principles. Github repo was created Sept, 24 of 2024 and removed after several weeks of well deserved criticism and massive flood/spam attack in issues. This mirrored repo is just a snapshot of historical artifact straight from GitHub. https://github.com/WinampDesktop/winamp
This repository has been archived on 2024-10-17. You can view files and clone it, but cannot push or open issues or pull requests.
52 Commits 3 Branches 0 Tags 2 GiB
C++ 54.7%
C 40.6%
NSIS 1.1%
Objective-C 0.8%
HTML 0.7%
Other 1.7%
83aa96afbe
Go to file
Greeniac1 83aa96afbe
Add more build tools AGAIN!
2024-09-27 03:21:04 +03:00
BuildTools Add more build tools AGAIN! 2024-09-27 03:21:04 +03:00
Src Delete Src/external_dependencies/libdiscid-0.6.2 directory 2024-09-26 16:58:42 +02:00
vcpkg-ports Initial community commit 2024-09-24 14:54:57 +02:00
.gitignore Adding .gitignore 2024-09-23 11:55:40 +02:00
automate-git.py Initial community commit 2024-09-24 14:54:57 +02:00
cef_x86.bat Initial community commit 2024-09-24 14:54:57 +02:00
install-packages.cmd chore: use "clean up" as verb instead of adjective, add space before dots 2024-09-26 09:58:05 +02:00
LICENSE.md chore: Update LICENSE to apply to v1.0.1 2024-09-26 09:41:43 +02:00
README.md Update README.md 2024-09-26 17:06:23 +02:00
vcpkg_version_finder.py Correct a spelling mistake 2024-09-24 20:08:55 +01:00
winampAll_2019.sln Initial community commit 2024-09-24 14:54:57 +02:00

README.md

Winamp

About

Winamp is a multimedia player launched in 1997, iconic for its flexibility and wide compatibility with audio formats. Originally developed by Nullsoft, it gained massive popularity with still millions of users. Its development slowed down, but now, its source code was opened to the community, allowing developers to improve and modernize the player to meet current user needs.

It really whips the llama's ass.

Usage

Building of the Winamp desktop client is currently based around Visual Studio 2019 (VS2019) and Intel IPP libs (You need to use exactly v6.1.1.035). There are different options of how to build Winamp:

  1. Use the build_winampAll_2019.cmd script file that makes 4 versions x86/x64 (Debug and Release). In this case, Visual Studio IDE is not required.
  2. Use the winampAll_2019.sln file to build and debug in Visual Studio IDE.

Dependencies

libdiscid

We take libdiscid from https://github.com/metabrainz/libdiscid/tree/v0.6.2, copy it in /Src/external_dependencies/libdiscid-0.6.2/

libvpx

We take libvpx from https://github.com/ShiftMediaProject/libvpx, modify it, and pack it to archive. Run unpack_libvpx_v1.8.2_msvc16.cmd to unpack.

libmpg123

We take libmpg123 from https://www.mpg123.de/download.shtml, modify it, and pack it to archive. Run unpack_libmpg123.cmd to unpack and process the DLLs.

OpenSSL

You need to use openssl-1.0.1u. For that, you need to build a static version of these libs. Run build_vs_2019_openssl_x86.cmd and build_vs_2019_openssl_64.cmd.

To build OpenSSL, you need to install:

DirectX 9 SDK

We take DirectX 9 SDK (June 2010) from Microsoft, modify it, and pack it to archive. Run unpack_microsoft_directx_sdk_2010.cmd to unpack it.

Microsoft ATLMFC lib fix

In file C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\atlmfc\include\atltransactionmanager.h

Go to line 427 and change from:

return ::DeleteFile((LPTSTR)lpFileName);

to:

return DeleteFile((LPTSTR)lpFileName);

Intel IPP 6.1.1.035

We take Intel IPP 6.1.1.035, modify it, and pack it to archive.

Run unpack_intel_ipp_6.1.1.035.cmd to unpack it.

Build Tools

Several external build tools are required to build Winamp. These tools are not bundled directly into the repository to comply with their respective licenses. You will need to download them separately from the following links:

Make sure to install these tools as part of your build environment. You may need to modify the build scripts to reflect the correct paths to these tools on your system.