I have just tried on Linux and found that it depends on the way how the file name is specified, namely whether foo.tex is given including the extension or only foo:
$ xetex --output-directory=./dynamic-content foo This is XeTeX, Version 3.14159265-2.6-0.99996 (TeX Live 2016) (preloaded format=xetex) entering extended mode (./foo.tex [1] ) Output written on ./dynamic-content/foo.pdf (1 page). $ xetex --output-directory=./dynamic-content foo.tex This is XeTeX, Version 3.14159265-2.6-0.99996 (TeX Live 2016) (preloaded format=xetex) entering extended mode (./dynamic-content/foo.tex [1] ) Output written on ./dynamic-content/foo.pdf (1 page). I have also tried luatex, tex, and pdfcsplain and all of them behave identically. Zdeněk Wagner http://ttsm.icpf.cas.cz/team/wagner.shtml http://icebearsoft.euweb.cz 2017-01-14 15:41 GMT+01:00 Philip Taylor <p.tay...@rhul.ac.uk>: > If XeTeX is invoked on file foo.tex specifying > --output-directory=../dynamic-content, > and if there is also a file ../dynamic-content/foo.tex, then XeTeX will > process that file > rather than the file which it was instructed to process : > > > \message {This is the intended foo.tex} > > \end > > > > This is XeTeX, Version 3.14159265-2.6-0.99996 (TeX Live 2016/W32TeX) > (preloaded format=xetex) > > restricted \write18 enabled. > > entering extended mode > > (../dynamic-content/./foo.tex This is the unintended foo.tex ) > > No pages of output. > > Transcript written on ../dynamic-content/foo.log. > > -- > > Philip Taylor >
-------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex