xiangfu has quit [Remote host closed the connection]
atommann has joined #qi-hardware
pcercuei has quit [Quit: dodo]
panda|z has quit [Ping timeout: 240 seconds]
panda|z has joined #qi-hardware
xiangfu has joined #qi-hardware
fmeerkoetter has joined #qi-hardware
xiangfu has quit [Ping timeout: 272 seconds]
xiangfu has joined #qi-hardware
fmeerkoetter has quit [Ping timeout: 250 seconds]
<unclouded>
very tempted to, but.. time
<wpwrak>
it's not as if there would be a maze of dialog screens awaiting you ;-)
wolfspraul has joined #qi-hardware
atommann has quit [Ping timeout: 246 seconds]
atommann has joined #qi-hardware
wolfspraul has quit [Ping timeout: 240 seconds]
wolfspraul has joined #qi-hardware
wolfspraul has quit [Ping timeout: 255 seconds]
wolfspraul has joined #qi-hardware
michael_lee has joined #qi-hardware
wolfspraul has quit [Ping timeout: 240 seconds]
wolfspraul has joined #qi-hardware
unclouded has quit [Quit: Leaving]
wolfspraul has quit [Ping timeout: 240 seconds]
wolfspraul has joined #qi-hardware
michael_lee has quit [Ping timeout: 260 seconds]
atommann has quit [Quit: Leaving]
lindi-_ is now known as lindi-
lindi- has quit [Changing host]
lindi- has joined #qi-hardware
pcercuei has joined #qi-hardware
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
wolfspraul has quit [Ping timeout: 240 seconds]
michael_lee has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
<DocScrutinizer51>
emulator?
<DocScrutinizer51>
for some SoC?
<DocScrutinizer05>
dammit, I won't be able to eat up those 1.5GB data volume. left VNC connected for 8h and it only used up 200MB ;-P
<DocScrutinizer05>
apropos:
<DocScrutinizer05>
wpwrak: how about you already start with maemo-scratchbox? give it a test, it gives you a first impression of what's awaiting you when we get that device to yours
<DocScrutinizer05>
[2014-08-20 Wed 15:35:08] <infobot> well, scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB
<DocScrutinizer05>
get the VM image from merlin's place!
<DocScrutinizer05>
actually I found the xephyr based emu quite exciting, it kinda really feels like the true thing: maemo on N900
<wpwrak>
DocScrutinizer05: (simulator) for anelok, just for GUI development. provides "touch" input and display
<wpwrak>
(scratchbox) i'll have a look at it
* mth
thinks scratchbox is the wrong approach...
<mth>
you can't completely hide the fact that you're doing a cross build
<mth>
and in the cases where it fails, scratchbox is an extra layer of complexity to deal with when debugging
<DocScrutinizer51>
sb is a nightmare
<DocScrutinizer51>
but the result is awesoome
<DocScrutinizer05>
even Nokia tried to come up with something more sleak: MADDE
<DocScrutinizer05>
but aiui MADDE needs a real N900 attached to PC to run the binaries on there, while sb has a complete emu of N900 (well, almost complete. obviously no phone calls, no GPS etc)
<DocScrutinizer05>
and they even use x86 binaries for that, aiui
* ysionneau
wonders what scratchbox is
<ysionneau>
is it like a mix of buildroot+qemu ?
<mth>
but how often do you really need to run target binaries as part of the build? only a few packages need something like that
<DocScrutinizer05>
ysionneau: yes
<mth>
most cross build problems are bad configure scripts that do things like hardcoding /usr/include into CFLAGS
<DocScrutinizer05>
it's not about building, it's about testing
<ysionneau>
ok
<mth>
I never got past the build stage before I dumped it ;)
<DocScrutinizer05>
haha
michael_lee has quit [Quit: Ex-Chat]
<ysionneau>
I watched a video of scratchbox on the web, it made me think about Android emulator (which is Qemu)
<DocScrutinizer05>
do NOT use the gui tool to install sb! actaully do not install sb at all ;), just use the VM image of merlin's server
<DocScrutinizer05>
I heard somebody managed to install sb natively only 2 months ago, and took him only one day
<DocScrutinizer05>
so it *can* be done
<DocScrutinizer05>
I suggest to steer clear
<wpwrak>
hmm. it starts increasingly like the sort of operation that needs a thorough backup before you try it ...
<DocScrutinizer05>
what? installing sb? it just creates a /sb/ dir of some 5GB size on your PC. Then eventually a initscript will start a chroot in there
<DocScrutinizer05>
so a good way to nuke your PC is a rm -rf /sb
<DocScrutinizer05>
like with any other chroot
<wpwrak>
5 GB. more fun then.
<DocScrutinizer05>
yeah, friggin bloated
<DocScrutinizer05>
that's however incl kernel sources and all, iirc
<DocScrutinizer05>
the VM is slightly >1GB
<DocScrutinizer05>
for installing rootstraps you need a "token", google is your friend, or justr ask me
<wpwrak>
it sounds increasingly like the sort of software i'd rather not have on my system :)
<DocScrutinizer05>
hmm, no. nothing wrong with it, once it's installed (or started in VM even, which I recommend)
<DocScrutinizer05>
sb itself is a biatch
<DocScrutinizer05>
and the bindmounts are as nasty as are on any other chroot
<DocScrutinizer05>
nevermind them in a VM however
<DocScrutinizer05>
just NEVER do a `rm -rf <chrootdir>` while stuff like /proc and /sys etc is still bindmounted to the chroot dir. That's general advice for all *nix chroots
<mth>
rm has a --one-file-system option that might help against that
<mth>
*might* because I'm not sure it would help against bind mounts on the same fs
<DocScrutinizer05>
maemo itself has some closed blobs e.g. powervr driver lib 3D) which need some "authentication" to download them from Nokia repo
<DocScrutinizer05>
mth: solution: "stop" the chroot before doing any rm
<DocScrutinizer05>
alas you forget about that lil detail every now and then
<DocScrutinizer05>
that's why I *always* emphasize it