Unsolved Porting to a new platform
-
I realize this question may be too broad for anyone to answer directly, but let's give it a try.
QtWebEngine is only supported on Linux, Windows and Mac. I'm interested in building it for QNX. This may not be as far fetched as it may sound considering that both Qt 5.15 and Blink work on this platform. I'm looking for some guidelines as to how to get from here to there: given a working copy of Qt 5.15 and a working Blink v80, what are the next steps? Of course, I'll take a properly-justified "this cannot be done" (begrudgingly).Thanks,
--Elad -
Hi,
I would start by editing the configure.pri of QtWebEngine to allow the build to proceed for QNX.
Are you building blink yourself ?
-
What I have done so far is
- Added QNX to
configure.pri - Built nss
- Built Python2, which is no longer supported on QNX (Python2 reached end of life over a year ago, why is it used by QtWebEngine?)
- Removed the check for
glibcas a requirement for a UNIX build
That gets me through the
qmakephase.From the documentation it seems that QtWebEngine has its own copy of blink. Is that correct? If so, can it use a native version, or is it tied to the built-in one?
--Elad
- Added QNX to
-
By the way, there is a bug in the ninja detection function. I have the latest version (1.10), but it is considered as "too old" because
qtConfTest_detectNinjachecks for the regular expression1.[7-9].*--Elad
-
@elahav said in Porting to a new platform:
Built Python2, which is no longer supported on QNX (Python2 reached end of life over a year ago, why is it used by QtWebEngine?)
Because of chromium which is the underlying tech that QtWebEngine is built on top of.
@elahav said in Porting to a new platform:
From the documentation it seems that QtWebEngine has its own copy of blink. Is that correct?
As noted above, it's built on top of Chromium. I do not know if you can easily rip that part out to use your blink build in place.
-
Elad -
How far did you get with a WebEngine port?
Jim
