16 Jan
2012
16 Jan
'12
10:06 p.m.
On Mon, 16 Jan 2012 12:09:22 -0800 (PST)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
If you patch files from your git repo you can:
-execute "git diff" to generate the diff between the current state of
the repo and the last committed change
-execute "git checkout -- ." to reset all your changes
so there should be no reason not to patch the local copy of the git repo
(except to publish build scripts for final releases).
I'm not
sure how smart the build system is at the
moment. Try symlinking
/usr/bin/moc and /opt/trinity/bin/moc to the real TQt3 moc
that is
residing in /opt/trinity/lib/tqt3-R14.0.0/bin/moc.
Remember to make clean
before trying to rebuild, as the build system will not
detect that the moc
binary has changed and recreate the .moc files.
I removed the Qt4 package. No more /usr/bin/moc.
/opt/trinity/bin/moc is already sym linked
to /opt/trinity/lib/tqt3-R14.0.0/bin/moc.
Regarding make clean, why or where do I do that? I'm copying the
files from my local GIT to $TMP and applying my patches there. I did
not want to patch the GIT files. So every time my build script runs I
am copying fresh from GIT.
Am I missing something?
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting