After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 682500 - in-source compilation fails due to gen.cpp
in-source compilation fails due to gen.cpp
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: qt-gstreamer
git master
Other Linux
: Normal minor
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-08-22 19:45 UTC by Greg Miller
Modified: 2016-01-08 20:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Greg Miller 2012-08-22 19:45:45 UTC
This error has persisted for months perhaps because nobody else is trying to compile from fresh clone of git repository?

make clean

make 

Scanning dependencies of target QtGLib_automoc
[  1%] Automoc for target QtGLib
Generating connect.moc
[  1%] Built target QtGLib_automoc
make[2]: Circular src/QGlib/gen.cpp <- src/QGlib/gen.cpp dependency dropped.
[  2%] Copying gen.cpp to the build directory
Error copying file "/srv/git/gstreamer-qt/src/QGlib/gen.cpp" to "/srv/git/gstreamer-qt/src/QGlib/gen.cpp".
make[2]: *** [src/QGlib/gen.cpp] Error 1
make[1]: *** [src/QGlib/CMakeFiles/QtGLib.dir/all] Error 2
make: *** [all] Error 2
Comment 1 George Kiagiadakis 2012-08-22 21:49:24 UTC
It looks as if you are trying to compile in the same directory as the source code (i.e. in-source build). Theoretically this should be supported, but I never actually thought of it (or tried it) because common cmake practice is to build out-of-source in a separate build directory. So, try following the build instructions from the README and it should work.

This is a bug that should be fixed of course, so I will leave the bug open, but I consider it minor.
Comment 2 Tim-Philipp Müller 2016-01-08 20:02:05 UTC
Let's close this if no one's going to work on fixing this, it is not in accordance with common practice after all, which is separte builddir.