On Fri, Dec 29, 2017 at 13:32:54 -0800, Jom O'Fisher wrote:
> >> Ninja should be using relative paths for the build tree and absolute
> for anything outside of it.
> That appears to be the case, so I need a better theory. I noticed another
> difference between compilation phase and link phase. The
>> Ninja should be using relative paths for the build tree and absolute
for anything outside of it.
That appears to be the case, so I need a better theory. I noticed another
difference between compilation phase and link phase. The link phase is
bracketed by cmd.exe /C "cd . && && cd .".
I'm wonder
On Thu, Dec 28, 2017 at 12:51:20 -0800, Jom O'Fisher wrote:
> (1) Invoke cmake to generate ninja project. Success.
> * Note that generated rules.ninja has .o compilation dependencies with
> absolute paths and .so link dependencies with relative paths.
Ninja should be using relative paths for the b
I may have sent this on the wrong dl. I'm trying cm...@cmake.org
On Thu, Dec 28, 2017 at 12:44 PM, Jom O'Fisher wrote:
> I have an issue that's really difficult to track down because it only
> seems to repro on certain machines which don't have access to.
>
> The sequence of events seems to be:
I have an issue that's really difficult to track down because it only seems
to repro on certain machines which don't have access to.
The sequence of events seems to be:
(1) Invoke cmake to generate ninja project. Success.
* Note that generated rules.ninja has .o compilation dependencies with
absol
