Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Thiago Macieira
On Monday, 24 July 2017 16:26:10 PDT Thiago Macieira wrote:
> This can also happen intra-Qt too, if you're doing split builds. Suppose
> you're building qtmultimedia again but it's already installed. You need to
> link to qtbase libraries, so the -L for the install dir is provided. That
> means the old set of libraries may be found.

And note how the search order for libraries used indirectly is different from 
those of libraries used directly.

I've given up on this problem. Martin and Kevin are welcome to work with Ossi 
on adding even more code to address even more corner cases. I won't lift a 
finger, I don't think it's good use of my time.

PS: I suspect it's already solved for dev branch because qgsttools_p is now a 
regular module, so there's nothing to be done there and an invasive change to 
5.9 won't be accepted.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Thiago Macieira
On Monday, 24 July 2017 15:20:07 PDT Allan Sandfeld Jensen wrote:
> It is a work-around, but it is an issue that pops up frequently and can take
> a while until solved. I do have development files of the system Qt
> installed, and it usually works just fine. When it does pop up it is
> however quite tricky to solve because if any pkg-config files add a system
> include directory to the compile command line, things break. Getting the
> correct order of includes on and gcc command line is impossible, so the
> only way of not getting a system header sneak in before the right Qt header
> is to make sure system include paths are never be explicitly specified, and
> that requires well-maintained bug-free devel packages.

That doesn't work when we're talking about another set of include paths that 
are not the system's.

This can also happen intra-Qt too, if you're doing split builds. Suppose 
you're building qtmultimedia again but it's already installed. You need to 
link to qtbase libraries, so the -L for the install dir is provided. That 
means the old set of libraries may be found.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Allan Sandfeld Jensen
On Sonntag, 23. Juli 2017 22:49:11 CEST Martin Koller wrote:
> On Sonntag, 23. Juli 2017 18:54:41 CEST Thiago Macieira wrote:
> > On Sunday, 23 July 2017 01:50:10 PDT Martin Koller wrote:
> > > I found this symbol to be in the qgsttools_p lib but I fear the linker
> > > takes the lib from a wrong path.
> > 
> > If you already have Qt installed system-wide, please remove the
> > development
> > files. You said you're on OpenSUSE, so just remove the Qt -devel packages.
> 
> Ouch.
> I assume this is just a workaround, and not "the solution", right ?
> 
It is a work-around, but it is an issue that pops up frequently and can take a 
while until solved. I do have development files of the system Qt installed, 
and it usually works just fine. When it does pop up it is however quite tricky 
to solve because if any pkg-config files add a system include directory to the 
compile command line, things break. Getting the correct order of includes on 
and gcc command line is impossible, so the only way of not getting a system 
header sneak in before the right Qt header is to make sure system include 
paths are never be explicitly specified, and that requires well-maintained 
bug-free devel packages.

So the issue might not even be Qt, but your distros.

'Allan

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Thiago Macieira
On Monday, 24 July 2017 13:30:24 PDT Martin Koller wrote:
> On Montag, 24. Juli 2017 16:52:05 CEST Thiago Macieira wrote:
> > On Monday, 24 July 2017 04:26:55 PDT Martin Koller wrote:
> > > Why does my Qt build use the system installed
> > > /usr/lib64/libqgsttools_p.prl
> > > file and not the one from the build dir
> > 
> > "Because it was found".
> 
> Then the solution is to make whatever found it, to find my Qt-build's
> version first, right ?

Easier said than done. Hence my recommendation to remove the file in the first 
place (if possible, the entire package that installed it).

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Martin Koller
On Montag, 24. Juli 2017 16:52:05 CEST Thiago Macieira wrote:
> On Monday, 24 July 2017 04:26:55 PDT Martin Koller wrote:
> > Why does my Qt build use the system installed /usr/lib64/libqgsttools_p.prl
> > file and not the one from the build dir
> 
> "Because it was found".

