On domingo, 9 de junho de 2013 09.37.05, Syam Krishnan wrote:
> >> Is it something I&aps;m doing with my VM?
> >
> > Probably. Please check your environment, especially the CXXFLAGS
> > environment variable.
>
> I'm attaching /proc/cpuinfo and output of "g++ -Q -v" for reference.
How about the
On 06/09/2013 09:09 AM, Thiago Macieira wrote:
On domingo, 9 de junho de 2013 07.51.03, Syam Krishnan wrote:
I don&aps;t know where it is coming from as I can&aps;t locate
&aps;atom&aps; in any of Qt creator source files.
Is it something I&aps;m doing with my VM?
Probably. Please check your e
On domingo, 9 de junho de 2013 07.51.03, Syam Krishnan wrote:
>
> I don&aps;t know where it is coming from as I can&aps;t locate
> &aps;atom&aps; in any of Qt creator source files.
>
> Is it something I&aps;m doing with my VM?
Probably. Please check your environment, especially the CXXFLAGS envi
Hi,
I'm building Qt Creator 2.8 beta on CentOS 6. I've noticed that
the gcc command line options get "-march=i686 -mtune=atom".
I'm building on a VM with Core i5 processor and 'atom' is not a
default option.
I don't know where it is coming fr
Thanks, Jens. The spacer item solution works for me, but I'm not sure I
completely understand what's going on here. I toyed around with this a
litte more and I'm confused by this output:
import QtQuick 2.1
import QtQuick.Layouts 1.0
Item {
width: 320
height: 240
ColumnLayout {
