Stuckie
Member
Hey,
Currently, the Dev Extends are causing issues with people who have been using their Pandora a bit.
Essentially, this is because its binding whatever configuration files are present in the extend over your Pandora.
The best way to solve this would be to create your own root overlay, and install the dev tools in there.. or of course, install the dev tools direct to NAND.
I have been testing out various other methods around this, such as compiler GCC in the standard cross-compiler manner, so it can be launched from a PND. However, simple tests worked fine, but complex tests caused it to fail spectacularly.. so that needs figured out a bit. I also don't seem to have the greatest amount of time these days to do fiddling, and seem to be far more tired than usual
I'd therefore advise you not to use the Dev Extends unless you know what you're doing and have backups.. however, I have never marked these things as being terribly stable, and always labeled them as the "dodgy hacks" they are. It's an interesting hack, but its becoming increasingly like something that has to be done uniquely for each Pandora, rather than a generic Dev Extend that works on all - due to the nature of the AUFS binds ( which don't always take.. grrr )
Original post hidden in the spoiler tags.
Currently, the Dev Extends are causing issues with people who have been using their Pandora a bit.
Essentially, this is because its binding whatever configuration files are present in the extend over your Pandora.
The best way to solve this would be to create your own root overlay, and install the dev tools in there.. or of course, install the dev tools direct to NAND.
I have been testing out various other methods around this, such as compiler GCC in the standard cross-compiler manner, so it can be launched from a PND. However, simple tests worked fine, but complex tests caused it to fail spectacularly.. so that needs figured out a bit. I also don't seem to have the greatest amount of time these days to do fiddling, and seem to be far more tired than usual
I'd therefore advise you not to use the Dev Extends unless you know what you're doing and have backups.. however, I have never marked these things as being terribly stable, and always labeled them as the "dodgy hacks" they are. It's an interesting hack, but its becoming increasingly like something that has to be done uniquely for each Pandora, rather than a generic Dev Extend that works on all - due to the nature of the AUFS binds ( which don't always take.. grrr )
Original post hidden in the spoiler tags.
** DEV EXTEND QUICK START **
You'll require the ExtendUtils suite: http://www.stuckiegamez.co.uk/apps/pandora/SimpleDev/extendutils.pnd this gets updated fairly regularly, so always check the Wiki documentation: http://pandorawiki.org/Extend_Utils
You'll also need a Dev Extend Package: http://www.stuckiegamez.co.uk/apps/pandora/SimpleDev/Dev.Extend.20thJune2010.zip - was the latest extend of Dev tools.
Extract the extends to the root of an SD card, and plonk the PND in your /pandora/menu.
Follow the instructions for a "Classic/Dev Extend" configuration on the Extend Utils Wiki: http://pandorawiki.org/Extend_Utils#Creating_a_Dev_Extend_Pre-Mount
Optionally, create your Home overlay as well and mount that too, check the documentation for details.
** DEV EXTEND QUICK START **
The "environment" includes pretty much what Torpor's thread recommends you install ( minus the omap demos.. I forgot them this time as once you see them once, they're a bit meh. )
SDL_Mixer was a funny one, however, as the -dev package in Angstrom seems to be of an older version that what's installed. So I somewhat cheated with that and forced an install, so there may be some issues there.
Editor wise, there's vim, nano and geany installed at least.
Source Control wise, there's CVS, SVN and GIT.
I can't remember if I installed anything else, but there's 358M left of the dev.extend file to add to, if needed.
Now, a little warning.
** WARNING ** WARNING ** WARNING ** WARNING ** WARNING ** WARNING **
This uses AUFS to mount directories from the SD Card to your NAND.
This means that it effectively locks that SD Card and you SHOULD NOT REMOVE IT before a reboot or shutdown, or you may very well cause your system to become unstable!
I have had no issues using this setup ( I've developed the PNDs I've put up with it, ) but I don't want people complaining they've hosed their system because they accidentally removed the card or something.
If you're at all paranoid, do not use this and setup a tool chain another way ( there's plenty - be it create a custom SD Card to boot from, the "standard" cross-compiler way, or just install direct on NAND )
** WARNING ** WARNING ** WARNING ** WARNING ** WARNING ** WARNING **
With that out of the way, this is what you get in your Zip file:
The "extendUtils" PND which does all the donkey work.
This is a slightly edited version of the one I previous put up in the AUFS Hackery thread, as I've found out that unmounting /home is not always possible ( makes sense really, your bash history sits in home, so you're trying to unmount it while it writes the command that you're unmounting it )
There's also the dev.extend file. This is an ext2 formatted loop-back file which contains the dev environment, and extends / over to it, so you're free to install extra things if need be. This is 512M.
Finally, there are a bunch of zip files of pre-made extend files, in 256M, 512M, 1G, 2G and 4G flavours. These will expand to what they say, so make sure you've enough space for them! ( NOTE: I've just realised I haven't formatted these... you can do this from your Pandora though: mke2fs /path/to/your.extend before mounting it.. or whatever other file system you wish to use! I'll fix this when I get back from work. )
You probably want to use one of these to extend your /home so you can keep your source code and things with you, separate from NAND and separate from the dev environment. This is actually very handy as you can reboot, mount your /home bind, and test your code on a "vanilla" Pandora to ensure it works before going through the packaging phase
It also protects your NAND from accidental /home writes from software you haven't quite tied up yet
I hope it's useful to someone.
It's certainly been useful to me, and it is effectively how I develop things on the Pandora for the moment.
[edit]
I've changed the structure of this a bit...
First you'll want the actual extend utilities. This includes a very experimental /home unbind which doesn't always behave itself.
You'll also possibly want one of the pre-formatted extend files. They come in 256Mb, 512Mb, 1Gb, 2Gb and 4Gb flavours. These are useful for a /home mount, or if you want to do a fresh root bind.
Finally, there's the original dev extend file release dated 18th June 2010.
This includes the following:
You can grab all this from here: http://www.stuckiegamez.co.uk/apps/pandora/SimpleDev
And I shall be keeping that folder up to date with the latest bits and pieces.
I'll be posting whether I've updated the PND or not, so don't worry about missing out those changes
[/edit]
Comments and suggestions for further amendments are welcome
And hopefully I haven't missed anything in my rush out the door!
[edit - 17th August]
I'm about to update this for a whole new style of Dev PND which matches closer to a standard cross-compiler install...
[/edit]
You'll require the ExtendUtils suite: http://www.stuckiegamez.co.uk/apps/pandora/SimpleDev/extendutils.pnd this gets updated fairly regularly, so always check the Wiki documentation: http://pandorawiki.org/Extend_Utils
You'll also need a Dev Extend Package: http://www.stuckiegamez.co.uk/apps/pandora/SimpleDev/Dev.Extend.20thJune2010.zip - was the latest extend of Dev tools.
Extract the extends to the root of an SD card, and plonk the PND in your /pandora/menu.
Follow the instructions for a "Classic/Dev Extend" configuration on the Extend Utils Wiki: http://pandorawiki.org/Extend_Utils#Creating_a_Dev_Extend_Pre-Mount
Optionally, create your Home overlay as well and mount that too, check the documentation for details.
** DEV EXTEND QUICK START **
The "environment" includes pretty much what Torpor's thread recommends you install ( minus the omap demos.. I forgot them this time as once you see them once, they're a bit meh. )
SDL_Mixer was a funny one, however, as the -dev package in Angstrom seems to be of an older version that what's installed. So I somewhat cheated with that and forced an install, so there may be some issues there.
Editor wise, there's vim, nano and geany installed at least.
Source Control wise, there's CVS, SVN and GIT.
I can't remember if I installed anything else, but there's 358M left of the dev.extend file to add to, if needed.
Now, a little warning.
** WARNING ** WARNING ** WARNING ** WARNING ** WARNING ** WARNING **
This uses AUFS to mount directories from the SD Card to your NAND.
This means that it effectively locks that SD Card and you SHOULD NOT REMOVE IT before a reboot or shutdown, or you may very well cause your system to become unstable!
I have had no issues using this setup ( I've developed the PNDs I've put up with it, ) but I don't want people complaining they've hosed their system because they accidentally removed the card or something.
If you're at all paranoid, do not use this and setup a tool chain another way ( there's plenty - be it create a custom SD Card to boot from, the "standard" cross-compiler way, or just install direct on NAND )
** WARNING ** WARNING ** WARNING ** WARNING ** WARNING ** WARNING **
With that out of the way, this is what you get in your Zip file:
The "extendUtils" PND which does all the donkey work.
This is a slightly edited version of the one I previous put up in the AUFS Hackery thread, as I've found out that unmounting /home is not always possible ( makes sense really, your bash history sits in home, so you're trying to unmount it while it writes the command that you're unmounting it )
There's also the dev.extend file. This is an ext2 formatted loop-back file which contains the dev environment, and extends / over to it, so you're free to install extra things if need be. This is 512M.
Finally, there are a bunch of zip files of pre-made extend files, in 256M, 512M, 1G, 2G and 4G flavours. These will expand to what they say, so make sure you've enough space for them! ( NOTE: I've just realised I haven't formatted these... you can do this from your Pandora though: mke2fs /path/to/your.extend before mounting it.. or whatever other file system you wish to use! I'll fix this when I get back from work. )
You probably want to use one of these to extend your /home so you can keep your source code and things with you, separate from NAND and separate from the dev environment. This is actually very handy as you can reboot, mount your /home bind, and test your code on a "vanilla" Pandora to ensure it works before going through the packaging phase
It also protects your NAND from accidental /home writes from software you haven't quite tied up yet
I hope it's useful to someone.
It's certainly been useful to me, and it is effectively how I develop things on the Pandora for the moment.
[edit]
I've changed the structure of this a bit...
First you'll want the actual extend utilities. This includes a very experimental /home unbind which doesn't always behave itself.
You'll also possibly want one of the pre-formatted extend files. They come in 256Mb, 512Mb, 1Gb, 2Gb and 4Gb flavours. These are useful for a /home mount, or if you want to do a fresh root bind.
Finally, there's the original dev extend file release dated 18th June 2010.
This includes the following:
+ alsa-lib
+ alsa-lib-dev
+ bigreqsproto
+ bigreqsproto-dev
+ binutils-dev
+ cpp
+ cpp-symlinks
+ cvs
+ devmem2-dev
+ fbset-dev
+ fontcacheproto
+ fontcacheproto-dev
+ g++
+ g++-symlinks
+ gcc
+ gcc-doc
+ gcc-symlinks
+ geany
+ gettext
+ gettext-dev
+ git
+ glibc-extra-nss
+ inputproto
+ inputproto-dev
+ kbproto
+ kbproto-dev
+ libapr-1-0
+ libaprutil-1-0
+ libc6-dev
+ libexpat-dev
+ libfontenc-dev
+ libfreetype-dev
+ libgettextlib
+ libgettextsrc
+ libgles-omap3-dev
+ libgmp-dev
+ libgmp3
+ libjpeg-dev
+ liblzo-dev
+ liblzo1
+ libmpfr-dev
+ libmpfr1
+ libpixman-1-dev
+ libpng-dev
+ libsdl-1.2-dev
+ libsdl-gfx-dev
+ libsdl-image-1.2-dev
+ libsdl-net-1.2-dev
+ libsdl-ttf-2.0-dev
+ libsdl-mixer ( forcibly hacked on.. Angstrom's version is older than what's on the Pandora for some reason. )
+ libstdc++-dev
+ libtiff-dev
+ libts-1.0-dev
+ libx11-dev
+ libxau-dev
+ libxdmcp-dev
+ libxext-dev
+ libxfont-dev
+ libz-dev
+ linux-libc-headers-dev
+ make
+ make-dev
+ ncurses-dev
+ subversion
+ update-rc.d-dev
+ util-macros
+ util-macros-dev
+ xcmiscproto
+ xcmiscproto-dev
+ xextproto
+ xextproto-dev
+ xf86bigfontproto
+ xf86bigfontproto-dev
+ xproto
+ xproto-dev
+ xtrans-dev
+ alsa-lib-dev
+ bigreqsproto
+ bigreqsproto-dev
+ binutils-dev
+ cpp
+ cpp-symlinks
+ cvs
+ devmem2-dev
+ fbset-dev
+ fontcacheproto
+ fontcacheproto-dev
+ g++
+ g++-symlinks
+ gcc
+ gcc-doc
+ gcc-symlinks
+ geany
+ gettext
+ gettext-dev
+ git
+ glibc-extra-nss
+ inputproto
+ inputproto-dev
+ kbproto
+ kbproto-dev
+ libapr-1-0
+ libaprutil-1-0
+ libc6-dev
+ libexpat-dev
+ libfontenc-dev
+ libfreetype-dev
+ libgettextlib
+ libgettextsrc
+ libgles-omap3-dev
+ libgmp-dev
+ libgmp3
+ libjpeg-dev
+ liblzo-dev
+ liblzo1
+ libmpfr-dev
+ libmpfr1
+ libpixman-1-dev
+ libpng-dev
+ libsdl-1.2-dev
+ libsdl-gfx-dev
+ libsdl-image-1.2-dev
+ libsdl-net-1.2-dev
+ libsdl-ttf-2.0-dev
+ libsdl-mixer ( forcibly hacked on.. Angstrom's version is older than what's on the Pandora for some reason. )
+ libstdc++-dev
+ libtiff-dev
+ libts-1.0-dev
+ libx11-dev
+ libxau-dev
+ libxdmcp-dev
+ libxext-dev
+ libxfont-dev
+ libz-dev
+ linux-libc-headers-dev
+ make
+ make-dev
+ ncurses-dev
+ subversion
+ update-rc.d-dev
+ util-macros
+ util-macros-dev
+ xcmiscproto
+ xcmiscproto-dev
+ xextproto
+ xextproto-dev
+ xf86bigfontproto
+ xf86bigfontproto-dev
+ xproto
+ xproto-dev
+ xtrans-dev
You can grab all this from here: http://www.stuckiegamez.co.uk/apps/pandora/SimpleDev
And I shall be keeping that folder up to date with the latest bits and pieces.
I'll be posting whether I've updated the PND or not, so don't worry about missing out those changes
[/edit]
Comments and suggestions for further amendments are welcome
And hopefully I haven't missed anything in my rush out the door!
[edit - 17th August]
I'm about to update this for a whole new style of Dev PND which matches closer to a standard cross-compiler install...
[/edit]