On 11/02/2011 12:06 AM, Rohan McGovern wrote: > Holger Hans Peter Freyther said:
>> how difficult will it be to only checkout/update/build qtbase and not _all_ >> of >> Qt? Is this something that is planned? > > That is already the way it works - as Shane Kearns pointed out in a > followup mail. For testing qtbase, you get qt5, qtbase and v8. > For testing another gitmodule, you get just that gitmodule, plus the > gitmodules it depends on, plus qt5. Sorry to be stubborn here. We try to have modules in Qt (in contrast to the monolithic qt as of the past), e.g. I could provide a 'Qt Monkey WebPage Scraper' module that is based on WebKit. Why would I want to build QtWebKit whenever I change something in my module? Do I miss the point? So my question is. What prevents us from doing this: Track QtBase -> build QtBase (as unpacked by the CI system) Track QtWebKit -> build QtWebKit (as unpacked by the CI system) Track QtDeclarative -> build QtDeclarative (as unpacked by the CI system) (no qt5 submodule involved, just plain git repository) To be the devils advocate: Can we have QtDeclarative and QtBase decoupled in a way that QtDeclarative works on a week old QtBase? a month? the one from the last stable/minor release? What would it mean if we can not do it? _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
