On Wednesday, 23 October 2019 17:00:47 PDT Simon Matthews wrote:
> ticks.cc:(.text._Z8TicksNowv+0x1c): undefined reference to `clock_gettime'
> ticks.cc:(.text._Z8TicksNowv+0x5a): undefined reference to `clock_gettime'
> collect2: error: ld returned 1 exit status
>
> This appear to be a problem th
I am getting a failure in linking:
/opt/rh/devtoolset-8/root/usr/bin/g++ -O3 -fdata-sections
-ffunction-sections -Wl,--gc-sections -Wl,-strip-all -static-libstdc++
-Wl,--as-needed -pthread -o gn -Wl,--start-group tools/gn/gn_main.o
base.a gn_lib.a -Wl,--end-group -ldl
util/ticks.o: In function `Tic
On Thursday, 10 October 2019 10:54:45 PDT Simon Matthews wrote:
> Is it possible to use an older version of Chromium that will work with
> Glibc 2.12 (that's what is installed in CentOS 6)?
You don't want that. This is a browser engine, which means you really, really
want the fixes to security is
On 10/9/19 5:54 PM, Thiago Macieira wrote:
> On Wednesday, 9 October 2019 16:07:46 PDT Simon Matthews wrote:
>> [simon@UserBuild qtwebengine]$ make
>> make: Nothing to be done for 'first'.
> That indicates it did not configure itself to build. I ran into this issue
> today: one of my colleagues is
On Thursday, 10 October 2019 01:07:46 CEST Simon Matthews wrote:
> On 10/9/19 3:52 PM, Thiago Macieira wrote:
>
> > On Wednesday, 9 October 2019 15:18:33 PDT Simon Matthews wrote:
> >
> >> However, it appears that files such as "Qt5WebEngineConfig.cmake" are
> >> not included in my build.
> >>
>
On Wednesday, 9 October 2019 16:07:46 PDT Simon Matthews wrote:
> [simon@UserBuild qtwebengine]$ make
> make: Nothing to be done for 'first'.
That indicates it did not configure itself to build. I ran into this issue
today: one of my colleagues is workng to remove Python2 from the distribution
a
On 10/9/19 3:52 PM, Thiago Macieira wrote:
> On Wednesday, 9 October 2019 15:18:33 PDT Simon Matthews wrote:
>> However, it appears that files such as "Qt5WebEngineConfig.cmake" are
>> not included in my build.
>>
>> Is it necessary to build QtWebEngine as a separate build?
> No.
>
> Are you sure t
On Wednesday, 9 October 2019 15:18:33 PDT Simon Matthews wrote:
> However, it appears that files such as "Qt5WebEngineConfig.cmake" are
> not included in my build.
>
> Is it necessary to build QtWebEngine as a separate build?
No.
Are you sure the build completed without errors? To be sure, go in
On 10/8/19 11:46 PM, Thiago Macieira wrote:
> On Tuesday, 8 October 2019 14:16:28 PDT Simon Matthews wrote:
>> I am trying to build Qt 5.13.1 on CentOS6.
>
> You're missing xkbcommon. Please install 0.5.0 or later.
I was able to find appropriate packages for xkbcommon and build Qt 5.13.1.
I need
> Le 17 mai 2018 à 14:26, Kai Koehne a écrit :
>
>
>
>> -Original Message-
>> From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org] On
>> Behalf Of Jérôme Laheurte
>> Sent: Thursday, May 17, 2018 2:12 PM
>> To: Qt Project
&
> -Original Message-
> From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org] On
> Behalf Of Jérôme Laheurte
> Sent: Thursday, May 17, 2018 2:12 PM
> To: Qt Project
> Subject: [Interest] Building QtWebEngine with Visual 2017
> [...]
> Nee
Hello. I’m trying to build QtWebEngine with h264 support on Windows. I
installed Qt 5.10.1 (msvc2017_64) and the source. Running qmake gives:
> qmake
Running configuration tests...
Done running configuration tests.
Configure summary:
Qt WebEngine:
Embedded build . no
On Friday March 13 2015 12:48:06 Thiago Macieira wrote:
> No. The arguments are stored in the Makefile itself.
Well, so then that cannot explain the issues I'm seeing. I'm starting without a
Makefile.
R.
___
Interest mailing list
Interest@qt-project.o
On Friday 13 March 2015 17:58:51 René J.V. Bertin wrote:
> On Friday March 13 2015 09:45:08 Thiago Macieira wrote:
> > qmake stores the arguments you gave it on the command-line and will always
>
> That's what the -nocache argument is supposed to prevent, I presume? FWIW,
> using that argument thr
On Friday March 13 2015 09:45:08 Thiago Macieira wrote:
> qmake stores the arguments you gave it on the command-line and will always
That's what the -nocache argument is supposed to prevent, I presume? FWIW,
using that argument throws an error when doing `qmake qtwebengine.pro`
> However, if y
On Friday 13 March 2015 17:40:10 René J.V. Bertin wrote:
> But that just exposes another issue. The gyp generator insists on adding a
> -Dtarget_arch=x64 option, but in the end the ninja.build file is the only
> one that is configured correctly for building 32bit on a 64bit platform.
> Apparently I
On Friday March 13 2015 09:14:32 Thiago Macieira wrote:
Hi,
> > The isPlatformSupported test for QtWebEngine has the following line
> >
> > linux-g++*|win32-msvc2013|macx-clang: return(true)
> >
> > which means that the test fails for the mkspec macx-clang-32 . Does that
> > mean the componen
On Friday 13 March 2015 11:09:17 René J.V. Bertin wrote:
> Hi,
>
> The isPlatformSupported test for QtWebEngine has the following line
>
> linux-g++*|win32-msvc2013|macx-clang: return(true)
>
> which means that the test fails for the mkspec macx-clang-32 . Does that
> mean the component cannot
Hi,
The isPlatformSupported test for QtWebEngine has the following line
linux-g++*|win32-msvc2013|macx-clang: return(true)
which means that the test fails for the mkspec macx-clang-32 . Does that mean
the component cannot be built on 32bit OS X, and if so, how come the test
appears like it w
19 matches
Mail list logo
