We really need to have Board/Council/Someone trusted take official image (unavailable via normal means), apply all patches that should be applied (as official image had bugs), and publish MD5 sums of "final" release of one-step development environment for Maemo. Then, of course, such image could be distributed via kind souls, via p2p sharing networks, or so. It's a joke, that we literally *can't* have new developers for more than a year already, as setting up dev environment is impossible without asking for things in obscure IRC channels, and spending countless hours on tracing patches required. If someone digs up a few threads where people (even experienced ones, like Copernicus) tried to set up new Maemo development boxes, you may, actually, shed a few tears. Or a river of them. Currently, it's more complicated than programming for some undocumented Japanese chip in early 80's. /Estel
Check if you have problematic scratchbox: 1. Login to scratchbox: run /scratchbox/login 2. print DEB_BUILD_OPTIONS in scratchbox: echo $DEB_BUILD_OPTIONS If it does *not* show "thumb" your scratchbox is already fixed and thumb is disabled. If it *show* thumb, disable it. Instructions how to disable *thumb* string in scratchbox: 1. Login to scratchbox: run /scratchbox/login 2. Edit file /targets/FREMANTLE_ARMEL.environment 3. Remove "thumb" from that file 4. Save file and *logout* from scratchbox Note that scratchbox is loading DEB_BUILD_OPTIONS variable at startup, so you need to restart scratchbox to take effect. After restarting please check again if thumb is really disabled.
28949514fb6762733678b12afc227f73 Changed_Ubuntu_Lucid_Desktop_Files.txt 85bc1524deb7bfeadb1d4bb2f18dea57 License_Agreement.txt 8c173b04bb3951bcfd4433da554b6c3a Maemo_Ubuntu_Lucid_Desktop_SDK_Virtual_Image_Final.7z 09b45b54c2ea5669e289b102b4443e03 Readme_Ubuntu_Lucid_Desktop_SDK_Virtual_Image_Final.txt