DMD currently produces .obj files in the current directory, stripping off any path provided.  Could there please be an option to preserve the path so that libraries with multiple modules with the same filename in different packages can be compiled?  "-preserve-paths" would work nicely.

You mean have it place the .obj file in the same directory as the source was found?

"Burton Radons" <loth@users.sourceforge.net> wrote in message news:bfqmh2$2mdm$1@digitaldaemon.com...
> DMD currently produces .obj files in the current directory, stripping off any path provided.  Could there please be an option to preserve the path so that libraries with multiple modules with the same filename in different packages can be compiled?  "-preserve-paths" would work nicely.
>

"Walter" <walter@digitalmars.com> wrote in message news:bfu79a$189$2@digitaldaemon.com...
> You mean have it place the .obj file in the same directory as the source
was
> found?
>

Or else (optionally) specify an object path, so you can control where the
.obj file goes?

Rich C.

Walter wrote:
> You mean have it place the .obj file in the same directory as the source was
> found?

Unless if the object path prefix has been changed, yes.

   dmd bar\foo.d -preserve-paths -c

Creates "bar\foo.obj".

   dmd bar\foo.d -preserve-paths -obaz -c

Creates "baz\bar\foo.obj".

> "Burton Radons" <loth@users.sourceforge.net> wrote in message
> news:bfqmh2$2mdm$1@digitaldaemon.com...
> 
>>DMD currently produces .obj files in the current directory, stripping
>>off any path provided.  Could there please be an option to preserve the
>>path so that libraries with multiple modules with the same filename in
>>different packages can be compiled?  "-preserve-paths" would work nicely.