On 18/03/16 09:25, Will Godfrey wrote:
On Fri, 18 Mar 2016 07:19:47 +0000I do a git pull from the yoshimi directory above /src and its all properly owned by me and dated from the pull time...
"Tom" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "madtom1999" for DMARC)
wrote:
On 17/03/16 16:24, Will Godfrey wrote:
On Thu, 17 Mar 2016 13:45:58 +0000So what do I need to do to so my ccmake . is not affected by prior
"Tom" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "madtom1999" for DMARC)
wrote:
Just to check - I've been 'git clone
git://yoshimi.git.sourceforge.net/gitroot/yoshimi/yoshimi" (from
.git/config) and then updating.
From a standing start you should use:
git clone git://yoshimi.git.sourceforge.net/gitroot/yoshimi/yoshimi
This will automatically get you the latest master branch
After that, for later updates just go into the directory and use:
git pull
versions (of yosh)?
Tom
I'm afraid I don't really understand what is happening here. A git pull should
overwrite the CMakeLists.txt file along with everything else, and a new call to
ccmake . should reveal the changes.
From time to time I completely delete the yoshimi directory (on a second
machine) then clone again from scratch. I do that just to check that it still
works correctly and no stale info is hanging around.
Is it possible, that you're somehow updating one directory but actually
compiling from a different one? I've done that myself before now :o
