On Sunday April 26 2020 20:16:33 René J.V. Bertin wrote:
>I was referring to code that just rolls their own implementation of the code
>in almost an given library. It's a bit of a pathological argument but I'd say
>it's beyond argument that you can always do that, whereas even exhaustive
On Sunday April 26 2020 18:19:28 David Faure wrote:
>> The possibility to use precompiled headers is only an argument here when
>> increased compilation times are brought up as an argument against such a
>> header. But that's not really an argument if you can continue to use just
>> the headers
On Sunday, April 26, 2020 5:50:40 PM CEST René J.V. Bertin wrote:
> On Sunday April 26 2020 16:58:10 David Faure wrote:
> >> As a side-note, I'd even argue that
> >> it would make sense to provide an all-inclusive header per framework,
> >> just
> >> like Apple's frameworks do.
> >
> >It's said to
On Sunday April 26 2020 16:58:10 David Faure wrote:
>> As a side-note, I'd even argue that
>> it would make sense to provide an all-inclusive header per framework, just
>> like Apple's frameworks do.
>
>It's said to improve compilation times with precompiled headers, but in
>practice nobody
On Sunday, April 26, 2020 4:32:46 PM CEST René J.V. Bertin wrote:
> On Sunday April 26 2020 15:46:35 David Faure wrote:
> >Well, yeah, you can't have it all.
>
> I suppose that the appropriate ECM could provide a function that returns the
> path to the "official" Qt headers (or an expression that
On Sunday April 26 2020 15:46:35 David Faure wrote:
>Well, yeah, you can't have it all.
I suppose that the appropriate ECM could provide a function that returns the
path to the "official" Qt headers (or an expression that evaluates to that
path) unless something like QT_HEADER_PATH is defined.
On Sunday, April 26, 2020 3:21:34 PM CEST René J.V. Bertin wrote:
> On Sunday April 26 2020 14:12:01 David Faure wrote:
> >> (and possibly LD_PRELOAD).
> >
> >I don't see why you would set LD_PRELOAD in this configuration.
>
> This may be necessary if even one of the multiple libraries that get
On Sunday April 26 2020 14:12:01 David Faure wrote:
>> (and possibly LD_PRELOAD).
>
>I don't see why you would set LD_PRELOAD in this configuration.
This may be necessary if even one of the multiple libraries that get loaded has
an old-style link to a Qt library which makes it ignore
On Saturday, April 25, 2020 2:23:34 PM CEST René J.V. Bertin wrote:
> Hi,
>
> A priori Qt guarantees that you can run binaries against a different, newer
> Qt version than they were built against, as long as no private APIs are
> used. This also works if that newer Qt version is installed
Hi,
A priori Qt guarantees that you can run binaries against a different, newer Qt
version than they were built against, as long as no private APIs are used. This
also works if that newer Qt version is installed elsewhere, provided you set
LD_LIBRARY_PATH correctly (and possibly LD_PRELOAD). I
10 matches
Mail list logo
