Re: [cmake-developers] Problem with created debian package

Am Freitag, 29. Dezember 2017 um 22:25:53, schrieb Domen Vrankar > 2017-12-29 14:20 GMT+01:00 Kornel Benko : > > > All of sudden, cmake(cpack) started producing wrong debian packages for > > one project. > > > > Did the project change in some way or was

Re: [cmake-developers] Build failure due to {cd bindir} failed on Windows/Ninja

>> 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

Re: [cmake-developers] Problem with created debian package

2017-12-29 14:20 GMT+01:00 Kornel Benko : > All of sudden, cmake(cpack) started producing wrong debian packages for > one project. > Did the project change in some way or was it the packaging environment that changed? I'd like to know a bit more details even if the solution below

Re: [cmake-developers] Build failure due to {cd bindir} failed on Windows/Ninja

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

[cmake-developers] Problem with created debian package

All of sudden, cmake(cpack) started producing wrong debian packages for one project. This is the output of debian package manager: dpkg: warning: downgrading lyx24 from 2.4.0-50424git-g3a4b233 to 2.4.0-50422git-gd6fb2ab (Reading database ... 422667 files and directories