On quinta-feira, 6 de junho de 2013 18.51.44, Oswald Buddenhagen wrote:
> On Thu, Jun 06, 2013 at 01:07:06PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> > On Thursday 06 June 2013 08:58:53 Thiago Macieira wrote:
> > > On quinta-feira, 6 de junho de 2013 17.57.08, Oswald Buddenhagen wrote:
>
> From: development-bounces+eike.ziller=digia@qt-project.org
> [development-bounces+eike.ziller=digia@qt-project.org] on behalf of
> Vincent [vincentb1...@gmail.com]
> Sent: 06 June 2013 18:20
> To: development@qt-project.org
> Subject: [Development] Standard options & deploying on Mac O
Hello,
I would like to be able to deploy Qt applications on Mac OS X 10.6. The
development environment is on 10.7.
I tried with Qt 5.0.2 and Qt 5.1.0 Beta 1 (downloaded binaries from
qt-project.org) and none of the compiled applications run on Mac OS X 10.6.
Then I tried to compile Qt 5.1.0 Beta
On Thursday 06 June 2013 08:58:53 Thiago Macieira wrote:
> On quinta-feira, 6 de junho de 2013 17.57.08, Oswald Buddenhagen wrote:
> > for the packagers, it would be the best solution to simply include the
> > docs directly into the particular source tarballs. we have been doing
> > that in ancient
On quinta-feira, 6 de junho de 2013 17.57.08, Oswald Buddenhagen wrote:
> for the packagers, it would be the best solution to simply include the
> docs directly into the particular source tarballs. we have been doing
> that in ancient times. and its consistent with shipping the syncqt'd
> headers,
On Thursday 06 June 2013 08:44:21 Thiago Macieira wrote:
[snip]
> Can we simply ship a qtdocs tarball with all documentation pre-built?
At least in Debian's case, it wouldn't be useful, as we need the sources
(preferred way of modification) to build them.
Of course, if it helps other people, cou
On Thursday 06 June 2013 17:38:53 Oswald Buddenhagen wrote:
> On Thu, Jun 06, 2013 at 12:25:18PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> > Is there a way to tell qtbase to build it's documentation when make is
> > called? It would be awesome if this could also be inherited by the other
On quinta-feira, 6 de junho de 2013 17.38.53, Oswald Buddenhagen wrote:
> On Thu, Jun 06, 2013 at 12:25:18PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> > Is there a way to tell qtbase to build it's documentation when make is
> > called? It would be awesome if this could also be inherited b
Hi! I have seen that many options from qtbase get inherited by other
submodules when building them from separate tarballs.
Is there a way to tell qtbase to build it's documentation when make is called?
It would be awesome if this could also be inherited by the other submodules.
Kinds regards, L
On quinta-feira, 6 de junho de 2013 11.22.28, Koehne Kai wrote:
> > That means we need to change the Qt 5.1 RC1 build scripts to pass
> > -no-c++11.
> Isn't the lower risk approach to just revert the change in the release
> branch? That is, we'd have the same behavior as with 5.0. I understand that
On quinta-feira, 6 de junho de 2013 07.52.53, Ziller Eike wrote:
> Just for clarification, the default mkspec of Qt 5 on Mac is clang (without
> libc++), not gcc/g++ .
The default mkspec on Mac is now clang *with* libc++.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect -
On terça-feira, 4 de junho de 2013 15.55.10, Thiago Macieira wrote:
> As of 3d0a60aaa4077a8 in Qt 5.2
That change is in 5.1.
That means we need to change the Qt 5.1 RC1 build scripts to pass -no-c++11.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Te
12 matches
Mail list logo
