Dusan Zatkovsky wrote: > Hi all. > > I have done a $SUBJ. I have question about commiting it to repo, because * > (follow long explanation). > > Longer explanation of plugin: > > Plugin is multi module maven project, which contains: > - maven plugin > - qtjambi library wrapper *1 > - resources for win32 *2 > - resources for win64 *2 > - resources for lin32 *2 > - resources for lin64 *2 > - example app > > *1 - longer discussion later, ignore it 4now > *2 - to work WITHOUT qtjambi extracted on disk, I have embedded > jiuc, lupdate, lrelease and some .so and .dll files into > "resource" modules. You should build qtjambi based maven > application without manually downloading anything. > > ... so my question is, if embedding binaries / commiting it into git is not a > problem. It is about 2-3 MB per platform, now for qtjambi 4.5, so it will > grow when moving to 4.6, 4.7 and so on. > Hmm, in my opinion is that the binaries that "belongs" to the Qt system should reside there. However, when building binary releases for the "public" then you are free to bundle all you want, as we do for assistant, designer, etc.
I guess what you should do is to make a new binary release for one of the platforms. Based on the work from Bruno, I have made a script that packages the necessary components from Qt/QtJambi src compile to a binary release, you may have a look on this and modify it with the necessary changes. Helge _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
