On 26/08/13 05:53, Hugo Drumond Jacob wrote:
> Hi Simone!
>
> You will use "meta-toolchain" target. However, you need add dependences
> to Qt5. Tomorrow, I can help you more (in pvt), because today I'm out of
> office!
May I suggest that you communicate on oe-dev or yocto ml instead of
private? m
hi all:
|wordparser.target = generated_source
wordparser.commands = build.bat
wordparser.depends = FORCE
wordparser.CONFIG = recursive
QMAKE_EXTRA_TARGETS += wordparser
PRE_TARGETDEPS += wordparser
TEMPLATE = vcapp
TARGET = demo
SOURCES = stub_test.cpp
|
build.bat generates lot’s of files that ar
Finally I was able to port my bittorrent client from Qt4 to Qt5. I already
ported some stuff this way. But this was really the hardest code to port, yet.
QHttp -> QNetworkAccessManager... ok. Minor problems, but no serious challenge.
However, one change is really evil: That there is no
connect
On domingo, 25 de agosto de 2013 20:48:29, Guido Seifert wrote:
> > See https://codereview.qt-project.org/47395
>
> Great. Seems to get in its final phase, soon. Your last comment: 'You can't
> insert here...'. Dammit, I would never have seen this.
There's a reason why we do reviews :-)
And ther
> > I think if QNetworkAccessManager and related classes are supposed to be the
> > main handlers to send and receive network traffic, it must be possible to
> > have 100% control over every single bit, which goes over the line.
>
> See https://codereview.qt-project.org/47395
Great. Seems to get
On domingo, 25 de agosto de 2013 16:43:22, Guido Seifert wrote:
> What I discovered: The QNetWorkRequest adds automatically 'stuff' to the
> header, e.g. "User-Agent: Mozilla/5.0". Hey? I am not Mozilla/5.0. Where
> does this come from?
>
> I think if QNetworkAccessManager and related classes ar
Hi Simone!
You will use "meta-toolchain" target. However, you need add dependences to
Qt5. Tomorrow, I can help you more (in pvt), because today I'm out of
office!
Hugo Drumond Jacob
Eng. de Controle e Automação - CREA-MG 143908/LP
Mestrando em Modelagem Matemática e Computacional - CEFET/MG
h...
> You can also just cherry-pick the changes into 5.1.
Thanks, Thiago, but this is only half as much fun. :-)
So I did checkout dev 5.2. And the new QUrl works like a charm. BUT... there is
always a but. I am still not happy. The reason why the trackers did not
recognize the info_hash was not
void bar (QIODevice& zzz)
{
// ...
zzz.close(); // Oops
}
void foo ()
{
QTemporaryFile file;
bar(file);
}
The function bar() may be replaced by anything that doesn't care what type
I/O object to work with (e.g. QDataStream). "Why the hell does a function
close an object owned by s
