[FFmpeg-devel] [PATCH] build: use Windows path for MSVC

Michael Niedermayer michael at niedermayer.cc
Sat Jan 23 17:24:38 CET 2016


On Sat, Jan 23, 2016 at 05:16:28PM +0100, Hendrik Leppkes wrote:
> On Sat, Jan 23, 2016 at 4:27 PM, Andreas Cadhalpun
> <andreas.cadhalpun at googlemail.com> wrote:
> > On 23.01.2016 15:07, Hendrik Leppkes wrote:
> >> On Sat, Jan 23, 2016 at 2:51 PM, Andreas Cadhalpun
> >> <andreas.cadhalpun at googlemail.com> wrote:
> >>> On 23.01.2016 14:48, Hendrik Leppkes wrote:
> >>>> Unfortunately, cygpath is not guaranteed to be available, and in fact
> >>>> is not on some working build setups today (ie. msys1 environments with
> >>>> msvc)
> >>>
> >>> Is there another way to get the Windows path on those environments?
> >>>
> >>
> >> Not that I am aware.
> >
> > Hmm, sed should be available everywhere.
> >
> > Does the attached patch fix the MSVC builds?
> >
> 
> Unfortunately these assumptions are also not valid. On cygwin for
> example, a path would be /cygdrive/C/path/to/folder
> Dealing with absolute paths in the unix/windows mixture is just not
> going to be easy, which is why we were careful to avoid them at all
> before.

IIUC windows excutables get their command line arguments translated
from unix to dos paths. Cant that be used to turn a unix into a dos
path to then later use in a more convoluted (not auto translated)
argument ?

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

There will always be a question for which you do not know the correct answer.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20160123/ac6b9224/attachment.sig>


More information about the ffmpeg-devel mailing list