Using libraries in VisualD

[evilrat]

On Friday, 4 April 2014 at 16:44:07 UTC, evilrat wrote:
> On Friday, 4 April 2014 at 15:58:47 UTC, Zaggy1024 wrote:
>> On Friday, 4 April 2014 at 09:34:29 UTC, evilrat wrote:
>>>
>>> this may means that you must compile that dsfml(?) as library
>>> first and then link it with your code. because adding import
>>> paths only says to compiler that they are exists, but no 
>>> actual
>>> code generated for them unless you put it in your build. i 
>>> hope
>>> it clear enough now.
>>
>> Isn't that what putting the path to the prebuilt .lib files in 
>> the linker configuration does?
>
> "import path" is for .d/.di files, library path is for .lib

sorry for such obvious comment. i must say that library files is 
full path or just filename.lib, and library search path is where 
.lib's can be found. and keep in mind that most(if not all) 
project options are delimited with spacebars only, not semicolon.

so if you have such paths like
"C:\Some Location\lib;D:\other\lib"
you shold try to split them like this
"C:\Some Location\lib" D:\other\lib