Developer Tutorials

Topic: Developer Tutorials (Read 113578 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

Re: Developer Tutorials

Reply #50 – 2016-12-30 19:41:34

I am having a problem with atl. I've installed the wtl and successfully compiled(and run) foo_sample. But I'm not able to make it work in a solution made from scratch. I added all the files from foo_sample to the solution, next set up the linker and added all the projects from sdk. It compiles fine, but when running in foobar I'm getting 'Internel error - one or more of the installed components have been damaged. How can I make it work?

Re: Developer Tutorials

Reply #51 – 2016-12-30 20:12:52

Have you added the required references under "Frameworks and references"? Right click the project "Solution explorer" and choose "References...". You'll need to add at least pfc, foobar2000_component_client and foobar2000_SDK. Most projects will additionally need foobar2000_sdk_helpers and foobar2000_ATL_helpers.

I'm not entirely sure what the error message means but it sounds like the DLL might lack the proper entrypoint function. This in turn would indicate that foobar2000_component_client is not linked into the DLL.

Re: Developer Tutorials

Reply #52 – 2016-12-30 20:36:59

Perhaps it is a mismatched name to the component filename verification service, versus installing the component to the Application\components folder instead of Configuration\user-components\foo_component_name?

Also, that service is always a good idea if you ever care about receiving crash reports, as it can be bothersome loading minidumps where the DLLs have been renamed from your original build filenames.

Re: Developer Tutorials

Reply #53 – 2016-12-30 20:47:30

Quote from: kode54 on 2016-12-30 20:36:59

Perhaps it is a mismatched name to the component filename verification service, versus installing the component to the Application\components folder instead of Configuration\user-components\foo_component_name?

Also, that service is always a good idea if you ever care about receiving crash reports, as it can be bothersome loading minidumps where the DLLs have been renamed from your original build filenames.

I wouldn't think that that service exists! Thanks for the help.

Re: Developer Tutorials

Reply #54 – 2016-12-30 21:24:56

VALIDATE_COMPONENT_FILENAME is the macro, it declares an implementation of the component validation service, styled to check your filename on disk. It can be expanded through more complex means to perform more thorough verification, although filename is usually all you need to care about for minidump concerns.

Re: Developer Tutorials

Reply #55 – 2018-10-23 09:34:58

Is there something similar for Android version of foobar2000?

Re: Developer Tutorials

Reply #56 – 2018-10-23 11:00:56

No. Mobile versions don't support third party components. I'm pretty sure it's not even allowed, certainly not allowed for Apple Store.

Re: Developer Tutorials

Reply #57 – 2018-10-24 15:16:02

There's a lot of things that Apple doesn't allow but fortunately this doesn't affect Android.
On Google Play & Android it's possible to add extra modules as separate APK files if they are published and signed by the same person. So the foobar2000 author will need to upload them in the end, but they can be developed by someone else.
Deadbeef player (Android version) used this mechanism to offer extra decoder pack as a separate APK.

Re: Developer Tutorials

Reply #58 – 2018-10-24 17:30:17

Quote from: magicgoose on 2018-10-24 15:16:02

On Google Play & Android it's possible to add extra modules as separate APK files if they are published and signed by the same person. So the foobar2000 author will need to upload them in the end, but they can be developed by someone else.

So, foobar2000 author will be responsible for those 3rd party plugins made by unknown authors? Sounds like a bad idea.