Then the solution is to make whatever found it, to find my Qt-build's version 
first, right ?

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\- against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Martin Koller
On Montag, 24. Juli 2017 08:34:56 CEST Thiago Macieira wrote:
> On Sunday, 23 July 2017 23:03:04 PDT Kevin Kofler wrote:
> > Thiago Macieira wrote:
> > > This is the root of your problem. Something that this plugin or
> > > qgsttools_p needs to link to said that its libraries are in /usr/lib64.
> > > qmake has some code to remove system paths, but it that won't work if the
> > > 
> > > path being requested is both:
> > >  a) not system
> > >  b) where Qt libraries are
> > 
> > /usr/lib64 is most definitely a system path. This is where 64-bit libraries
> > belong to according to the FHS.
> 
> Agreed. You have a double (or even triple) failure causing your problem.
> 
> qmake should have removed /usr/lib64 but didn't. That means the configure 
> detection of what the system linker paths are failed. See any of the 
> .qmake.stash files to see what it did detect, if anything.

QMAKE_CXX.LIBDIRS = \
/usr/lib64/gcc/x86_64-suse-linux/4.8 \
/usr/lib64 \
/lib64 \
/usr/x86_64-suse-linux/lib \
/lib \
/usr/lib

> Then there's the second issue that something did add /usr/lib64. It shouldn't 
> have. But it might be from a .prl file, which is much stupider than 
> pkg-config.

That comes from the system installed /usr/lib64/libqgsttools_p.prl
which was installed by the openSuse rpm  libqt5-qtmultimedia-devel-5.9.1

it contains:

QMAKE_PRO_INPUT = gsttools.pro
QMAKE_PRL_TARGET = libqgsttools_p.so.1.0.0
QMAKE_PRL_CONFIG = lex yacc depend_includepath testcase_targets import_plugins 
import_qpa_plugin qt_build_extra file_copies qmake_use qt warn_on release 
link_prl incremental shared release linux unix posix gcc sse2 sse3 ssse3 sse4_1 
sse4_2 avx avx2 compile_examples enable_new_dtags f16c largefile nostrip 
prefix_build force_independent utf8_source create_prl link_prl prepare_docs 
qt_docs_targets no_private_qt_headers_warning QTDIR_build qt_example_installs 
exceptions_off testcase_exceptions explicitlib have_target dll c++11 thread uic 
opengl moc resources
QMAKE_PRL_VERSION = 1.0.0
QMAKE_PRL_LIBS = -L/usr/lib64 
-L/home/abuild/rpmbuild/BUILD/qtmultimedia-opensource-src-5.9.1/lib 
-lQt5MultimediaWidgets -lQt5Multimedia -lQt5Widgets -lQt5Gui -lQt5Network 
-lQt5Core -lGL -lpthread -lasound -lgstaudio-1.0 -lgstvideo-1.0 
-lgstpbutils-1.0 -lgstapp-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 
-lpulse-mainloop-glib -lpulse -lglib-2.0

Why does my Qt build use the system installed /usr/lib64/libqgsttools_p.prl 
file and not the one from the build dir
/home/PACKAGES/qt/5.9.1/qt-everywhere-opensource-src-5.9.1/qtmultimedia/lib/libqgsttools_p.prl
which contains
QMAKE_PRL_BUILD_DIR = 
/home/PACKAGES/qt/5.9.1/qt-everywhere-opensource-src-5.9.1/qtmultimedia/src/gsttools
QMAKE_PRO_INPUT = gsttools.pro
QMAKE_PRL_TARGET = libqgsttools_p.so.1.0.0
QMAKE_PRL_CONFIG = lex yacc debug depend_includepath testcase_targets 
import_plugins import_qpa_plugin qt_build_extra file_copies qmake_use qt 
warn_on link_prl incremental shared debug linux unix posix gcc sse2 sse3 ssse3 
sse4_1 sse4_2 avx avx2 compile_examples enable_new_dtags f16c largefile 
optimize_debug precompile_header prefix_build force_independent utf8_source 
create_prl link_prl prepare_docs qt_docs_targets no_private_qt_headers_warning 
QTDIR_build qt_example_installs exceptions_off testcase_exceptions explicitlib 
have_target dll debug_info c++11 thread uic opengl moc resources
QMAKE_PRL_VERSION = 1.0.0
QMAKE_PRL_LIBS = 
-L/home/PACKAGES/qt/5.9.1/qt-everywhere-opensource-src-5.9.1/qtmultimedia/lib 
-lQt5MultimediaWidgetsWinCC_OA 
-L/home/PACKAGES/qt/5.9.1/qt-everywhere-opensource-src-5.9.1/qtbase/lib 
-lQt5MultimediaWinCC_OA -lQt5WidgetsWinCC_OA -lQt5GuiWinCC_OA 
-lQt5NetworkWinCC_OA -lQt5CoreWinCC_OA -lGL -lpthread -lasound -lgstaudio-1.0 
-lgstvideo-1.0 -lgstpbutils-1.0 -lgstapp-1.0 -lgstbase-1.0 -lgstreamer-1.0 
-lgobject-2.0 -lpulse-mainloop-glib -lpulse -lglib-2.0

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\- against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Martin Koller
On Montag, 24. Juli 2017 08:32:23 CEST Thiago Macieira wrote:
> On Sunday, 23 July 2017 22:58:02 PDT Martin Koller wrote:
> > So the bug in fact is that qt does not give a correct name for
> > libQt5MultimediaGstTools.prl ?
> 
> I don't know if that's a bug. I've never felt a problem with the .prl being 
> named like that.
> 
> > In fact it does use the infix for the other libs here (5.9.1), e.g. I find
> > ./qtmultimedia/lib/libQt5MultimediaWidgetsWinCC_OA.prl
> 
> How about qgsttools_p ?
> 

