On 18 October 2012 12:21, David Nadlinger <[email protected]> wrote:
> On Thursday, 18 October 2012 at 07:29:45 UTC, Manu wrote: > >> and 2) I don't really care where it is, I would just like an answer that >> is >> agree'd by the various compilers, and which is included in each of their >> search paths by default. How can one make a build script for their apps >> when it's not consistent where libraries are to be found? >> > > Just an aside: During the whole discussion, please don't forget that you > also need to compile your library separately for each compiler, as long as > they are not ABI compatible (which is still a long way out). Thus, while I > don't think a standard import path wouldn't be nice to have, the issue > doesn't stand out as a single big problem as it might seem at first. Really? The D compilers aren't ABI compatible on Linux? Good to know. Cheers! Well, for my own purposes, I only intend to interact with bindings for C libs, which, fortunately, are universally binary compatible :)
