hi list,
i have no idea of c++, but building stuff from a script should be easy
enough
…i thought.
unfortunately it fails for the current master branch, not being able to
compile HelloWebkit.
a locate qwebview yields the directories /usr/include/QtWebKit/ and
/usr/lib/qt/plugins/designer/
how
Hello Philipp,
We are using Qt Jambi in our project. At some point we decided to set up
build server for it on our side (since there seemed to be no build server
anywhere in Qt Jambi community).
The build server we have now is available here: http://qtjambi.syncloud.org,
you can log in as a guest.
2012/8/11 Vladimir Sapronov
> Hello Philipp,
>
> We are using Qt Jambi in our project. At some point we decided to set up
> build server for it on our side (since there seemed to be no build server
> anywhere in Qt Jambi community).
> …
>
> That build takes latest from
> https://git.gitorious.org
2012/8/11 Philipp A. i hope the xml file is all that’s left.
>
ok, status update:
https://github.com/flying-sheep/qtjambi-git-pkgbuild/issues/1
can anyone help me on how the qtjambi-deployment.xml is generated, and what
i need to install to make the designer work?
___
lauantai 11 elokuu 13:24:12 Philipp A. kirjoitti:
> 2012/8/11 Philipp A.
> > i hope the xml file is all that’s left.
>
> ok, status update:
> https://github.com/flying-sheep/qtjambi-git-pkgbuild/issues/1
>
> can anyone help me on how the qtjambi-deployment.xml is generated, and what
> i need to
Philipp A. wrote:
> unfortunately it fails for the current master branch, not being able to
> compile HelloWebkit.
>
> a locate qwebview yields the directories /usr/include/QtWebKit/ and
> /usr/lib/qt/plugins/designer/
>
> how to set my paths for this setup? currently i have it like so, and
> despi
@samu: thanks for the info regarding the XML!
@darryl: thank you too for the info.
regarding the packaging, i’d rather roll my own. it’s always saner to
maintain your own builds than reshaping packages made for other systems. if
you disagree: why don’t you just deploy .deb OR .rpm? one can be con
Philipp A. wrote:
> regarding the packaging, i’d rather roll my own. it’s always saner to
> maintain your own builds than reshaping packages made for other systems.
> if you disagree: why don’t you just deploy .deb OR .rpm? one can be
> converted into the other ;)
Yes I agree, each disto should ro
2012/8/15 Darryl Miles
> Yes I agree, each disto should roll their own. I am not suggesting you
> take the output *.rpm or *.deb from another disto and use them, but you can
> certainly get a lot of answers from the source inputs on the auto-builders
> for those other distros.
>
> Studying the e
