From: yopito <yopito@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Qt pyside : update to 5.15.2
Date: Fri, 22 Jan 2021 19:51:08 +0100 [thread overview]
Message-ID: <20210122185108.w_r7gneL-zyrkeIufTDAd_qXxna5DZZ3t3GOomq1MzM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26962@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
New comment by yopito on void-packages repository
https://github.com/void-linux/void-packages/pull/26962#issuecomment-765610902
Comment:
Since qt5 is built with gcc, adding `-isystem /usr/armv7l-linux-gnueabihf/usr/include/c++/10.2/armv7l-linux-gnueabihf` to clang make it happy !
manual build once packaging failed as usual:
```
(chroot) $ clang --target=armv7l-linux-gnueabihf --sysroot=/usr/armv7l-linux-gnueabihf \
-fPIC -Wno-constant-logical-operand -std=c++14 \
-I/usr/armv7l-linux-gnueabihf/usr/include/qt5 \
-isystem/usr/armv7l-linux-gnueabihf/usr/include/c++/10.2/armv7l-linux-gnueabihf \
/tmp/QtCore_global_XSznox.hpp
=> no error, a .gch file has been generated:
/tmp/QtCore_global_XSznox.hpp
/tmp/QtCore_global_XSznox.hpp.gch
```
Related to gcc internals for C++, its equivalent of clang's systoot I guess ?
Keep on digging
Edit: reinvent the wheel that q66 already explained just aboved. At least, this is the same wheel.
next prev parent reply other threads:[~2021-01-22 18:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 13:27 [PR PATCH] [WIP] Qt pyside 5.12.2 yopito
2020-12-05 22:49 ` ericonr
2020-12-05 23:18 ` ericonr
2020-12-05 23:19 ` ericonr
2020-12-06 9:06 ` yopito
2020-12-19 15:48 ` [PR PATCH] [Updated] [WIP] Qt pyside 5.15.2 yopito
2020-12-19 16:18 ` yopito
2020-12-19 17:53 ` yopito
2020-12-19 17:55 ` yopito
2020-12-20 10:43 ` [PR PATCH] [Updated] " yopito
2020-12-20 12:33 ` yopito
2020-12-20 12:35 ` yopito
2020-12-26 4:58 ` sgn
2020-12-26 5:10 ` ericonr
2020-12-26 11:13 ` yopito
2020-12-26 19:57 ` ericonr
2021-01-16 20:06 ` [PR PATCH] [Updated] " yopito
2021-01-16 20:14 ` yopito
2021-01-17 0:33 ` Qt pyside : update to 5.15.2 yopito
2021-01-17 1:27 ` ericonr
2021-01-17 3:11 ` q66
2021-01-17 10:27 ` yopito
2021-01-17 19:06 ` [WIP] " ericonr
2021-01-17 19:25 ` ericonr
2021-01-17 19:26 ` ericonr
2021-01-17 19:50 ` yopito
2021-01-17 20:01 ` ericonr
2021-01-17 20:04 ` ericonr
2021-01-18 0:27 ` ericonr
2021-01-18 19:29 ` yopito
2021-01-18 19:33 ` ericonr
2021-01-22 18:40 ` yopito
2021-01-22 18:51 ` yopito [this message]
2021-01-23 18:59 ` [PR PATCH] [Updated] " yopito
2021-01-23 22:35 ` yopito
2021-01-24 8:19 ` yopito
2021-01-26 21:22 ` [PR REVIEW] " ericonr
2021-01-26 21:38 ` q66
2021-01-26 22:46 ` yopito
2021-01-26 23:16 ` ericonr
2021-01-26 23:43 ` sgn
2021-01-27 19:10 ` [PR PATCH] [Updated] " yopito
2021-01-27 19:14 ` [PR REVIEW] " yopito
2021-01-27 22:15 ` ericonr
2021-01-27 22:55 ` [PR PATCH] [Updated] " yopito
2021-01-27 22:55 ` [PR REVIEW] " yopito
2021-01-28 0:15 ` q66
2021-01-28 3:33 ` [PR PATCH] [Closed]: " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210122185108.w_r7gneL-zyrkeIufTDAd_qXxna5DZZ3t3GOomq1MzM@z \
--to=yopito@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).