https://doc.qt.io/qt-5/resources.html
The resource files listed in the .qrc file are files that are part of the
application's source tree. *The specified paths are relative to the directory
containing the .qrc file.* Note that the listed resource files must be located
in the same directory as th
On 24/5/19 6:35 pm, René J.V. Bertin wrote:
Hi,
Is there a known issue when using QFDb::addApplicationFontFromData() or
QFDb::addApplicationFont() with an embedded resource path in Qt 5.9 on Mac? I'm
getting a crash; as far as I can tell the CTFontRef creation from the font data
succeeds but
At Sun, 26 May 2019 22:07:37 +0200 fro...@tungware.se wrote:
>
> On 2019-05-26 21:32, Robert Heller wrote:
> > I am trying to bundle a directory of files generated by Doxygen into a Qt
> > resource file, but I am getting a strange error from rcc. Here is the
> > transscript:
> >
> > Script star
On 2019-05-26 21:32, Robert Heller wrote:
I am trying to bundle a directory of files generated by Doxygen into a Qt
resource file, but I am getting a strange error from rcc. Here is the
transscript:
Script started on Sun 26 May 2019 03:09:18 PM EDT
gollum.deepsoft.com% less -X release/htmldoc.q
I am trying to bundle a directory of files generated by Doxygen into a Qt
resource file, but I am getting a strange error from rcc. Here is the
transscript:
Script started on Sun 26 May 2019 03:09:18 PM EDT
gollum.deepsoft.com% less -X release/htmldoc.qrc
release/html/open.png
Den sön 26 maj 2019 kl 17:15 skrev Thiago Macieira :
>
> On Saturday, 25 May 2019 02:43:11 PDT Giuseppe D'Angelo via Interest wrote:
> > On the other hand, Q_ASSUME(cond) tells the compiler that cond is true,
> > always. If cond is actually false at runtime, you have undefined
> > behavior. And sin
On Saturday, 25 May 2019 02:43:11 PDT Giuseppe D'Angelo via Interest wrote:
> On the other hand, Q_ASSUME(cond) tells the compiler that cond is true,
> always. If cond is actually false at runtime, you have undefined
> behavior. And since undefined behavior cannot happen, the compiler is
> free to
On Sunday May 26 2019 14:10:46 Elvis Stansvik wrote:
>to check if p is 1, else check if p is 2. With the default: added with
>the unreachable hint, it's enough for it to generate instructions to
>check if p is 1, because if it isn't, then it is 2 for sure (because
>the default:, which covers every
Il 26/05/19 12:36, René J. V. Bertin ha scritto:
Giuseppe D'Angelo via Interest wrote:
Hi,
On the other hand, Q_ASSUME(cond) tells the compiler that cond is true,
After reading the MS doc I sort of understand how you can use the construct to
implement a Q_UNREACHABLE (but in the example give
Den sön 26 maj 2019 kl 12:37 skrev René J. V. Bertin :
>
> Giuseppe D'Angelo via Interest wrote:
>
> Hi,
>
> > On the other hand, Q_ASSUME(cond) tells the compiler that cond is true,
>
> After reading the MS doc I sort of understand how you can use the construct to
> implement a Q_UNREACHABLE (but
Den sön 26 maj 2019 kl 12:37 skrev René J. V. Bertin :
>
> Giuseppe D'Angelo via Interest wrote:
>
> Hi,
>
> > On the other hand, Q_ASSUME(cond) tells the compiler that cond is true,
>
> After reading the MS doc I sort of understand how you can use the construct to
> implement a Q_UNREACHABLE (but
Den sön 26 maj 2019 kl 12:37 skrev René J. V. Bertin :
>
> Giuseppe D'Angelo via Interest wrote:
>
> Hi,
>
> > On the other hand, Q_ASSUME(cond) tells the compiler that cond is true,
>
> After reading the MS doc I sort of understand how you can use the construct to
> implement a Q_UNREACHABLE (but
Giuseppe D'Angelo via Interest wrote:
Hi,
> On the other hand, Q_ASSUME(cond) tells the compiler that cond is true,
After reading the MS doc I sort of understand how you can use the construct to
implement a Q_UNREACHABLE (but in the example given I don't see the codegen
advantage of `default:
13 matches
Mail list logo
