Hi All,
I'm trying to extend the 3rd party component foo_bpm. It seems to have been dormant since April 2010. I can build the source for the last version of foo_bpm (0.2.4.1) with the current SDK (2011-03-11). However it fails to load in foobar due to the missing DLL or wrong foobar major version number notification. I think this is probably because I am mixing an old component source with the latest SDK. Is this possible? I'm certain the author, Fraganator, would have built it in the V1.0 SDK circa Jan - April 2010.
I'm learning component development, but have verified my SDK setup like I say I can sucessfully make a DLL and can get the tutorial component to build and load just fine.
Can anyone advise me on where I could get the V1 SDK in order to try building the foo_bpm source with that?
Thanks
Chris
There shouldn't really be any significant differences between the current SDK and the older ones, interface-wise.
There is however a minimum foobar2000 version required for components compiled with a particular SDK, due to the introduction of newer interfaces, which also is bumped when incompatible changes are made, which should be very seldom.
Are you trying to load a component built with a new SDK in an old foobar2000? If so, upgrade your foobar.
Are you trying to load a component built with a new SDK in an old foobar2000? If so, upgrade your foobar.
No, I'm using the current SDK and latest stable foobar (v1.1.11). Perhaps I have another problem - I'm aware its a bit clutching at straws, but I can't think why the last released foobar DLL loads ok, yet the one I have built doesn't. Of course I have checked that it is statically linked.
One thing I did notice was that visual studio 2010 professional doesn't seem to have a one to one mapping with its ATL files with the ATL in WT8.0 (the headers of which I am using to get the ATL Helper project to build). This shouldn't affect anything at runtime, right? I think any missing dependencies would just affect compile and link time problems.
I'm new to a lot of the more library specific stuff as my day job is in embedded C software.
Throw your DLL at Dependency Walker (http://www.dependencywalker.com) and see if there's any DLL except for the usual suspects (shared/ieshims) that is missing. You might be missing some runtime of a library you're built against.
Thanks, that's a big help. I can immediately see that some dependencies are missing in the built dll; MSJava.dll, shared.dll and libfftw3-3.dll. The last is an open source fft library specific to foo_bpm component - I can check the path for that. shared.dll I assume is ok from your comment. That just leaves the msjava.dll. I'll see what I can do... Cheers
EDIT: FIXED! thanks, the name of the DLL for the fft was typo'ed, so it couldn't find this. what a great tool dependency walker is - thanks for introducing me to that.
msjava.dll is like ieshims.dll one of those false positives that never are there.
shared.dll is provided by fb2k at load time, so that's indeed not a problem.