25.10.2017, 23:56, "Thiago Macieira" :
> On Wednesday, 25 October 2017 13:32:29 PDT Christian Gagneraud wrote:
>> On 25/10/2017 11:12 PM, Maurice Kalinowski wrote:
>> > The reason is that code.qt.io is never meant as a public searchable
>> > tool, but its purpose has always been to reduce the
On Wednesday, 25 October 2017 22:01:50 PDT Christian Gagneraud wrote:
> Go on Thiago! Say it please: "it would be really nice if more Qt repos
> would be searchable from google or github" ;)
I never denied that. Of course they would.
Though in my case, I usually already know where what I'm lookin
On 26/10/2017 5:51 PM, Thiago Macieira wrote:
On Wednesday, 25 October 2017 21:47:07 PDT Christian Gagneraud wrote:
results:
https://github.com/apple/darwin-xnu/search?utf8=%E2%9C%93&q=read_random+&typ
e=
Answer is item 6: osfmk/prng/random.c
See, it works! ;)
Hmmm...
This also works *now*:
On Wednesday, 25 October 2017 21:47:07 PDT Christian Gagneraud wrote:
> results:
> https://github.com/apple/darwin-xnu/search?utf8=%E2%9C%93&q=read_random+&typ
> e=
>
> Answer is item 6: osfmk/prng/random.c
>
> See, it works! ;)
Hmmm...
This also works *now*:
https://github.com/apple-opensource
On 26/10/2017 4:55 PM, Thiago Macieira wrote:
On Wednesday, 25 October 2017 20:03:43 PDT Christian Gagneraud wrote:
Even "read_random xnu site:github.com" returns the result that point to
bsd/sys/random.h in the apple/darwin-xnu repo (ranked 4 for me)
By the way, I was looking for the implemen
On Wednesday, 25 October 2017 20:03:43 PDT Christian Gagneraud wrote:
> Even "read_random xnu site:github.com" returns the result that point to
> bsd/sys/random.h in the apple/darwin-xnu repo (ranked 4 for me)
By the way, I was looking for the implementation of this function, not the
header defin
On 26/10/2017 12:05 PM, Thiago Macieira wrote:
On Wednesday, 25 October 2017 15:41:48 PDT Christian Gagneraud wrote:
Interesting "read_random site:github.com/apple/darwin-xnu" returns 6
results. One of them points to bsd/sys/random.h, is this your missing
include? ;P
Yes, is what we are missi
On Wednesday, 25 October 2017 15:41:48 PDT Christian Gagneraud wrote:
> Interesting "read_random site:github.com/apple/darwin-xnu" returns 6
> results. One of them points to bsd/sys/random.h, is this your missing
> include? ;P
Yes, is what we are missing. The Linux and OpenBSD getentropy()
funct
On 26/10/2017 11:21 AM, Thiago Macieira wrote:
On Wednesday, 25 October 2017 14:47:43 PDT Christian Gagneraud wrote:
Considering the contents of that website change very frequently, I'd
assume
that the reason is either that there's no point indexing something that
becomes stale quickly or that t
On Wednesday, 25 October 2017 14:47:43 PDT Christian Gagneraud wrote:
> > Considering the contents of that website change very frequently, I'd
> > assume
> > that the reason is either that there's no point indexing something that
> > becomes stale quickly or that they want to reduce the workload on
On 26/10/2017 9:55 AM, Thiago Macieira wrote:
On Wednesday, 25 October 2017 13:32:29 PDT Christian Gagneraud wrote:
On 25/10/2017 11:12 PM, Maurice Kalinowski wrote:
The reason is that code.qt.io is never meant as a public searchable
tool, but its purpose has always been to reduce the load on g
On Wednesday, 25 October 2017 13:32:29 PDT Christian Gagneraud wrote:
> On 25/10/2017 11:12 PM, Maurice Kalinowski wrote:
> > The reason is that code.qt.io is never meant as a public searchable
> > tool, but its purpose has always been to reduce the load on gerrit
> > when doing initial clones.
> >
On 25/10/2017 11:12 PM, Maurice Kalinowski wrote:
The reason is that code.qt.io is never meant as a public searchable
tool, but its purpose has always been to reduce the load on gerrit
when doing initial clones.
Come on people, it's not that everything is meant to be purely evil,
but as code.qt.
2017-10-25 16:16 GMT+02:00 Konstantin Tokarev :
>
>
> 25.10.2017, 12:55, "Christian Gagneraud" :
>> Google returns no result because the Qt company refuses to publish its
>> open source tools in an open manner: code.qt.io explicitly expresses
>> that it does not wish to be indexed by search engines
25.10.2017, 12:55, "Christian Gagneraud" :
> On 25/10/17 22:25, Benjamin TERRIER wrote:
>> Hi,
>>
>> To get an idea of how patching Qt5 works, one can look at the function
>> patchQtCore() used in windeployqt.
>> It will give you an idea of how its done on windows.
>>
>> http://code.qt.io/cg
2017-10-25 12:12 GMT+02:00 Maurice Kalinowski :
> The reason is that code.qt.io is never meant as a public searchable tool, but
> its purpose has always been to reduce the load on gerrit when doing initial
> clones.
>
> Come on people, it's not that everything is meant to be purely evil, but as
urice
> -Original Message-
> From: Interest [mailto:interest-bounces+maurice.kalinowski=qt.io@qt-
> project.org] On Behalf Of Benjamin TERRIER
> Sent: Wednesday, October 25, 2017 12:08 PM
> To: Christian Gagneraud
> Cc: qt qt
> Subject: Re: [Interest] [Development] Qt inst
That explains why I always end up on clones when I use a search engine... sad.
Sometimes I feel like The Qt Company doesn't totally appreciate the
open source side of Qt.
Anyway it is easier to use Woboq clone, they have nice code browsing
functionalities:
https://code.woboq.org/qt5/qttools/src/wi
On 25/10/17 22:25, Benjamin TERRIER wrote:
Hi,
To get an idea of how patching Qt5 works, one can look at the function
patchQtCore() used in windeployqt.
It will give you an idea of how its done on windows.
http://code.qt.io/cgit/qt/qttools.git/tree/src/windeployqt/utils.cpp#n948
Thank you for
Hi,
To get an idea of how patching Qt5 works, one can look at the function
patchQtCore() used in windeployqt.
It will give you an idea of how its done on windows.
http://code.qt.io/cgit/qt/qttools.git/tree/src/windeployqt/utils.cpp#n948
BR,
Benjamin
2017-10-18 9:17 GMT+02:00 Christian Gagnerau
On 18/10/2017 8:08 pm, "Thiago Macieira" wrote:
[moving to the interest mailing list; please drop development@ when
replying]
On Tuesday, 17 October 2017 23:38:24 PDT bhaskar kotha wrote:
> How to configure Qt so that Qmake should not take absolute path.
That's not possible. You can't move Qt:
[moving to the interest mailing list; please drop development@ when replying]
On Tuesday, 17 October 2017 23:38:24 PDT bhaskar kotha wrote:
> How to configure Qt so that Qmake should not take absolute path.
That's not possible. You can't move Qt: you have to decide where it's going to
be the mom
22 matches
Mail list logo
