> The alternative is to put this code inside qmake itself, so no new binary
> is created. This has the advantage that several Qt classes are already
> bootstrapped, including the filesystem engine.
A bit late to the conversation, but wouldn't a nice first step / middle ground
be modifying qtsync
Hi,
> 1) the overwhelming majority of Windows downloads are of the pre-compiled
>binaries and have been for as long as I can remember, so we will continue
>to invest time to make that better, easier, more efficient
>That's why we're now going to ship an MSVC2012 64-bit build, a non-ANG
On quarta-feira, 10 de abril de 2013 21.54.29, Michael Jackson wrote:
> So we have to move include files around during the build because command
> line lengths are too long? I have never understood why the header for
> QString isn't QString.h. Why is it qstring.h?
The header is qstring.h because i
On quarta-feira, 10 de abril de 2013 17.37.02, Thiago Macieira wrote:
> The alternative is to put this code inside qmake itself, so no new binary
> is created. This has the advantage that several Qt classes are already
> bootstrapped, including the filesystem engine.
Uh... oops. Chicken-and-the-e
ichael Jackson
> Sent: Wednesday, April 10, 2013 6:31 PM
> To: interest@qt-project.org
> Subject: Re: [Interest] Apologies on the "bloat" thread (a.k.a yes Windows is
> still important)
>
>
> On Apr 10, 2013, at 8:37 PM, Thiago Macieira
> wrote:
>
>&
nterest-bounces+scott=onshorecs@qt-project.org] On Behalf Of
Michael Jackson
Sent: Wednesday, April 10, 2013 6:31 PM
To: interest@qt-project.org
Subject: Re: [Interest] Apologies on the "bloat" thread (a.k.a yes Windows is
still important)
On Apr 10, 2013, at 8:37 PM, Thiago Macieira
On Apr 10, 2013, at 8:37 PM, Thiago Macieira wrote:
> Yes, there's a way. To tell you the truth, I was wondering if it could be
> done
> in C++ with only the Standard Library. I've recently done that (qtchooser)
> and
> it wasn't very pleasant. And especially there's one snag for Windows: li
On quarta-feira, 10 de abril de 2013 19.28.10, Justin Ferguson wrote:
> > that make sense on Windows must be implemented on Windows before they are
> > accepted. Any changes made >anywhere must not break the build >on Windows
>
> please accept this criticism as earnest, heartfelt and with the best
st-bounces+scott.bloom=onshorecs@qt-project.org
[mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On Behalf Of
Thiago Macieira
Sent: Wednesday, April 10, 2013 5:37 PM
To: interest@qt-project.org
Subject: Re: [Interest] Apologies on the "bloat" thread (a.k.a yes Windows is
On quarta-feira, 10 de abril de 2013 23.03.53, Scott Aron Bloom wrote:
> Do you have a specification for what the perl script is required to do?
"Use the source, Luke!" ? :-)
Basically, it needs to scan all the *.h files in a given directory and
partially interpret the C++ class declarations in
hi,
On Apr 10, 2013 5:50 PM, "Thiago Macieira"
wrote:
>
> First of all, let me apologise for my behaviour in the thread on
"dependency
> bloat". I've re-read my first reply and it was clearly out of line. And
the
> number of off-ML messages I got also indicates that.
same.
> So, my deepest apol
horecs@qt-project.org
[mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On Behalf Of
Thiago Macieira
Sent: Wednesday, April 10, 2013 3:50 PM
To: interest@qt-project.org
Subject: [Interest] Apologies on the "bloat" thread (a.k.a yes Windows is still
important)
First of all
First of all, let me apologise for my behaviour in the thread on "dependency
bloat". I've re-read my first reply and it was clearly out of line. And the
number of off-ML messages I got also indicates that.
So, my deepest apologies for letting my personal feelings and frustrations
with Windows g
13 matches
Mail list logo