I have the following files under qtmultimedia

./lib/libQt5MultimediaWidgetsWinCC_OA.prl
./lib/libqgsttools_p.prl
./lib/libQt5MultimediaWinCC_OA.prl

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\- against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Oswald Buddenhagen
On Mon, Jul 24, 2017 at 07:58:30AM +0200, Kevin Kofler wrote:
> Thiago Macieira wrote:
> > No, this is the solution, unless you want to build in a chroot'ed build
> > root. In the environment where you're going to build a given software, you
> > must not have the development packages of that software already installed.
> 
> That is utter nonsense.
>
yes, it's one of thiago's pet peeves. ;)

> Any package that picks up headers or library symlinks from the old
> installed version instead of from the one you are currently building
> is buggy.
> 
https://bugreports.qt.io/browse/QTBUG-50921
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Thiago Macieira
On Sunday, 23 July 2017 23:03:04 PDT Kevin Kofler wrote:
> Thiago Macieira wrote:
> > This is the root of your problem. Something that this plugin or
> > qgsttools_p needs to link to said that its libraries are in /usr/lib64.
> > qmake has some code to remove system paths, but it that won't work if the
> > 
> > path being requested is both:
> >  a) not system
> >  b) where Qt libraries are
> 
> /usr/lib64 is most definitely a system path. This is where 64-bit libraries
> belong to according to the FHS.

Agreed. You have a double (or even triple) failure causing your problem.

qmake should have removed /usr/lib64 but didn't. That means the configure 
detection of what the system linker paths are failed. See any of the 
.qmake.stash files to see what it did detect, if anything.

Then there's the second issue that something did add /usr/lib64. It shouldn't 
have. But it might be from a .prl file, which is much stupider than pkg-config.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Thiago Macieira
On Sunday, 23 July 2017 22:58:02 PDT Martin Koller wrote:
> So the bug in fact is that qt does not give a correct name for
> libQt5MultimediaGstTools.prl ?

I don't know if that's a bug. I've never felt a problem with the .prl being 
named like that.

> In fact it does use the infix for the other libs here (5.9.1), e.g. I find
> ./qtmultimedia/lib/libQt5MultimediaWidgetsWinCC_OA.prl

How about qgsttools_p ?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Thiago Macieira
On Sunday, 23 July 2017 22:58:30 PDT Kevin Kofler wrote:
> Thiago Macieira wrote:
> > No, this is the solution, unless you want to build in a chroot'ed build
> > root. In the environment where you're going to build a given software, you
> > must not have the development packages of that software already installed.
> 
> That is utter nonsense. Any package that picks up headers or library
> symlinks from the old installed version instead of from the one you are
> currently building is buggy.

You're thinking only of a 1-software problem. This is complex when you have 
more than one. Take this as an example: you want to build software for your 
professional project but not pollute your system, so you build Qt and 
GStreamer 1.0 but tell it to install in /opt/myproject.

