Hi everyone,

As I'm currently about to restructure the project building
routines in Mono-D (http://mono-d.alexanderbothe.com/), I've been
recommended to use rdmd as the primary build tool and not to
invoke dmd etc. manually anymore.

Rdmd seems pretty easy to handle for building executables w/o
having to care about many background things so intensively. But:
While creating executables is ridiculously easy, how does one
build/link modules to .a/.lib/.so files?
Should I put in a -c flag for just compiling the sources to one
.o/.obj file and call the specific linker afterwards? I'm
primarily thinking of linking stuff to shared objects on linux,
as the -lib flag will already tell dmd to create a static library.

Thanks in advance,
Alex

On 3/10/13, alex <info@alexanderbothe.com> wrote:
> how does one build/link modules to .a/.lib/.so files?

It doesn't support this yet but it will soon. A pull was made recently: https://github.com/D-Programming-Language/tools/pull/51

On Sunday, 10 March 2013 at 19:01:43 UTC, Andrej Mitrovic wrote:
> On 3/10/13, alex <info@alexanderbothe.com> wrote:
>> how does one build/link modules to .a/.lib/.so files?
>
> It doesn't support this yet but it will soon. A pull was made recently:
> https://github.com/D-Programming-Language/tools/pull/51

Love this stuff. What do you think - starting with coding on rdmd support anyway and dropping shared/static lib support for a short time span?
Or..actually, the -c solution should work. I'm too lazy to test it right now though.