Oswald Buddenhagen wrote:
> feedback to them from the features. if the effect you're describing is
> genuine, there is something seriously screwed up in the qmake internals;
> you may get useful reports from valgrind or asan.
HAH! Would you believe I can no longer reproduce the error I copied
Oswald Buddenhagen wrote:
>>
> that makes just no sense whatsoever. the command line options are
> declared in a separate section near the top of the file, and there is no
That's what I had been thinking all the time too. It's only when you draw my
attention to config_help.txt and saw the
On Fri, Jan 20, 2017 at 09:14:00PM +0100, René J. V. Bertin wrote:
> Oswald Buddenhagen wrote:
>
>
> > check whether qtmultimedia/{config_help.txt,configure.json} exist and
>
> They do.
>
> > claim support.
>
> I think I can do better: apparently I have found the culprit. In the Features
>
Oswald Buddenhagen wrote:
> check whether qtmultimedia/{config_help.txt,configure.json} exist and
They do.
> claim support.
I think I can do better: apparently I have found the culprit. In the Features
section of qtmultimedia/src/multimedia/configure.json:
"pulseaudio": {
Thiago Macieira wrote:
> Don't assume. The question stands.
QED:
%> rm -rf /path/to/build/qtmultimedia
%> tar -xf /path/to/qt-everywhere-opensource-src-5.8.0-rc.tar.xz qt-everywhere-
opensource-src-5.8.0-rc/qtmultimedia
%> (cd /path/to/build ;
On Thu, Jan 19, 2017 at 10:20:59PM +0100, René J. V. Bertin wrote:
> Let me try to reformulate the question: what options must I pass to
> ../qt-everywhere-opensource-src-5.8.0-rc/configure so that the qtmultimedia
> component is built without pulseaudio and gstreamer support?
>
check whether
Edward Welbourne wrote:
> which I suppose to be fairly explicit about which configure script he's
> talking about.
Thanks, Eddy.
I know it's important to avoid ambiguity, but I have also mentioned from the
beginning that I was doing a top-level build and it simply didn't occur to me
On quinta-feira, 19 de janeiro de 2017 22:20:59 PST René J. V. Bertin wrote:
>> I've also been talking since the beginning about configure. Sorry
>> about the confusion.
Thiago Macieira replied:
> There are two configure scripts: one in the top-level and one in
> qtbase. Please be clear which one
On quinta-feira, 19 de janeiro de 2017 22:20:59 PST René J. V. Bertin wrote:
> I've also been talking since the beginning about configure. Sorry about the
> confusion.
There are two configure scripts: one in the top-level and one in qtbase. Please
be clear which one you mean.
--
Thiago
Oswald Buddenhagen wrote:
> that doesn't matter. the point is that you talked about qtbase.pro
> instead of the top-level project qt.pro.
I've also been talking since the beginning about configure. Sorry about the
confusion. That configure script is obfuscated enough to make it very easy to
On Thu, Jan 19, 2017 at 02:40:43PM +0100, René J. V. Bertin wrote:
> Oswald Buddenhagen wrote:
> > that's what happens when you don't follow my instructions. i explicitly
> > told you that the configure approach is for a top-level (qt5.git) build.
>
> You wrote
> >> if you're doing a top-level
Oswald Buddenhagen wrote:
>>
> that's what happens when you don't follow my instructions. i explicitly
> told you that the configure approach is for a top-level (qt5.git) build.
You wrote
>> if you're doing a top-level build, you just pass it to configure.
I'm doing a top-level build, not
On Wed, Jan 18, 2017 at 04:57:34PM +0100, René J. V. Bertin wrote:
> Oswald Buddenhagen wrote:
> > if you're doing a top-level build, you just pass it to configure.
>
> But how? Configure now yells on -no-pulseaudio :
> >> ERROR: Unknown command line option '-no-pulseaudio'.
>
> And that error
Thiago Macieira wrote:
> Don't assume. The question stands.
Actually the answer is yes. If this message is printed as a red herring, that's
a bug, so also a problem. It would mean that even with the libraries present I
couldn't build WITH support for GStreamer and/or PulseAudio.
As Oswald
On quarta-feira, 18 de janeiro de 2017 18:29:16 PST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > Please confirm whether you have a real problem or just a red herring.
>
> The configure summary claims it will build with support for GStreamer 1.0
> and PulseAudio. Assuming that claim is
On quarta-feira, 18 de janeiro de 2017 03:08:03 PST René J.V. Bertin wrote:
> But yet the configure process picks up both PulseAudio and GStreamer 1.0. As
> expected this still happens when I out-comment the relevant lines in the
> above snippet.
The section you pasted has nothing to do with the
Oswald Buddenhagen wrote:
> if you're doing a top-level build, you just pass it to configure.
But how? Configure now yells on -no-pulseaudio :
>> ERROR: Unknown command line option '-no-pulseaudio'.
And that error comes from qmake, possibly because it doesn't know this option
when processing
On Wed, Jan 18, 2017 at 03:08:03AM -0800, René J.V. Bertin wrote:
> What happened with the --no-pulseaudio configure argument? I get the
> impression that one can supposedly pass arguments to QtMultiMedia's
> configure step, but how does that work?
>
if you're doing a top-level build, you just
Seems the configure process also picks up the X11 libGL when it's available.
I used to protect against that in the configure script, but the OpenGL
detection
logic has been moved from out of there, too :-/
diff --git a/qtbase/configure b/qtbase/configure
index 0b8b417..91c6bc1 100755
---
Hi,
Still tinkering with Qt 5.8, now doing a more complete "toplevel" build on Mac.
I have PulseAudio and Gstreamer 1.0 installed in the target prefix, but those
are strictly for use with GTk/Gnome apps, I don't want to introduce
dependencies on these libraries in Qt.
I see that
20 matches
Mail list logo
