**** BEGIN LOGGING AT Wed Sep 04 02:59:58 2013
Sep 04 12:40:46 <Crofton|work> cfo215, what is the ubuntu version that gave you trouble?
Sep 04 12:45:08 <cfo215> 12.04.2 LTS
Sep 04 12:48:07 <Crofton|work> thanks
Sep 04 12:48:26 <Crofton|work> bluelightning, ^^^ do we know anyone testing on that version?
Sep 04 12:49:07 <Crofton|work> and running gcc from populate_sdk had a ldvdso issue?
Sep 04 12:49:57 <bluelightning> Crofton|work: that is in the list of YP supported distributions, so we do QA with it
Sep 04 12:50:15 <bluelightning> Crofton|work: however, last I heard this was an angstrom-specific problem
Sep 04 12:50:20 <Crofton|work> and that includes making sure sdk's work?
Sep 04 12:50:33 <bluelightning> Crofton|work: we may not have a test case for the Qt tools within the SDK either
Sep 04 12:50:56 <bluelightning> Crofton|work: we do test the plain SDKs, AFAIK
Sep 04 12:51:07 <Crofton|work> I'm having a hard time seeing how this could be Angstrom specific
Sep 04 12:51:30 <Crofton|work> and would like to make sure the problem doesn't creep into somethign we release
Sep 04 12:51:33 <bluelightning> on the face of it I would have to agree, but that's what cfo215 was reporting
Sep 04 12:51:42 <Crofton|work> I know
Sep 04 12:54:32 <cfo215> bluelightning, Crofton|work: I'm sorry I had to blow away the Ubuntu 12.04.2 I was using.  As time permits, I could install it in a virtual box and see if the problem is reproduceable there.
Sep 04 12:54:50 <Crofton|work> no worries, I'd rather you be successful
Sep 04 13:06:06 <cfo215> bluelightning, Crofton|work:  thanks for all your help.  And a to anyone else I might have forgotten.
Sep 04 13:29:17 <cfo215> bluelightning, Crofton|work: keep you fingers crossed... now building with my layer included....
Sep 04 13:29:52 <cfo215> which shouldn't effect the development tools at all.
Sep 04 13:52:00 <cfo215> Crofton|work, when you do a populate_sdk, does it also build tools for the host system.  .i.e.  I'm developing in Qt for the target.  I'd like to also run at least the gui part locally (x86_64) while developing it.
Sep 04 13:57:31 <Crofton|work> I'm not sure I follow?
Sep 04 14:36:10 <cfo215> Crofton|work, Qt is multi-platform.  Does populate_sdk build an sdk for X86_64 machine (host) at the same time it builds sdk for the target (ARM).  So I can choose which libraries to link my source to X86_64 or ARM.
Sep 04 14:36:45 <Crofton|work> you'd have to ask someone smart
Sep 04 14:37:00 <Crofton|work> sounds like you need a couple of sdks
Sep 04 14:37:04 <cfo215> Crofton, LOL.  No problem.  I think I just answered my own question.
Sep 04 14:37:09 <Crofton|work> but can't you use the stuff on the build machine?
Sep 04 14:37:40 <Crofton|work> I sort of see what you are thinking I think
Sep 04 14:37:43 <cfo215> Crofton, that's right.  I'm just afraid to install dev-tools on my system so I don't break anything... I'm sure it will be fine...
Sep 04 14:38:39 <Crofton|work> be careful :)
Sep 04 14:39:21 <cfo215> Crofton|work, maybe I'll build a virtual machine to put my dev-tools into...  that's probably safer.
Sep 04 14:40:09 <bluelightning> cfo215: it wouldn't be too hard - that's the "host" part of the SDK, so if you can build a "nativesdk" version of all the tools you need and ensure that gets into the host part of the SDK (i.e. add it to TOOLCHAIN_HOST_TASK) then that is possible
Sep 04 14:40:12 <Crofton|work> I suppose I should try OE in a vm again one day
Sep 04 14:40:29 <bluelightning> no need for multiple SDKs
Sep 04 14:40:37 <bluelightning> (for this at least)
Sep 04 14:42:57 <cfo215> I still need the GUI for Qt for my development.  It seems I have some development tools, though I didn't install them(?).  I have gcc (GCC) 4.8.1 20130603 (Red Hat 4.8.1-1) installed.
Sep 04 14:43:28 <cfo215> bluelightning, I'm not at all familiar with Fedora so I don't know what got installed by default.
Sep 04 14:44:12 <cfo215> bluelightning, I'm thinking i should be able to compile Qt 4.8.4 from the tarball in the sources directory.
Sep 04 14:44:45 <cfo215> or whatever version it concocted.  I pulled that out of my a...
Sep 04 14:45:23 <cfo215> that way I have the "same" Qt on my host as on the target.
Sep 04 14:45:52 <bluelightning> cfo215: well, you shouldn't have to compile it by hand, you'd just add the Qt tools to the SDK as I described above
Sep 04 14:46:51 <cfo215> bluelightning, thanks... I just now read that.  I'll rtfm to see how to implement the TOOLCHAIN_HOST_TASK.
Sep 04 14:49:06 <bluelightning> cfo215: I don't think it's in the current version of the fm to be honest ;)
Sep 04 14:49:20 <bluelightning> cfo215: you can see examples of its usage with "git grep TOOLCHAIN_HOST_TASK" though
Sep 04 14:49:33 <bluelightning> e.g. meta/recipes-qt/meta/meta-toolchain-qt.inc
Sep 04 14:49:47 <cfo215> bluelightning, Of course not... :0
Sep 04 14:50:08 <bluelightning> it's in the very latest version of the manual though, I ensured it got added
Sep 04 14:50:27 <cfo215> bluelightning, I'll look at that.
Sep 04 14:50:38 <cfo215> bluelightning, thanks.  I'll see if I can find the current version.
Sep 04 14:50:45 <bluelightning> to be honest I don't know that it says a lot other than what I mentioned above
Sep 04 14:51:31 <cfo215> bluelightning, I just love that about the OE/Yocto Docs.  The assume you know more than you possibly can just starting with it.
Sep 04 14:52:08 <bluelightning> cfo215: we are continuously improving the documentation, FWIW
Sep 04 14:52:27 <cfo215> bluelightning, I'm a firm believer that all documentation should be written to about a 9th grade level and assume very little knowledge on the part of the reader.
Sep 04 14:52:45 <bluelightning> in the next dev cycle there is a plan to add more task-oriented sections (we've steadily been adding those already)
Sep 04 14:53:29 <cfo215> bluelightning, trust me I know about documentation.  They don't really pay us now to document... just to build.
Sep 04 14:53:35 <bluelightning> we don't consciously write the docs for people with existing knowledge, it just takes time to develop decent task-oriented documentation
Sep 04 14:53:51 <cfo215> bluelightning, agreed.
Sep 04 14:54:41 <bluelightning> if there are pieces missing that you've noticed we'd really appreciate documentation bug reports, there's an appropriate set of categories in the Yocto Project bugzilla
Sep 04 14:55:33 <cfo215> bluelightning, i found this: ./deploy/eglibc/ipk/x86_64-nativesdk/nativesdk-qt4-tools_4.8.4-r13.0.0_x86_64-nativesdk.ipk
Sep 04 14:55:51 <cfo215> bluelightning, is that what you're referring to?
Sep 04 14:56:04 <bluelightning> cfo215: if you're building meta-toolchain-qte you'll already have that in the host part of the SDK
Sep 04 14:56:34 <cfo215> yes, that's what I build.  So i should have composer then somewhere.
Sep 04 14:58:15 <cfo215> bluelightning, thanks, I'll look at it all and see what I have.  got to get to a meeting.
Sep 04 15:41:57 <cfo215> bluelightning, i'll make sure to report any documentation issues to bugzilla.
Sep 04 15:57:06 <bluelightning> cfo215: thanks
Sep 04 16:13:07 <cfo215> bluelightning, is Qt Designer part of the meta-toolchain-qte build?  I can't seem to find it.
Sep 04 16:17:11 <bluelightning> cfo215: so, FWIW, it looks like nativesdk-qt4-tools is built with -embedded
Sep 04 16:17:26 <bluelightning> cfo215: thus the X11-based tools aren't included out of the box
Sep 04 16:20:09 <cfo215> bluelightning, IC, thanks again.  So probably if i built an qemux86 target machine with Qt/X11 on it I'd get those tools in an IPK I could use in Fedora?  Or is that to simple to ask for?
Sep 04 16:20:55 <bluelightning> cfo215: I don't think those would work in the way you'd need
Sep 04 16:21:14 <bluelightning> cfo215: it really has to be nativesdk or just install the Fedora packages for those tools not in the SDK
Sep 04 16:23:32 <cfo215> bluelightning, that sounds like a plan, I was trying to have 4.8.4.  I'm not sure what Fedora's package is on.  I'll look.  Plan 'B' will be compile from the tarball in the sources dir.
Sep 04 16:44:43 <cfo215> bluelightning, so i bitbake nativesdk-qt4-tools_4.8.4 then?  Sorry, I'm still a newb when it comes to this stuff.
Sep 04 16:45:25 <bluelightning> bitbake nativesdk-qt4-tools
Sep 04 16:45:40 <cfo215> bluelightning, thanks again.  I'll do that.
Sep 04 16:46:27 <cfo215> bluelightning, stupid question:  MACHINE= or MACHINE=beaglebone?
Sep 04 16:46:50 <bluelightning> cfo215: MACHINE should be set to whatever your desired target machine is
Sep 04 16:48:06 <cfo215> bluelightning, the target in my case would be my Fedora (X86_64) since I want the tools to run on my PC.  Is that correct?
Sep 04 16:48:29 <bluelightning> cfo215: it's not that simple I'm afraid, as I said earlier
Sep 04 16:49:01 <bluelightning> cfo215: do you mind if I come back to you? I'm trying to migrate the OE layer index atm
Sep 04 16:49:36 <cfo215> bluelightning, no worries.  I'll bitbake it for beagle an see what I get.
Sep 04 16:50:12 <bluelightning> cfo215: FYI, since it's a nativesdk recipe it'll be building to run on SDKMACHINE rather than MACHINE
Sep 04 16:50:37 <bluelightning> and SDKMACHINE defaults to the same as your build machine if not set
Sep 04 16:50:54 <cfo215> bluelightning, which I believe is exactly what I'm after.
Sep 04 16:51:24 <cfo215> and that recipe I presume include the X11 stuff.
Sep 04 16:51:43 <bluelightning> no, that's what I mentioned earlier
Sep 04 16:52:09 <cfo215> bluelightning, Ok, building from source and hoping for the best... thanks again for all your help.
Sep 04 16:52:22 <bluelightning> cfo215: if you have a look at meta/recipes-qt/qt4/nativesdk-qt4-tools.inc you'll see it supplies -embedded in the Qt configure command line, which means it's effectively building Qt/Embedded not Qt for X11
Sep 04 16:52:31 <bluelightning> you may need to modify that
Sep 04 16:52:36 <bluelightning> but even then that might not be enough
Sep 04 16:52:50 <cfo215> bluelightning, I'll have a look.
Sep 04 16:52:53 <bluelightning> FWIW, you're in slightly uncharted territory
Sep 04 16:53:12 <cfo215> bluelightning, as is always the case with me... ;-)
Sep 04 16:55:23 <Crofton|work> being able to demo this use case, especially with ADT for developing a qt app would be perful
Sep 04 17:00:18 <cfo215> Crofton|work, it seems to be a reasonable expectation on my part.  Especially since most people would be deploying Qt GUI apps to their target machines.
Sep 04 17:01:09 <cfo215> Crofton|work, at least thats my case.
Sep 04 17:01:56 <cfo215> Crofton|work, what do you know about nativesdk-libx11?
Sep 04 17:02:05 <Crofton|work> nothing :)
Sep 04 17:02:17 <cfo215> dang nabb it
Sep 04 17:03:10 <cfo215> Oh well, going to go compile that Qt 4 from the source.... God willing it won't hose my angstrom development environment.
Sep 04 17:04:36 <Crofton|work> it shoudln't
Sep 04 17:05:06 <cfo215> compiling... that should get done in about an hour.... 
Sep 04 17:09:50 <cfo215> Crofton|work, here's another thought I had... adding a recipe to create shell scripts for copying the system images to an SD card.  that way people (like me... ) don't have to lookup the process each time they do it.
Sep 04 17:10:21 <Crofton|work> there is an sd card class around
Sep 04 17:10:31 <Crofton|work> the headache is they tend to need root
Sep 04 17:12:31 <cfo215> I wouldn't think you would need root to have bitbake put a text file in the images folder.  which is all a shell script is afterall.  leave it up to the end-user to chmod and execute it.
Sep 04 17:13:05 <cfo215> just have it there for convenience is all I'm saying.
Sep 04 17:14:15 <cfo215> I only bring it up because I see someone else already doing it... http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=85:yocto-gumstix&catid=35:gumstix&Itemid=67
Sep 04 17:16:21 <Crofton|work> more of a bsp thing
Sep 04 17:16:36 <Crofton|work> although I see they are sharing scripts across a couple of vendors hw
Sep 04 17:18:36 <cfo215> I think the SD card getting pretty universal for the small boards.
Sep 04 17:20:51 <cfo215> I found this... ./meta-angstrom/recipes-angstrom/angstrom/omap3-mkcard.bb  which I presume makes a SD card for Beagleboard-xM.
Sep 04 17:21:56 <cfo215> from the file: DESCRIPTION="Format a card for omap3 booting"
Sep 04 18:41:53 <cfo215> anyone here know how to create an img file from the images output by bitbake? That way I can use something to the effect of 'dd bs=1m if=nameof.img of=/dev/sdX' for creating sd cards.
Sep 04 18:53:29 <cfo215> Crofton|work, looks like that recipe is a good start.  It creates a shell-script that creates the 'boot' and 'Angstrom' partitions on the SD card.  It just doesn't copy the files to the SD card.  So I have a starting point...
Sep 04 20:42:28 <cfo215> I'm having trouble with a Flash Disk not auto mounting.  I'm using the console-image (Linux beaglebone 3.8.13 #1 SMP Tue Sep 3 14:16:18 EDT 2013 armv7l GNU/Linux).  Dumb question, but is it supposed to auto-mount?
Sep 04 20:42:53 <Crofton|work> read /etc/fstab
Sep 04 20:43:11 <cfo215> Crofton, thanks, will do
Sep 04 20:44:16 <cfo215> Crofton|work, not much in there as to explanation of how to add things... I'll google.
Sep 04 20:44:46 <Crofton|work> /dev/mmcblk0p1       /media/card          auto       defaults,sync         0  0
Sep 04 20:44:56 <Crofton|work> I always have to uncomment this line
Sep 04 20:45:08 <Crofton|work> not sure how the stuff that comes and goes is handled
Sep 04 20:45:12 <Crofton|work> check dmesg
Sep 04 20:45:17 <Crofton|work> udev rules?
Sep 04 20:45:18 <cfo215> that's not in there...
Sep 04 20:45:27 <cfo215> at least in the console-image
Sep 04 20:46:39 <Crofton|work> see if you get any messgaes when you plug it in
Sep 04 20:47:32 <cfo215> showing as sda
Sep 04 20:49:05 <cfo215> Crofton|work, I put the output from dmesg at http://pastebin.com/GyU4BRAc
Sep 04 20:51:00 <cfo215> Crofton|work, I put the fstab as i found it at http://pastebin.com/tGRKFs5J
Sep 04 20:54:14 <Crofton|work> I think there should be a udev rule that triggers the mount
Sep 04 20:54:37 <cfo215> Crofton, looking...
Sep 04 20:55:15 <Crofton|work> I'll be afk
Sep 04 21:15:51 <cfo215> Crofton|work, I created a dir in my root home and mounted it there using "mount -t vfat /dev/sda1 /home/root/flash/".  I think the problem may be because it's vfat type?  Way over my head here...
Sep 04 21:35:46 <cfo215> bluelightning, can you help me with some Qt issues?  It appears that the Qt4 recipie doesn't build Qt with -qt-gfx-transformed, therefore I keep getting "Transformed: driver not found" when i use export QWS_DISPLAY=Transformed:Rot270:0 prior to running my file
Sep 04 21:38:53 <bluelightning> cfo215: it's built as a plugin
Sep 04 21:39:32 <cfo215> bluelightning, plugin to ???.  How do I use the plugin.  Sorry, first time with Qt.
Sep 04 21:39:43 <cfo215> bluelightning, and embedded. :(
Sep 04 21:39:55 <bluelightning> as far as I know it would just need to be installed
Sep 04 21:40:11 <bluelightning> it's probably in a separate package
Sep 04 21:40:32 <cfo215> bluelightning, IC... I'll see what i can find.  BB or generated IPK?
Sep 04 21:41:44 <bluelightning> cfo215: generated ipk
Sep 04 21:41:52 <bluelightning> cfo215: looking here I think it's called qt4-embedded-plugin-gfxdriver-gfxtransformed
Sep 04 21:42:08 <bluelightning> if you wou
Sep 04 21:42:10 <bluelightning> er
Sep 04 21:42:16 <cfo215> bluelightning, thanks, I'll look
Sep 04 21:42:24 <bluelightning> if you would prefer it compiled in you can of course change the config options
Sep 04 21:42:33 <bluelightning> but installing the package should work
Sep 04 21:44:17 <cfo215> I'd probably prefer it compiled in... but I'll go the package route for now... I really  need to show the peps something today...  it's 1/3 working.   I can get it to load (1), but touch screen doesn't seem to work with it (2) and of course the problem you just solved for me.
Sep 04 21:44:44 <cfo215> i used "export QWS_MOUSE_PROTO=LinuxInput:/dev/input/touchscreen0" but that doesn't seem to help.
Sep 04 21:45:37 <cfo215>  bluelightning, though if I "cat /dev/input/touchscreen0" I do see activity when I move my finger over the touchscreen.
Sep 04 21:45:59 <bluelightning> I don't think you want linuxinput, I think you want tslib
Sep 04 21:46:24 <bluelightning> did you try ts_test btw? I think we talked about that before
Sep 04 21:48:20 <cfo215> is that a BB image?  
Sep 04 21:48:41 <bluelightning> no, ts_test is a utility
Sep 04 21:49:23 <bluelightning> part of the tslib-tests package
Sep 04 21:49:42 <cfo215> I'll have to install it.
Sep 04 21:51:49 <cfo215> bluelightning, tslib: Selected device is not a touchscreen (must support ABS and KEY event types)
Sep 04 21:52:14 <bluelightning> hmm, never seen that before
Sep 04 21:53:51 <cfo215> bluelightning, never mind... i didn't know I had to "export TSLIB_TSDEVICE=/dev/input/touchscreen0" prior to running.
Sep 04 21:54:09 <bluelightning> ah, I see
Sep 04 21:54:15 <bluelightning> I guess I knew that at some point
Sep 04 21:55:17 <cfo215> sort of working but I think i need to run ts_calibrate
Sep 04 21:56:08 <cfo215> bluelightning, "mouse" cursor disappears when I touch it.
Sep 04 21:56:34 <bluelightning> under Qt embedded or the ts utility?
Sep 04 21:57:48 <cfo215> both
Sep 04 21:58:29 <cfo215> i take that back.  "pointer" stays in middle of screen with Qt
Sep 04 21:58:52 <cfo215> but it doesn't move either and my buttons don't "click"
Sep 04 21:59:45 <cfo215> bluelightning, but I'm really happy to see it running, even in it's broken state... At least I know the toolchain is working.  Now we're down to configuration issues.
Sep 04 22:06:17 <cfo215> bluelightning, ts_test worked better after ts_calibrate
Sep 04 22:36:14 <cfo215> bluelightning, thanks for all your help.  I really appreciate it.  After loading the plugins I was able to run my test app.  I still have a lot of work ahead of me, but I'm satisfied that the OE/Yocto/Angstrom works now.
Sep 04 22:37:39 <bluelightning> cfo215: great :)
Sep 04 22:37:43 <bluelightning> cfo215: you're welcome
**** ENDING LOGGING AT Thu Sep 05 02:59:59 2013