. are well- defined tools with well-defined interfaces, manuals,
etc.. They are not internal helpers.
[1] we already copy the .dll files because of that problem and the DLLs
are
much larger, so copying the executables is no big deal.
--
Thiago Macieira - thiago.macieira (AT) intel.com
and they run
qmake for that. Those two are definitely not backwards compatible anymore.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
need to find a new name for Qt 5.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development
in creating shell aliases.
But I'll happily implement those changes if it helps!
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
as:
a) it exists
b) it works
c) it's the official and documented way of creating Qt applications in Qt 5
Any other names are under the customer's taste.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
*us* and our *users*.
The distros *will* apply renaming. And without our help, they may introduce
bugs and they will be definitely deviating from the documented way.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
about
the modality? Do people usually refer to it as the window modality? Food for
thought.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
4
and Qt5 builds in different directories.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
should be a shell script, a perl script or
another bootstrapped executable.
Please comment.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
. I linked to a bug report by the
Fedora packagers.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development
) that requires installing one more .pc file, in addition to the ones we have
d) the location of this pkg-config install is most likely *different* from
$libdir/pkgconfig.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
On sexta-feira, 19 de outubro de 2012 16.16.14, Thiago Macieira wrote:
1) we introduce a $libexecdir configuration option to qmake and
QLibraryInfo. For backwards compatibility, this $libexecdir will receive
the legacy names of QT_INSTALL_BINS and QLibraryInfo::BinariesPath. It will
default
-I${includedir}
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
On sábado, 20 de outubro de 2012 10.28.35, Stephen Kelly wrote:
On Saturday, October 20, 2012 10:30:36 Alberto Mardegan wrote:
On 10/20/2012 02:16 AM, Thiago Macieira wrote:
[...]
3) In addition, we'll create a *new* tool also called qmake that will be
I wonder how FindQt4.cmake
to comment on the proposal.
Preferably also list goals and non goals. For example Sune's concern that I
linked to before seems to have become a non-goal. Please make those things
explicit.
What concern?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
int*.
And now it is:
../../include/QtNetwork/private/../../../src/network/socket/qnet_unix_p.h,
line 126: Error: Formal argument 3 of type unsigned* in call to accept(int,
sockaddr*, unsigned*) is being passed int*.
Looks like the same error to me.
--
Thiago Macieira - thiago.macieira
/qnetworkinterface_unix.cpp vs.
socket/qhttpsocketengine.cpp
Both files #include the same header. So the error is still the same.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt
macro. It should be _POSIX_VERSION, not
_POSIX_C_SOURCE.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development
qmake, it might be problematic to have it
built from Qt 5 sources. It would need to be statically built and split
off during packaging so that it had no dependencies on Qt 5. If you can
achieve that, go ahead and write it in Qt.
Yup.
--
Thiago Macieira - thiago.macieira (AT) intel.com
this
tool, and e.g. on Windows to have that tool in the PATH and pointing to the
corresponding Qt for the environment set up shell scripts. In the SDK, the
tools/ directory might be a good place for it.
It's easy to add a -qt5 ignored option to the regular qmake too.
--
Thiago Macieira
keep this tool in
the qtbase package. I need to hear from distros here.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
is released along with QtCreator 2.6?
We are working on updating. The next SDK release will contain 5.0.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
known to him.
I think there's the only one clean way to deal with it: continue to support
xlib qpa plugin in parallel with xcb.
There's another: static link the XCB libraries into the plugin.
You need to have the libxcb-*.a files with -fPIC, that's all.
--
Thiago Macieira - thiago.macieira
it?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http
where to put its output. Since it's not
$$[QT_INSTALL_BINS], we need another path. But you're right that we don't need
the change to QLibraryInfo. If anyone ever needs to find and run those tools
(not counting their unit tests), QProcess is enough since it will search
$PATH.
--
Thiago Macieira
. Please submit the fixes and we'll incorporate them.
Don't expect that reporting the issue on the mailing list will trigger a fix.
We have no way of testing Solaris, so the fix must come from you in the form of
a patch.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect
://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open
On segunda-feira, 22 de outubro de 2012 21.21.17, André Pönitz wrote:
On Mon, Oct 22, 2012 at 09:08:38AM -0700, Thiago Macieira wrote:
On segunda-feira, 22 de outubro de 2012 15.45.56, Oswald
Buddenhagen wrote:
On Fri, Oct 19, 2012 at 04:16:14PM -0700, Thiago Macieira wrote:
Note
.
Indeed, it doesn't make much of a difference. So I'll just do the easiest,
which is to make the reading code simpler.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message
can be very well self-contained, as it has always been.
i strongly prefer to have it outside qt itself.
If we add the -qt5 option to the traditional qmake, then it can be
considered optional.
I still prefer to develop it inside qtbase.
--
Thiago Macieira - thiago.macieira (AT) intel.com
IMO)
I think all this becomes much too confusing.
If the option is required in one platform and does not cause anything but a
minor inconvenience on others, why not document it?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
applied.
Though I want to hear from distros what they think of the fact that Designer
is being put in the same bucket.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
.
If the option is required in one platform and does not cause anything but
a
minor inconvenience on others, why not document it?
So then will Qmake on Windows/Mac complain about the -qt5 argument? Or
simply drop it?
Drop it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
it.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http
. This case cannot exist for one
buildsystem that does know about Qt 5 anyway. Either that's two buildsystems
or it's one that knows about Qt 5.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally
not be a lot of (maintenance) work...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt
already
believed.
I really hope we choose Full Disclosure as our security model, as it
gives the _users_ the best opportunity to protect both themselves and
their end-users.
I do not and my reasons are above.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
will not be accepted.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
their minds.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http
. I can ask my colleagues
working on X, but my guess is that they don't have a private API the way we
do.
So as long as it's a newer version at runtime, it should work.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt
to be called from
wrong path when Qt is installed from the installer package.
There are a couple of people complaining about the same on Windows. Seen on
#qt, with 4.8.3.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
?
Please note that the actual hours being displayed are always correct, it's
just the TZ indication which is off.
It's got to be a glibc bug.
We only do:
tzset();
localtime();
Since we don't do anything special, I'm forced to conclude that the bug is in
glibc.
--
Thiago Macieira
/38342 (requirement, breaks Mac build
and I need help)
https://codereview.qt-project.org/38225 (creates libexec)
https://codereview.qt-project.org/38344 (the toolwrapper)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
/Source/JavaScriptCore/offlineasm/generate_offset
_extractor.rb llint\LowLevelInterpreter.asm LLIntDesiredOffsets.h
That's a Ruby script. You need to install Ruby too in order to build WebKit.
This time we will need RUBY. What next?
Erlang, Eiffel, Lua, or Tcl.
--
Thiago Macieira - thiago.macieira
them without the changes I've proposed in this
email. His changes conflict with mine, so one of the two of us will need to
adapt and rebase.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
On segunda-feira, 29 de outubro de 2012 15.20.20, Thiago Macieira wrote:
* Default paths:
The defaults on a regular Unix or Windows installs are:
-bindir$prefix/bin [unchanged]
-libdir$prefix/lib [unchanged]
-libexecdir$prefix/lib/qt5/libexec [new
On terça-feira, 30 de outubro de 2012 06.47.06, Алексей Павлов wrote:
2012/10/30 Thiago Macieira thiago.macie...@intel.com
Erlang, Eiffel, Lua, or Tcl.
Oh no problem :) Tomorrow I build all of these ))
P.S. Python, Tcl/Tk and Ruby I already build with mingw)
I was kidding, you know
On segunda-feira, 29 de outubro de 2012 18.51.10, Thiago Macieira wrote:
However, if you do a -prefix /usr configuration, then the layout will be:
/usr/binUser applications only (qdbus,
linguist, etc.) /usr/liblibs
/usr/lib
the difference between flex and win_flex? Note that there's a flex
with msysgit, so if we used flex instead of win_flex, it would make setups
easier.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
, is there a problem with adding these?
There's no problem in adding those. It's quite easy, actually.
For lupdate, I changed the .pro file and, at the end where it read:
load(qt_tool)
I changed to:
load(qt_wrapped_tool)
That's all.
--
Thiago Macieira - thiago.macieira
. And among the latter,
which ones need to be wrapped.
Finally, I am not listing the separation of paths for QML 1 and 2, since I
have not heard opposition to that fact. If I'm wrong, do speak up.
[*] consensus does not mean unanimity
--
Thiago Macieira - thiago.macieira (AT) intel.com
On terça-feira, 30 de outubro de 2012 23.52.08, André Pönitz wrote:
On Tue, Oct 30, 2012 at 01:47:03PM -0700, Thiago Macieira wrote:
5) executable split between end-user applications and indirect tooling
The most controversial proposal so far is to split the binaries into two
groups: one
in qtbase and see if the version in PATH is new enough. We can still try
to use a copy of qt5.git/gnuwin32 as fallback if we can locate it.
What is the minimum required version?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
be
symlinked?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http
On quarta-feira, 31 de outubro de 2012 09.46.18, Alberto Mardegan wrote:
On 10/31/2012 01:06 AM, Thiago Macieira wrote:
In any case, what's the problem with making a subjective decision? Clearly
the applications need to be split in two groups, so why shouldn't the Qt
Project make its
the
arguments on why we should not manage that on make install.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development
On quarta-feira, 31 de outubro de 2012 08.02.20, Thiago Macieira wrote:
On quarta-feira, 31 de outubro de 2012 12.23.27, Oswald Buddenhagen wrote:
3) library versioning (i.e., adding 5 to the library name)
-1
renaming is unnecessary:
- there is no problem at all at run-time
are simpler. They need to pass additional -
xxxdir options if they *choose* to according to their distro policies, not
because our defaults are incorrect.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
it.
What is the minimum required version?
I'm not exactly sure, but I know that 2.5.4 is too old (generated code
won't compile) and 2.5.35 seems to work well.
That's the one that comes with msysgit. Can we make the buildsystem use flex
if flex is available instead?
--
Thiago Macieira
On quinta-feira, 1 de novembro de 2012 09.23.37, Lincoln Ramsay wrote:
On 01/11/12 01:02, Thiago Macieira wrote:
Also, do I understand correctly that you're suggesting that multiarch
distributions should have *both*:
/usr/lib/qt5//bin/assistant AND
/usr
/kde4/plugins/:/home/thiago/kde/lib/plugins/:/usr/lib64/kde4/plugins
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
is unchanged.
Please note that we *can* have qmlviewer, provided it's the Qt Quick 1. It
works in either scenario of tooling: if it's in $PATH, it's via the
toolwrapper, in which case you run the Qt 5 version by adding the -qt5 option.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
On quinta-feira, 1 de novembro de 2012 11.56.25, Lincoln Ramsay wrote:
On 01/11/12 09:41, Thiago Macieira wrote:
On quinta-feira, 1 de novembro de 2012 09.23.37, Lincoln Ramsay wrote:
On 01/11/12 01:02, Thiago Macieira wrote:
Also, do I understand correctly that you're suggesting
for multiarch, requiring
features in their buildsystems that they don't have yet?
Do you quite realise how unreasonable this sounds?
On Wed, Oct 31, 2012 at 12:38:06PM -0700, Thiago Macieira wrote:
I disagree with leaving /usr/bin unmanaged at all. I want to hear the
arguments on why we should
hard since there's no mention in documentation which signals are limited
this way.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
/share/qt5 for installed builds only, ARCHDATADIR = DATADIR
PREFIX elsewhere.
I really, really, really want A, but I don't really mind either way for B.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
then 32-bit package to be installed on 32-bit systems. That's
a policy change.
On Wed, Oct 31, 2012 at 12:38:06PM -0700, Thiago Macieira wrote:
I disagree with leaving /usr/bin unmanaged at all. I want to hear the
arguments on why we should not manage that on make install
of the patches leads to options a and c
only. I need to split the patch that adds archdatadir so that option b is
opened up and we can apply the Qml2ImportsPath patch.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
On quinta-feira, 1 de novembro de 2012 14.49.27, Stephen Chu wrote:
Again. This is using clang 3.1 with QMAKE_CXXFLAGS += -std=c++11
Is that the real clang 3.1, or the 3.1 version of Apple clang? They are not
the same, they have different C++11 support status and known bugs.
--
Thiago
On quinta-feira, 1 de novembro de 2012 13.13.34, Thiago Macieira wrote:
On quinta-feira, 1 de novembro de 2012 14.49.27, Stephen Chu wrote:
Again. This is using clang 3.1 with QMAKE_CXXFLAGS += -std=c++11
Is that the real clang 3.1, or the 3.1 version of Apple clang? They are not
the same
of arguments from the receiver instead of
the sender? We did that for regular functions and member functions.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
this.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http
for this.
And connecting to functor works without C++11 (now, it is probably ok to
say that connecting to functor with less arguments than the signal is only
working with C++11)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
: PLUGIN_TYPE (plugins/ subdirectory) needs to be defined.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
a8fd0c3654f8352773638633778cd8003680cbc7 )
But since Jason has left (AFAIK?), the history repeat again
There have been a series of commits doing it in the other direction.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
a decision to release
it was made in spite of there being open tasks in the meta bug.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
to be done for the initial Qt 5 release.
It won't happen for Qt 5. It's way too late for that.
But tell me: what do you want to see in this common base class? What methods
from QAbstractSocket?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
, it will tell you why.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http
QListQIODevice * in your
case above? You said disconnect, read, write, all of which you can do with
QIODevice (close() is virtual, the signals are in QIODevice).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
platforms as Tier 1, provided they meet the other quality criteria,
even if they aren't in the CI.
Specifically, I'm thinking of QNX and, in turn, wondering if the team behind it
is committed to the quality effort to Tier 1 in 5.0.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
see how the connectTo* methods could be shared, and I don't
think it would be a good idea to try to do so.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
(QFile, QBuffer) and the sequential one (all the rest).
I'd like to see non blocking (or asynchronous) IO for files as well.
Would be interesting.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
. But, if it's relevant, it should
be added to Qt Quick 2 too (first?)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part
at the moment
of use.
My recommendation is that you do not allow relative URLs. Require them to be
absolute, in which case you'll need the file:/// prefix.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description
if they are
convenience for something you can already do by another method.
However, Qt 4.8 cannot receive new features nor new symbols. If there were a
Qt 4.9, we could add the change there.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
The 5 has been added to all Unix, except for Mac framework builds. On Windows,
the 5 has moved positions.
The patch has just passed through CI as
d725239c3e09c2b740a093265f6a9675fd2f8524
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology
[branch master]
remote = origin
merge = refs/heads/master
[branch test]
remote = origin
merge = refs/heads/master
*If anyone else has any idea, please help me with this.*
There's nothing wrong with your setup.
You can push to origin, since that's the Gerrit repository.
--
Thiago Macieira
://codereview.qt-project.org/#change,39385
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
exclusively
(not 32-bit-Windows)? (Has that day come?)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development
one shot tasks, we're missing a
good API to replace QtConcurrent for now.
I'd like to see someone give TBB a Qt-ish API wrapper.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed
On sábado, 17 de novembro de 2012 05.14.39, Lorn Potter wrote:
Hi,
So how is one supposed to build submodules that got removed by change
41c3f2cb5f633f0e540482ca01b2c2caa2475e57 ?
certainly make module-qtsensors is now broken.
cd qtsensors make
--
Thiago Macieira - thiago.macieira
On sábado, 17 de novembro de 2012, às 05.35.18, you wrote:
On 17/11/2012, at 5:27 AM, Thiago Macieira thiago.macie...@intel.com
wrote:
On sábado, 17 de novembro de 2012 05.14.39, Lorn Potter wrote:
Hi,
So how is one supposed to build submodules that got removed by change
anymore.
Config-tests are run by qmake, so I don't see a problem.
The commands above *must* work. If they don't, we just need to fix them.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally
committee if
anyone is interested.
We can't wait for C++1y, but we should instead try and influence it by
designing something nice.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally
On domingo, 18 de novembro de 2012 12.26.25, Sze Howe Koh wrote:
On 16 November 2012 07:39, Thiago Macieira thiago.macie...@intel.com
wrote:
I'd like to see someone give TBB a Qt-ish API wrapper.
How would the licensing work if, say, a Qt Commercial customer uses
Qt-wrapped TBB, encounters
reuse the
names QFuture and similar for further purposes, including whatever
replacements to QtConcurrent we come up with.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message
(provided it's approved).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt
an example of a thread pool used differently: the DNS resolver
code in QtNetwork. It uses 5 threads, regardless of how many CPU cores you
have. It involves a blocking call. And as such, it must not use the global
thread pool because it would prevent other tasks from running.
--
Thiago Macieira
801 - 900 of 6026 matches
Mail list logo
