Hello everyone,

Here is a summary of what changes I have integrated into community-port-to-4_6:

* First patch removes the ant.qt-jambi.jar.uptodate property, since it basically
  duplicates the work of the <javac> task (which won't recompile class files if
  they are newer than the source files) and the <jar> task (which won't recreate
  a jar if the jar is newer than all its source files);

* Patches 2 to 4 rework the generator.xmlmerge.* targets. In fact, all
  individual generator.xmlmerge.xxx targets (xxx being core, xml, opengl and
  whatnot) have disappeared, along with their <condition>s. Everything is done
  with one macro, one check target, and one work target. There is one
  "functional" difference: if one file is changed, the generator.xmlmerge
  targets makes it all. But then that's a very little part of the build process
  (time wise) and the gain in legibility (and ease of future modifications)
  justifies it (imho).

There is one other behaviour change: the two targets affected don't rely on the
qtjambi.force property anymore, since none of these targets really needed them
to start with, and also because in general, after having studied the build.xml
file for quite some time, I don't see a need for it at all.

The added bonus is the diffstat:

 build.xml |  318 ++++++++++++-------------------------------------------------
 1 files changed, 63 insertions(+), 255 deletions(-)

_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest

Reply via email to