Right-click on your project (the folder called 'gen_myplugin' in the Solution Explorer window on the left) and select Properties.Since these are references, these values become available for use by the plugin.īy default Visual Studio removes some files we need to compile our code. As part of loading the plugin, the Winamp.exe will store the handle to its main window and the hinstance for the plugin dll into these two fields. This is the method that the Winamp.exe calls when loading these gen_*.dll files. You might have noticed the reference that is returned as part of the winampGetGeneralPurposePlugin() method. You might be wondering why the last two fields in the winampGeneralPurposePlugin structure are left empty. #ifndef gen_myplugin_h //- #define gen_myplugin_h #include // plugin version (don't touch this) #define GPPHDR_VER 0x10 // plugin name/title (change this to something you like) #define PLUGIN_NAME "My first generic Winamp plugin!" // main structure with plugin information, version, name.
#WINAMP WIKI CODE#
If you double-click to view them you should see code that looks something like this: The main files we want to work with are called 'gen_myplugin.h' and 'gen_myplugin.cpp'. Once you click okay Visual Studio should create a bunch of boilerplate code for you, and throw some files in your project with names like "resource.h", "stdafx.h", "AssemblyInfo.cpp", and so on. Be sure to start your plugin name with 'gen_' to make it work properly.Īll of the examples in this guide will assume you named your plugin 'gen_myplugin', but you can call it whatever you like as long as it starts with 'gen_' (for generic plugin) and ends with '.dll'. Thus, to make our basic plugin we want to name the first part of the file 'gen_'. This saves time and space instead of loading all dlls and then detecting which ones are real plugins).
#WINAMP WIKI .DLL#
dll filename, so you will need to properly name the file if you want Winamp to recognize it (details: the Winamp client searches for and loads plugins based on the first part of their filenames. Note: Winamp classifies plugins based on the first part of their.
When Visual Studio opens, select File -> New -> Project.Launch Visual Studio by clicking Start -> Programs -> Microsoft Visual C++ Express Edition -> Microsoft Visual C++ Express Edition.In Visual Studio this is called a 'project'. The first thing we need to do is create a place to store our code. Double-click the file (it's probably called something like 'vcsetup.exe') and run the installer.You'll probably also want a copy of Winamp itself, to test your plugin you can get that on the Winamp site here.
#WINAMP WIKI FREE#
You can get a free copy of Visual Studio C++ Express here. To begin, you'll need a tool that lets you write code. Many thanks go out to forum members Kaboon, kichik, baafie, burek021, and bananskib for their code examples and advice. The following code has been created based on samples from several forum threads. We'll have to expand this guide in the future to give out more pointers. It also assumes you have some familiarity with programming. This guide assumes you're developing using Visual Studio in a Windows environment.
0 kommentar(er)
