Menu
Search

Forums

Forum Index

Thread overview
Path separator confusion in linker
Apr 07, 2003
Matthew Wilson
Apr 07, 2003
Walter
Apr 07, 2003
Matthew Wilson
April 07, 2003
Gravatar of Matthew WilsonPosted by Matthew WilsonReply
Matthew Wilson
Gravatar of Matthew Wilson


Reply
The compiler works fine with / as well as \, whereas the linker does not. This is ... hours later ... somewhat of a confounding contradiction. :(
April 07, 2003
Gravatar of WalterPosted by Walter
in reply to Matthew Wilson		Reply
Walter
Gravatar of Walter
Posted in reply to Matthew Wilson


Reply
"Matthew Wilson" <dmd@synesis.com.au> wrote in message news:b6r6j4$vrg$1@digitaldaemon.com...
> The compiler works fine with / as well as \, whereas the linker does not. This is ... hours later ... somewhat of a confounding contradiction. :(

That's another artifact of following the Microsoft convention of using / for switches. Optlink is command compatible with most Microsoft linkers.
April 07, 2003
Gravatar of Matthew WilsonPosted by Matthew Wilson
in reply to Walter		Reply
Matthew Wilson
Gravatar of Matthew Wilson
Posted in reply to Walter


Reply
IC.

I can live with it.

:)

"Walter" <walter@digitalmars.com> wrote in message news:b6sjm5$crt$3@digitaldaemon.com...
>
> "Matthew Wilson" <dmd@synesis.com.au> wrote in message news:b6r6j4$vrg$1@digitaldaemon.com...
> > The compiler works fine with / as well as \, whereas the linker does
not.
> > This is ... hours later ... somewhat of a confounding contradiction. :(
>
> That's another artifact of following the Microsoft convention of using /
for
> switches. Optlink is command compatible with most Microsoft linkers.
>
>