View Single Post
Old 07-17-2016, 05:49 PM   #5
varlog
actually it is /var/log
varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.varlog ought to be getting tired of karma fortunes by now.
 
varlog's Avatar
 
Posts: 341
Karma: 2994236
Join Date: Sep 2012
Location: usually Europa
Device: prs t1
Quote:
Originally Posted by DiapDealer View Post
...
Like I mentioned, when cmake gets confused, or out of whack, it's best to delete everything in the current build directory and let cmake start from scratch again.
it's the second thing I usually do (and I've done).
Quote:
Also, if you're unsure if you've inadvertantly changed any of the cmake build/install scripts, just use git status and/or git diff to eliminate that possibility.
I've carried the whole structure via USB: the permissions got mangled: git status cries all is new because of it, but still...
varlog is offline   Reply With Quote