On Thu, 23 Jul 2015, Martin Storsjö wrote:
Anyway, seems the solution to use a script is rejected. We can't call
a script in the source folder, because the source folder may have
spaces. Just like MS link.exe...
I wouldn't call it "rejected", but we need to think further...
Another option that I came to think of (which unfortunately doesn't work
just as such) would be to set ld to "cl -link". When adding the -link
option to cl, all following arguments are passed straight to link.exe
(which cl.exe manages to find just fine, even if a different link.exe
exists earlier in the path).
The problem is that cl refuses to just invoke link.exe unless you actually
provide some source file name (object file name in this case) prior to
-link.
Alternatively one could rewrite the link.exe options into cl.exe option
format (e.g. -Fe instead of -out: and such), but I think we might use
options that require -link anyway (options that aren't available in cl as
such), and once you add -link, it's fiddly (and brittle) to make sure that
options are set at the right place in the right format.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
