On Thu, Oct 15, 2009 at 11:08 AM, Eskil Abrahamsen Blomfeldt <[email protected]> wrote: > Francis Galiegue skrev: >> >> >> What's more, there's the problem of juic that needs... uic.cpp from >> the qt sources as well! That is, if I read the build output >> properly... >> >> > > Juic uses some common .cpp files from uic (for stuff like parsing the > .ui-files), and both juic and the designer integration uses private header > files from Qt. > > While distributions will not default to building Qt into the working > directory, they can very easily make a source package for Qt Jambi which > contains the necessary files, like we have always done. I think it's correct > to put this responsibility on the person creating the package, as they will > have control over the Qt sources they are aiming to support, and as this is > precisely the type of work which the distribution is supposed to handle. If > people want to build from the git repository directly, they should be able > to build with -prefix $PWD. > > If you want to make this easier for the people building the source package, > it would be possible to make a target in the build script which copies the > necessary files from a specified Qt source directory and into locations > where they can be detected and used by Qt Jambi. We have used a separate > script for this when building source packages, but it should be possible to > include it in the ant script. >
Interesting... Is this script available somewhere? Maybe it's in the qt-jambi git repos, but I haven't got to that part of the build system yet. -- Francis Galiegue, [email protected] "It seems obvious [...] that at least some 'business intelligence' tools invest so much intelligence on the business side that they have nothing left for generating SQL queries" (Stéphane Faroult, in "The Art of SQL", ISBN 0-596-00894-5) _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
