On Sunday, 12 July 2015 at 05:18:24 UTC, Mike Parker wrote:
This has nothing to do with DMD, DUB, or linking :) Derelict
loads the shared libraries at runtime through the system API
(LoadLibrary on Windows and dlopen elsewhere). Each package has
a default set of library names it looks for. I wa
On Sunday, 12 July 2015 at 02:14:06 UTC, serh wrote:
This is what I get when I run "dub" in the directory:
http://codepad.org/BpnOHVSV
As mentioned, I already have respective Allegro libs installed,
but as liballegro.so.5.0 instead of liballegro-5.0.so and so on.
The C++ linker sees them fine
On Sun, 12 Jul 2015 02:14:04 +, serh wrote:
> As mentioned, I already have respective Allegro libs installed, but as
> liballegro.so.5.0 instead of liballegro-5.0.so and so on.
> The C++ linker sees them fine, but I am not sure how to make dmd/DUB see
> the correct libraries to link.
Derelict
On Sunday, 12 July 2015 at 01:17:27 UTC, Mike Parker wrote:
No Derelict package has a compile-time or link-time dependency
on the libraries they bind. The libraries are loaded at run
time. DUB doesn't know anything about those libraries, so you
shouldn't be seeing such an error with 'dub build'
On Saturday, 11 July 2015 at 16:43:39 UTC, serh wrote:
Hello,
I am trying to use Derelict's Allegro 5 in my DUB project,
however, when I try to run `dub build` it says it cannot find
liballegro-5.0.11.so and liballegro-5.0.so.
I have both libraries installed as liballegro.so.5.0.11 and
liba
Hello,
I am trying to use Derelict's Allegro 5 in my DUB project,
however, when I try to run `dub build` it says it cannot find
liballegro-5.0.11.so and liballegro-5.0.so.
I have both libraries installed as liballegro.so.5.0.11 and
liballegro.so.5.0 under my Arch system respectively.
Is th
