On 8/27/21 10:35 AM, Ki Rill wrote:

Yes, either 3.5.0 or 3.7.0, they now build with 2 types of libs, static and dynamic. The raylib.lib file is for static linking, the raylibdll.lib file is for DLL.

Glad you got it working!

You know, I taught a class using raylib and D (I learned a lot from your video series, thanks!), and I didn't even think about just copy the libraries to your project directory as a "step". Instead I had them put in the /LIBDIR flags to wherever they installed it.

This way is MUCH easier, I think I'll switch to that.

dub in general has some rough edges when linking against libraries that aren't in default locations. Having to edit the dub.json file is sub-par.

-Steve

On 8/27/21 11:19 AM, Ki Rill wrote:

To clarify, the .dll file's path is not embedded into the binary. You have to add it's path to your "Path" environment variable in order for your game to load it.

But you do need the /LIBPATH option to tell it where to find the .lib file.

"lflags": ["/LIBPATH:C:\\Users\\Username\\Desktop\\test\\source\\"]

msvcrt120.lib
OLDNAMES.lib
shell32.lib

That shouldn't happen. I've never had to tell it where the default libraries are. For sure the lflags does NOT override the default library search paths.

I suspect your MSVC installation is bad, or there are some other switches causing problems.

-Steve

On Friday, 27 August 2021 at 15:24:14 UTC, Steven Schveighoffer wrote:

Hmm... well, I will use the default setup and think about it later.

I mostly use Linux, Windows realm is an uncharted territory for me.

On 8/27/21 11:43 AM, Ki Rill wrote:

Take my diagnoses with a grain of salt -- I mostly use MacOS and Linux, and I'm mostly lost on Windows. I was proficient with Visual C++ 5 or so a long time ago ;)

-Steve