[10:07] <maxvanceffer> Hi to all ! Can some body help me, in what paths my app can write data ?
[10:08] <maxvanceffer> Because i am trying right now to write some cache inside my app folder, but app armor denied
[18:12] <aquarius> OK, now confused. I'm on 14.04, attempting to build a C++ app in Qt Creator using my 14.10 arm chroot. If I re-run cmake in Qt Creator (right-click project name in left sidebar, say "Run CMake"), it throws the error "g++ version must be at least 4.9!". Now, the gcc in my 14.04 machine is indeed 4.8.4, but in the chroot it is not; it is 4.9.1.
[18:13] <aquarius> so this should work, right? But... no. So... help?
[18:14] <aquarius> also, appdevs ^ :)
[18:28] <popey> and it's definitely using the kit and not building on your desktop?
[18:28] <aquarius> I don't know how to know that :(
[18:29] <aquarius> certainly I haven't changed anything about the build code, and it has built in the past -- it's an armhf chroot which builds for the phone, so if it were entirely using my desktop's stuff, it'd fail when installed tothe phone 'cos the desktop is amd64
[18:29] <aquarius> and the build output says:
[18:29] <aquarius> Command returned 1: schroot -c 'click-ubuntu-sdk-14.10-armhf-ucca-1000-{807325e9-3c48-498f-825b-80767f03ac79}' --run-session -- env DEB_BUILD_ARCH=amd64 DEB_BUILD_ARCH_BITS=64 DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_BUILD_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_GNU_CPU
[18:29] <aquarius> =arm DEB_HOST_ARCH_OS=linux DEB_HOST_ARCH=armhf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_HOST_ARCH_CPU=arm DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH_BITS=32 DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux cmake /home/aquarius/Programs/Others/addtodash '-GCodeBlocks - Unix Makefiles'
[18:29] <popey> click projects on the left
[18:30] <popey> why are you building in a 14.10 chroot?
[18:30] <aquarius> which certainly looks like it's building on the phone.
[18:30] <popey> you should be on a 15.04 chroot
[18:30] <popey> IMO
[18:30] <aquarius> (and only the "Bq E4.5 Ubuntu (GCC armhf)" kit is being used.
[18:31] <aquarius> Mainly because I haven't set up a 15.04 chroot yet, because the 14.10 one works fine.
[18:31] <popey> i would
[18:31] <popey> i recently updated my 15.04 because it build broken binaries
[18:31] <popey> I even added the stable ppa to my chroot
[18:31] <popey> and now it builds things that work :S
[18:31] <aquarius> mine builds things that work -- it did a week ago, anyway :)
[18:31] <aquarius> agreed that I should at some point set up a new one
[18:32] <aquarius> but the whole area of kits and chroots is terribly confusing and I am loath to abandon a working thing :)
[18:33] <popey> pfff
[18:33] <popey> just do this:-
[18:33] <popey> click chroot -a armhf -f ubuntu-sdk-15.04 create
[18:33] <popey> with sudo
[18:33] <popey> and leave it running
[18:34] <aquarius> currently reading up on how to create a new kit.
[18:34] <aquarius> (I know the command line works, but I don't wanna do it that way.)
[18:34] <popey> i only interact with the sdk via the command line
[18:35] <popey> I don't use qtc at all anymore
[18:35] <aquarius> i am the exact opposite :)
[18:35] <popey> :)
[18:35] <popey> all bases covered
[18:36] <aquarius> "Managing targets and kits" under https://developer.ubuntu.com/en/apps/sdk/tutorials/click-targets-and-device-kits/ seems to be the way
[18:36] <aquarius> now to wait a hundred years while I download a whole debian archive again ;)
[18:39] <aquarius> let's see if this fixes things, at least.
[19:24] <aquarius> popey, that does seem to have fixed the previous issue, indeed, now that I'm building in a 15.04 chroot. So, I get dragged kicking and screaming into the modern day, again :)
[19:34] <popey> :)
[19:34] <popey> well, also, 14.10 isn't even supported anymore
[19:37] <aquarius> apps built with it should still work, though
[19:38] <aquarius> that's what version numbering of the components is for. :)