Hello everyone, The volunteer is myself. I have great hope in qt_jambi since it allows me to start a pet project of mine. But before I can start this project, I need to build it. And right now, I can't.
The patch I sent as an introduction (a dry introduction, I must admit) allows me to complete the build process up to the stage of, well, failing at juic. I don't remember what I read about this offhand, but it seems that I need to have the Qt sources available to build at this stage, and that this was a known problem. I need to dig it back from the net again to build all this. Anyway, I can be of some help: the build.xml file is huge right now, and can be divided. At work, I maintain a project which uses several simple ant build files "connected" together to complete the build process. What would you think of a patch series that would split the main build.xml into more individual, manageable parts? Of course, this patch series would be immensely simplified if I had a clue about how to solve the problem above (when I hard copy the headers from the Qt source into the build tree for juic, I encounter a "missing target for uic.o", but even without this, I think I can manage something useful. Comments? -- 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