That means /opt/myproject/lib/pkgconfig/gstreamer-1.0.pc file has:
prefix=/opt/myproject
exec_prefix=/opt/myproject
libdir=/opt/myproject/lib

So when Qt asks pkg-config for the path to the GStreamer library, it will 
print:
-L/opt/myproject/lib -lgstreamer-1.0

That -L switch will make the linker find Qt libraries too.


Before you say, "well, list Qt libraries first", let me add another 
complication: the plugin has this in the linker line:

-lQt5MultimediaGstTools.t -lQt5MultimediaWidgets.t -lQt5Multimedia.t 
-lQt5Widgets.t -lQt5Gui.t -lQt5Network.t -lQt5Core.t

but if you ldd it after compiling, you find it loaded one more library 
(Qt5OpenGL) because of an indirect dependency. So even if qmake listed the 
Qt's own -L and its libraries first (and it does), we may still have a problem 
due to the indirect dependency and how it's found by the linker.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Kevin Kofler
Martin Koller wrote:
> So the bug in fact is that qt does not give a correct name for
> libQt5MultimediaGstTools.prl ?

The bug is that something tries to use -L/usr/lib64. That directory is in 
the default linker search path, it makes no sense to -L it, and doing it 
anyway messes up the search order.

Kevin Kofler

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-24 Thread Kevin Kofler
Thiago Macieira wrote:
> This is the root of your problem. Something that this plugin or
> qgsttools_p needs to link to said that its libraries are in /usr/lib64.
> qmake has some code to remove system paths, but it that won't work if the
> path being requested is both:
>  a) not system
>  b) where Qt libraries are

/usr/lib64 is most definitely a system path. This is where 64-bit libraries 
belong to according to the FHS.

Kevin Kofler

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-23 Thread Kevin Kofler
Thiago Macieira wrote:
> No, this is the solution, unless you want to build in a chroot'ed build
> root. In the environment where you're going to build a given software, you
> must not have the development packages of that software already installed.

That is utter nonsense. Any package that picks up headers or library 
symlinks from the old installed version instead of from the one you are 
currently building is buggy.

Kevin Kofler

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-23 Thread Martin Koller
On Sonntag, 23. Juli 2017 23:40:30 CEST Thiago Macieira wrote:

> > -) -lQt5MultimediaWidgets and others: why are they used here instead of the
> > namespaced/infixed versions, which are also given> 
> >but later in the line ?
> 
> Same reason: the system-wide qgsttools_p.prl file was found.
> 
> Even with the turning of qgsttools_p into a real Qt module (albeit internal) 
> in commit ab6ebd360eb27a0d502839fca07ae0e6e107cec6, the infix won't help you 
> because the infix is not stored in the .prl file. Look at my case:
> 
> $ find `qmake -query QT_INSTALL_LIBS` -name \*Qt5MultimediaGstTools\*
> /home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so.5.10
> /home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so
> /home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so.5
> /home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.prl
> /home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.la
> /home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so.5.10.0
> 
> The .prl and .la files don't have the ".t" infix.

So the bug in fact is that qt does not give a correct name for 
libQt5MultimediaGstTools.prl ?

In fact it does use the infix for the other libs here (5.9.1), e.g. I find 
./qtmultimedia/lib/libQt5MultimediaWidgetsWinCC_OA.prl


-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\- against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-23 Thread Thiago Macieira
On Sunday, 23 July 2017 01:50:10 PDT Martin Koller wrote:
> -) why is -L/usr/lib64 there (should be a std. path, no?)

This is the root of your problem. Something that this plugin or qgsttools_p 
needs to link to said that its libraries are in /usr/lib64. qmake has some 
code to remove system paths, but it that won't work if the path being 
requested is both:
 a) not system
 b) where Qt libraries are

Hence: uninstall the development packages.

> -) From where the heck comes this path
> "/home/abuild/rpmbuild/BUILD/qtmultimedia-opensource-src-5.9.1/lib" ?
>I don't have a /home/abuild directory on my system.
>This is the ONLY Makefile in the whole Qt tree which contains this path

The "rpmbuild" part indicates that it comes from an RPM build. So most likely 
this is because qmake found the qgsttools_p.prl file in /usr/lib64 and that 
file 
has bogus information.

You may get away with this problem by just removing that file, as nothing 
outside of qtmultimedia itself should be linking against qgsttools_p.

