Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
1
Development - (fb2k) / Failed linking with GetOpenFileName
Last post by mortalis -
Hi.
Maybe someone had this problem or could point me to its root...
Trying to call GetOpenFileName() method from Windows SDK (comdlg32.h), but during linking it fails with the following:

Code: [Select]
mainmenu.obj : error LNK2001: unresolved external symbol __imp_GetOpenFileNameW
SDK-2023-09-23\foobar2000\foo_sample\x64\Release\foo_sample.dll : fatal error LNK1120: 1 unresolved externals

I just included this minimal chunk to the mainmenu.cpp of the foo_sample project from the SDK-2023-09-23, in the execute() method.

Code: [Select]
OPENFILENAME ofn;
GetOpenFileName(&ofn);

I found that the method should be in the comdlg.lib of the Windows SDK 10. I tried with 10.0.20348.0 which should have the method, according to this:
https://learn.microsoft.com/en-us/windows/win32/api/commdlg/nf-commdlg-getopenfilenamew

Checked in the project properties that it points to that version.
And the .lib is there of course.
The verbose build log also contains the path to the directory with the .lib, although it's huge and I'm not exactly sure where to look.
I can attach the full log if someone needs it, but it should be reproducible on another PC I think.

Weird thing is that I found GetOpenFileName in the shared library in the foobar SDK, and it builds.

Also, when I build a minimal console app in Visual Studio with that chunk, plus include <windows.h>, it build without errors (in exe and dll modes).

Thanks.
5
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by TF3RDL -
Quote from: Azuriye on
Hello, I have a small doubt regarding this gap when changing the window size... Any idea how to resolve this or why it's happening in the first place? I'm not blaming the plugin since this seemed to happen with other spectrum analyzer programs as well unless I change the note range and bands per octave to somewhat eliminate this gap. You can see when windowed there's a-lot of gap present at the beginning of the note compared to full-screen but I want to totally eliminate this gap.
BTW, that start and end "gap" do exist in original foo_musical_spectrum when the horizontal screen resolution is not an integer factor of number of actual bands, which is absent in this CodePen project and even older version of this component
10
Development - (fb2k) / Re: x64 compilation failed, but x86 compilation succeeded.
Last post by mortalis -
Thanks for the fix.
So the "pfc" project has incorrect build profile names, and output directories for Debug and Release on x64.

Strangely I changed the configuration name to just "Debug" from the solution Configuration Properties, but it resulted in "fatal error LNK1169: one or more multiply defined symbols found".

So it seems the solution specifically expects the pfc to have configuration as "Debug FB2K" / "Release FB2K" though not sure this is defined, and why it's different from other projects, with just plain "Debug" / "Release"...