/srv/irclogs.ubuntu.com/2015/01/03/#ubuntu-touch.txt

aquariusnot much documentation about .qmlproject files -- like, for example, does QtC only read projectname.qmlproject? Or can I create a second one and that gets read too? That'd be quite elegant.00:00
dobeyif you have multiple qmlproject files, they would be treated as separate projects00:03
dobeyie, when you go to "open project" in qtc, you choose the .qmlproject file00:03
dobeyi'm /still/ not quite sure what you're trying to do. if this is for the ucs thing, then the thing to do to make it work properly in both places, is to have your tool add stuff to the .qmlproject's importPaths, and ensure that the components get propertly isntalled into the respective lib/$arch directories, when the click gets built00:05
aquariusyep00:05
aquariusI agree.00:05
dobeyor better, have your tool pull them into a lib/ structure, so you don't have to add all the separate import paths for each component and keep it updated (having arch-dependent paths in qmlproject file is not a great idea)00:06
aquariusthat's the plan, roughly, yep00:07
aquariusI don't want to add arch-dependent paths to .qmlproject either, but I'm not sure it's avoidable.00:07
aquariushuh00:08
aquariusit already *has* arch-dependent paths in it.00:08
aquarius    importPaths: [ "." ,"/usr/bin","/usr/lib/x86_64-linux-gnu/qt5/qml" ]00:09
aquariusso I can't really go wrong with adding "./lib/x86_64-linux-gnu" to the end of that.00:09
aquariusanybody who commits .qmlproject to source control and then checks it out on a different machine with a different arch is *already* screwed.00:09
dobeyoi00:10
dobeywtf is /usr/bin in there00:10
dobeyoh well00:11
dobeyi should probably go eat and look wantingly at more car parts or something00:11
aquariusright, that solves the problem for pure qml stuff, anyway00:11
aquariusI need to actually implement it :)00:11
aquariusnext step: work out how to do this same thing for cmake and qmake based projects.00:11
aquariusand then I'm good.00:11
aquariuscheers, pal; that was helpful00:12
dobeyadd cmake/UbuntuCompoinentStore.cmake00:12
dobey:)00:12
aquariusI believe that's exactly the plan, but I'm not good with makefile stuff, so I shall look at that tomorrow :)00:13
jmgallo55hello everyone04:25
jmgallo55can anyone point me to a place for new developers using Ubuntu SDK?04:27
aquariusElleo, ping about making an extension plugin :)09:58
Elleoaquarius: pong :)10:10
aquariusElleo, do you have a clear idea in your head of how to build a QML Extension Plugin (http://doc.qt.io/qt-5/qtqml-tutorials-extending-qml-example.html#chapter-6-writing-an-extension-plugin) for all three architectures (arm, amd64, x86)?10:11
aquariusand if so, do you fancy spending a little time building a tiny one and setting it up as a downloadable component to my instructions that I can experiment with? :)10:12
Elleoaquarius: sure10:15
aquariusElleo, cool. Invent a component of your choice; what it is is up to you :)10:16
Elleoaquarius: although, you can actually get something straight from the SDK to play with if you create a new app and choose "simple ui with c++ extension" iirc10:16
aquariuswell.10:16
Elleoalthough it won't *just* be an extension10:16
aquariusI have done precisely that10:16
aquariusand I have a .so file which can run external commands10:16
aquariusand it can be included10:16
aquariusbut I don't think it's just an extension10:17
aquariusand I think we should make binary component be extension plugins10:17
Elleoaquarius: the .so file will be just an extension (if it's based on the sdk template)10:17
aquariusoh, really?10:17
Elleoaquarius: but that template also includes an app and ui stuff that make use of the extension10:17
Elleowhich is what I meant by it not being just an extension10:18
aquariusthat's OK -- I can just pull the .so file out10:18
Elleoyeah10:18
aquariuswhich is what I've done, for testing10:18
aquariusbut I agree with you that we ought to have a template which builds these things correctly10:18
aquariusand puts the compiled files in the correct place for the component store to recognise them10:18
aquariusI've decided on that stuff not10:18
aquariusnow10:18
aquariusI think :)10:18
Elleoyeah10:18
ElleoI'm not especially familiar with qt creator's template stuff, but I don't mind helping to figure things out if needed10:19
aquariusI also know what to do to a pure qml project to make it import such a component from a lib/$arch location, hooray10:19
aquariusI do *not* know what to do for cmake or qmake projects to make them do the same10:19
aquariusif you do know, that'd be handy info :P10:19
Elleoafraid not10:20
ElleoI'd assumed it was all done automatically by some part of the runtime system10:20
aquariusI may have a bunch of questions for you about that in a bit, then :P10:20
Elleorather than being related to the build system10:20
Elleoperhaps its setting an rpath on the binary?10:20
Elleoalthough it wouldn't be able to do that for pure qml stuff10:21
aquariusnope10:21
Elleoaha10:21
aquariusto make an extension plugin available to an app, you put it on the QML2_IMPORT_PATH10:21
Elleojust glanced at the cmake stuff for one of my projects10:22
aquariusthis happens differently in Qt Creator and in actual deployedness on the phone10:22
Elleoand it has set(QT_IMPORTS_DIR "lib/${ARCH_TRIPLET}")10:22
aquariuson the phone, the apparmor wrapper sets QML2_IMPORT_PATH to include lib/$arch10:22
aquariusin QtC, for pure QML projects, projectname.qmlproject has importPaths set in it.10:23
aquariusI don't know how it's done for cmake or qmake projects in Qt Creator, though. In particular, QT_IMPORTS_DIR is for compiling, isn't it? Not for runtime inclusion of QML imports.10:23
aquariusalthough I may be wrong about that.10:24
aquariusif it's *already* the case, that's great :)10:24
Elleonot certain how that's used yet, just poking around a bit at the minute10:25
Elleoyeah, I'm not sure what's going on; I suspect prodding the SDK folks would produce better results though ;)10:34
Elleothat QT_IMPORTS_DIR setting is the only thing I can find in the cmake setup that seems in anyway relevant10:40
Elleocan't find anything much in the way of docs for it though10:41
ElleoI suspect it might just end up being used to determine where to install plugins10:42
Elleoaquarius: have to head out for a bit now, but will be around again this evening10:47
aquariusElleo, cheers :)11:03
TakagamiG'morning all...13:10
Makalakpopey when is the new porting guide going up?15:26
aquariusElleo, nik90_, aha, I can now install binary components in pure QML apps, and install QML components too. Hooray! End-to-end working tests :-)15:41
nik90_aquarius: wo that's fast!15:57
aquariusnik90_, not really, man; the original proposal was last February :)15:58
nik90_aquarius: well what you had in last feb was proposal + demo...now its working prototype work in the past few days15:58
aquariusnik90_, I'm pushing this stuff to a new branch in the component-store project; at some point when you have time, I'd like to bring you up to date on what I'm doing so you know and can give me thoughts15:58
nik90_sure15:59
aquariuswhen's good for you?15:59
nik90_aquarius: tonight, I will be out...does tomorrow sound good?15:59
aquariusit does. I have set aside this weekend to work on this stuff :)15:59
nik90_cool15:59
nik90_tomorrow I should be free for the whole day pretty much15:59
nik90_just ping me when you want to talk16:00
aquariusStill remaining to do are: correctly handle adding community components to qmake and cmake projects; handle adding curated components to projects (should be easy); document the whole world; deploy the server :)16:00
aquariusbut I can, right now this second, create a new QML app with Ubuntu SDK, type "ucs install sil/GetHomeDir", and then add "import ubuntu_component_store.sil.GetHomeDir 1.0" to my QML file and get a new Launcher {} item which returns my home directory, which pure QML apps can't do.16:02
aquariushooray!16:02
aquariusI think hooray, anyway :)16:02
nik90_sweet16:03
aquariusnik90_, am I right in thinking that curated components will only be pure QML?17:27
aquariusnik90_, on the assumption that that's true, one can now ucs install curated components. :)17:38
nik90_aquarius: yeah for now curated components will be pure QML since we don't have much people to review c++ components.18:08
stu_Is r58 the latest versino of  Ubuntu 15.04? I do not seem to get any updates after that, but that release is 16 days old...18:21
stu_Seems to be the latest entry in the cahnge log as well...18:22
gcollurastu_, I think the development is on hold due to christmas holidays :)18:50
stu_Ok, they certainly deserve some holidays -- I was mostly curious as to whether something changed (maybe need to update from where to update).  But looking around a bit more it is probably normal not to get any updates now.18:54
ogra_stu_, https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/ ... after the SDK team messed around with oxide the images are unbuildable since a few weeks now19:35
Makalakogra_: these are the main images right, system.img?19:51
ogra_Makalak, this is the rootfs20:38
julienrbthttps://twitter.com/imslavko/status/551477294137483266 lol :D20:50
julienrbtops20:50
julienrbtsry20:50
nhainesha!20:58
Elleoaquarius: awesome :)22:32

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!