> -) -lQt5MultimediaWidgets and others: why are they used here instead of the
> namespaced/infixed versions, which are also given> 
>but later in the line ?

Same reason: the system-wide qgsttools_p.prl file was found.

Even with the turning of qgsttools_p into a real Qt module (albeit internal) 
in commit ab6ebd360eb27a0d502839fca07ae0e6e107cec6, the infix won't help you 
because the infix is not stored in the .prl file. Look at my case:

$ find `qmake -query QT_INSTALL_LIBS` -name \*Qt5MultimediaGstTools\*
/home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so.5.10
/home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so
/home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so.5
/home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.prl
/home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.la
/home/tjmaciei/obj/qt/qt5/qtbase/lib/libQt5MultimediaGstTools.t.so.5.10.0

The .prl and .la files don't have the ".t" infix.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-23 Thread Thiago Macieira
On Sunday, 23 July 2017 14:22:03 PDT Thiago Macieira wrote:
> > (I need Qt devel system files when compiling KDE, but I need to build my
> > own Qt for company project)
> 
> You must install and uninstall the development packages as needed then. Or
> set up a build root for building one or the other software. Or for both.

There's another trick I use to make completely separate self-built Qt for 
development from the system Qt that KDE & Plasma use: I use a lib infix. That's 
the -qtlibinfix parameter to configure.

It probably went unnoticed in several pastes I made, but it's sometimes there:

   textdata bss dec hex filename
 250649   10192 164  261005   3fb8d libQt5MultimediaGstTools.t.so.5.10.0

See that ".t" between the library name and the ".so"?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-23 Thread Thiago Macieira
On Sunday, 23 July 2017 13:49:11 PDT Martin Koller wrote:
> On Sonntag, 23. Juli 2017 18:54:41 CEST Thiago Macieira wrote:
> > On Sunday, 23 July 2017 01:50:10 PDT Martin Koller wrote:
> > > I found this symbol to be in the qgsttools_p lib but I fear the linker
> > > takes the lib from a wrong path.
> > 
> > If you already have Qt installed system-wide, please remove the
> > development
> > files. You said you're on OpenSUSE, so just remove the Qt -devel packages.
> 
> Ouch.
> I assume this is just a workaround, and not "the solution", right ?

No, this is the solution, unless you want to build in a chroot'ed build root. 
In the environment where you're going to build a given software, you must not 
have the development packages of that software already installed.

That's also why I highly recommend against using any Linux distribution that 
lacks the concept of development package.

> (I need Qt devel system files when compiling KDE, but I need to build my own
> Qt for company project)

You must install and uninstall the development packages as needed then. Or set 
up a build root for building one or the other software. Or for both.

> I can compile/link all parts of Qt, just the gstreamer plugins are a
> problem. Can this be solved in a clean way ?

You probably have either -L/usr/lib or -L/usr/lib64 added to your linker line. 
Find the source of that option (probably a pkg-config file for GStreamer) and 
fix 
there.

If the issue is not a system path, then you've got the corner I mentioned. 
Unsolvable short of removing files.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-23 Thread Martin Koller
On Sonntag, 23. Juli 2017 18:54:41 CEST Thiago Macieira wrote:
> On Sunday, 23 July 2017 01:50:10 PDT Martin Koller wrote:
> > I found this symbol to be in the qgsttools_p lib but I fear the linker takes
> > the lib from a wrong path.
> 
> If you already have Qt installed system-wide, please remove the development 
> files. You said you're on OpenSUSE, so just remove the Qt -devel packages.

Ouch.
I assume this is just a workaround, and not "the solution", right ?

(I need Qt devel system files when compiling KDE, but I need to build my own
Qt for company project)

I can compile/link all parts of Qt, just the gstreamer plugins are a problem.
Can this be solved in a clean way ?

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\- against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] can not build 5.9.1 qtmultimedia

2017-07-23 Thread Thiago Macieira
On Sunday, 23 July 2017 01:50:10 PDT Martin Koller wrote:
> I found this symbol to be in the qgsttools_p lib but I fear the linker takes
> the lib from a wrong path.

If you already have Qt installed system-wide, please remove the development 
files. You said you're on OpenSUSE, so just remove the Qt -devel packages.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development