|
From: | Nikos Chantziaras |
Subject: | Re: [Mingw-cross-env-list] MXE suddenly wants to rebuild everything |
Date: | Sat, 01 Jun 2013 18:39:03 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 |
On 01/06/13 18:24, Tony Theodore wrote:
On 02/06/2013, at 1:06 AM, Nikos Chantziaras <address@hidden> wrote:Yeah, already tried "touch usr/installed/*", but it doesn't help.That's strange, it would take a bug in "make" or something strange with your system clock to cause that behaviour. What does the output of: $ date $ stat -l src/gcc.mk $ stat -l usr/installed/gcc look like?
Hmm, I've actually started the rebuild. It actually finished much sooner than expected. It didn't actually rebuild everything. It rebuilt gcc and qt. I assumed it was going to rebuild everything, since it started with gcc. But it seems I was wrong. I've still no idea why it did that. Most probably I touched some file by mistake.
My MXE tree is about a year old though (I have tons of settings in the *.mk files that really I don't want to lose) and I don't track it with Git, so the new stuff is definitely not there.What sort of settings are they? Is there a way we could make it easier to keep updated with mxe and keep your local settings?
Not sure how easy it would be to automate this. Here's a good example (qt.mk) of the kind of changes I'm doing:
http://pastebin.com/raw.php?i=dkn6jZUC
[Prev in Thread] | Current Thread | [Next in Thread] |