X64\foo_sample.dll <= for 圆4 and arm64ecĪrm64ec\foo_sample.dll <= arm64ec foobar2000 will prefer this over 圆4 if providedĬomponents packaged this way will let foobar2000 choose the right DLL to load. To support multiple CPU architectures with one package, put files meant for legacy x86 foobar2000 in top level and create subdirectories named after the architectures, with files that are specialized for those architectures.įor an example, 圆4 foobar2000 will extract whole component archive, then overwrite files in root with those in 圆4 subfolder:įoo_sample.dll <= this is for legacy x86 foobar2000 If your component requires additional files, include them in the zip foobar2000 will extract them to the folder containing your DLL upon installation.ĭelivering as straightforward zip-of-a-DLL still works, but that leaves it up to the user to download the correct binary. This is simply a renamed zip of your DLL. See also: Visual Studio Compatibility, SDK Contents.Ĭomponents are delivered to the user in form of fb2k-component file. Do not implement it yourself.įoobar2000 components are made using foobar2000 SDK and Microsoft Visual Studio. This function is generated automatically by the foobar2000_component_client module. 3 Getting a component listed on /componentsĪ foobar2000 component is a Windows Dynamic Link Library (DLL) extending the functionality of the foobar2000 application.Ī foobar2000 component implements one or more entrypoint services and interacts with services provided by foobar2000 core or other components.Įach component has a single exported DLL function, foobar2000_get_interface(), called on startup to initialize and discover entrypoint services of your component.
0 kommentar(er)
