BindBC Updates: new loader function, SDL_net, streamlined SDL_* version indentifiers

Mike Parker aldacron at gmail.com
Sun May 24 05:15:19 UTC 2020


On Sunday, 24 May 2020 at 04:16:10 UTC, Daniel C wrote:
> On Saturday, 23 May 2020 at 19:59:51 UTC, Daniel C wrote:
>> I'll be mucking around with it again later.
>
> Well, I'm having limited success.  I got 32-bit compile/run 
> using basic -m32, and -m64 compiles but crashes lol.  Trying 
> out 32-bit -m32mscoff with Microsoft Build Tools (2019) 
> resulted in this mess:
> phobos32mscoff.lib(runtime_c8b_76e.obj) : error LNK2001: 
> unresolved external sym
> bol _printf
> phobos32mscoff.lib(parseoptions_d98_7cf.obj) : error LNK2001: 
> unresolved externa
> l symbol _printf
> phobos32mscoff.lib(gc_244f_122.obj) : error LNK2001: unresolved 
> external symbol
> _printf
> phobos32mscoff.lib(msvc_32mscoff.obj) : error LNK2001: 
> unresolved external symbo
> l __vsnprintf
> phobos32mscoff.lib(parseoptions_d93_21b.obj) : error LNK2001: 
> unresolved externa
> l symbol _sscanf
>
> Frustrating!  I don't even know where to go for help with that 
> stuff.  Through experimentation, I was able to compile with 
> older Visual C++ 2010 tools, but I'd rather not be using 10 
> year old tech.

There should be no need to revert to VS 2010. These errors 
indicate that something in your build process or setup is borked.

Have you tried building your app with dub and using bindbc-sdl as 
a dependency rather than doing it separately DMD? This way, you 
can ensure that everything is being compiled with the same 
options and the linker is getting the correct libraries.

>
> Maybe this wasn't the time for me to come back lol

I would say it's generally much easier to build D projects these 
days than it ever has been. We just need to figure out where 
you're going wrong.



More information about the Digitalmars-d-announce mailing list