=== nudtrobert1 is now known as nudtrobert === nudtrobert1 is now known as nudtrobert [16:17] following the 'Building Unity 8' instructions, cmake fails at "find_package(Qt5Core 5.2 REQUIRED)", though libqt5core5a is installed. it's the exact same error that's described here: https://askubuntu.com/questions/625471/installing-dependencies-for-building-unity-8 [16:17] any ideas? [16:55] ennui: not sure exactly what you need, but 'libqt5core5a' doesn't contain header files, which I assume cmake is looking for... [17:06] you probably need 'qtbase5-dev' & such [17:08] apt-cache showsrc unity8 | grep Build-Depends [17:09] or to install those dependencies, use: sudo apt-get build-dep unity8 [17:12] (didn't try that, but it's what I would try :) ) [17:15] JanC: thanks! 'sudo apt-get build-dep unity8' fixed the qt5core error, but I'm getting a bunch of other 'not found' errors. could you have a quick glance? [17:15] http://pastie.org/pastes/10401467#14 [17:17] (I'm working with a fresh, up-to-date vivid install and precisely followed all steps in the build guide.) [17:21] to be clear: I've never built unity8, that was just general development info on Debian-based distros [17:23] I assume you are trying to build a current source version of unity8, which might have extra build-dependencies compared to the version in vivid [17:23] or newer versions of build-dependencies [17:24] maybe somebody else can help you with that [17:24] yes, I checked out the current trunk (as suggested). so there's no automatic way to figure out the build dependencies? [17:25] the main developers are more likely to be around during European (or maybe US) business hours on work days [17:26] JanC: okay, I'll ask again tomorrow, then. thank you! [17:26] ennui: the wily source package would probably have more up-to-date build-dependencies [17:27] ennui: see e.g. http://packages.ubuntu.com/source/wily/unity8 [17:27] JanC: ah, perfect, thanks! [17:29] remember that it might not be possible to build a trunk version of unity8 on vivid without replacing a number of libraries with newer versions etc., which might break existing applications... [17:31] well, build deps won't break vivid, but libraries needed to run could break other apps [17:32] one way around this would be to create a wily chroot and work inside that [20:38] JanC: the unity build worked fine on wily. i'll file a bug about the outdated instructions. === g4mby is now known as PaulW2U