Related
Looking for some assistance getting the NDK working properly on Windows 7 (64).
I followed all of the instructions to set up the NDK in windows but am running into an issue.
Per the instructions you need to install CYGWIN which i did and then go to the root NDK folder and run build/host-setup.sh.
Once I run this i get the following error;
ERROR: Could not find a valid GNU make executable.
Please ensure GNU Make 3.81 or later is installed.
Click to expand...
Click to collapse
I do have GNU make 3.81 installed for windows.
If i try to use cygwin to run a make APP=hello-jni as a test as it states i get the error;
bash: make: command not found
Click to expand...
Click to collapse
if i use windows command prompt i can run the make.exe fine.
I'm thinking the issue is because its trying to use a Linux based make since i would assume Cygwin cannot rune EXE files.
Could anyone assist me with this that has it set up and working properly in windows?
Any takers please?
Check 'Make' package in Cygwin setup.
Do yourself a favor and use a real operating system. Ditch that MSJUNK.
On top of that, I *strongly* suggest that NOBODY EVER use windoze for compiling ANYTHING. When you are building software for other people to use, you most *definitely* do NOT want to build software that has been compromised. Windoze is the world's number ONE compromised platform. It about as save as having your way with a 50 year old street corner hooker without protection.
Hey there, I'm compiling the android source with a couple of mods merged in from cyanogenmod and leonnib4. I was getting a few random errors, but they went away with simple fixes...Now, I'm getting a new error, and I can't seem to wrap my head around it. It happens almost right out of the gate...every time I type make...
EDIT: New error 41. I seemed to have fixed the old error 1 by removing the previous build from out/target/product/passion, as the error pointed to the obj folder. Everything went smooth until the camera, and now I have a new error. I'm trying to merge in CyanogenMod camera source (for 720p), and I think that's the problem. Could it be something in the framework? I'm lost.
I have set up my build env on a MacBook Pro running OS X 10.5.8 with all the proper tools installed as per the AOSP site's instructions. I have run the envsetup script, and chosen the passion lunch option (yum )...
Anyway, here's the error:
Code:
81 errors
make: *** [out/target/common/obj/APPS/Camera_intermediates/classes-full-debug.jar] Error 41
The full scenario on pastebin: http://pastebin.com/8359mktC
Does anyone have any idea what's going on?
ik this is really old but what did u do to fix this? having the same error compiling cm9
Maybe we can get a group knowledge base going, I'm attempting to build CM6 right now. The idea is to help out with Vibrant porting, but I'm getting stuck and thought you guys might have some hints. If I can get it going, I'll update the wiki or create one somewhere else for Vibrant specific stuff.
So, right now my build system is 64-bit Ubuntu 9.04. I can switch, it looks like it might be better to be on a 32-bit setup, so there's one option.
The basic path to where I am now, following basic directions from here: http://wiki.cyanogenmod.com/index.php?title=Building_from_source
Code:
sudo aptitude install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
sudo aptitude install ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib
curl http://android.git.kernel.org/repo >~/bin/repo
chmod a+x ~/bin/repo
export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
(Path modified to match my local path)
repo init -u git://github.com/CyanogenMod/android.git -b froyo
repo sync
source build/envsetup.sh
make -j4 adb
This results in a segfault....
Code:
host Executable: adb (out/host/linux-x86/obj/EXECUTABLES/adb_intermediates/adb)
true
Install: out/host/linux-x86/bin/adb
make: *** [out/host/linux-x86/bin/adb] Segmentation fault (core dumped)
Using "lunch" and selecting a target, then "make clean" gives me the same error building adb. Attempting to build the ROM also gives me a segfault, so at least I'm consistent. It always seems to be on an "Install" step, if that helps.
If you get it to compile be sure to post, I'd love to start helping I just lack motivation and free time... And knowledge around Android, but I'm working on that piece
ttabbal said:
Maybe we can get a group knowledge base going, I'm attempting to build CM6 right now. The idea is to help out with Vibrant porting, but I'm getting stuck and thought you guys might have some hints. If I can get it going, I'll update the wiki or create one somewhere else for Vibrant specific stuff.
So, right now my build system is 64-bit Ubuntu 9.04. I can switch, it looks like it might be better to be on a 32-bit setup, so there's one option.
The basic path to where I am now, following basic directions from here: http://wiki.cyanogenmod.com/index.php?title=Building_from_source
Code:
sudo aptitude install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
sudo aptitude install ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib
curl http://android.git.kernel.org/repo >~/bin/repo
chmod a+x ~/bin/repo
export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
(Path modified to match my local path)
repo init -u git://github.com/CyanogenMod/android.git -b froyo
repo sync
source build/envsetup.sh
make -j4 adb
This results in a segfault....
Code:
host Executable: adb (out/host/linux-x86/obj/EXECUTABLES/adb_intermediates/adb)
true
Install: out/host/linux-x86/bin/adb
make: *** [out/host/linux-x86/bin/adb] Segmentation fault (core dumped)
Using "lunch" and selecting a target, then "make clean" gives me the same error building adb. Attempting to build the ROM also gives me a segfault, so at least I'm consistent. It always seems to be on an "Install" step, if that helps.
Click to expand...
Click to collapse
This usually meanings that there is a memory management issue but im no dev hope this helps
Now if we had others posting about what they have done.... hint...
OK, I know there aren't a ton of us messing with things at this level. Hopefully someone else has seen this. I'll try to install a 32-bit Ubuntu 10.whatever tonight and see if that helps. It is possible my issues are being caused by the 32-bit compatibility libraries or similar.
ttabbal said:
Now if we had others posting about what they have done.... hint...
OK, I know there aren't a ton of us messing with things at this level. Hopefully someone else has seen this. I'll try to install a 32-bit Ubuntu 10.whatever tonight and see if that helps. It is possible my issues are being caused by the 32-bit compatibility libraries or similar.
Click to expand...
Click to collapse
I just installed ubuntu32, and am going through the repo sync, as soon as that finishes, I'll pack up and head home and finish there, hopefully it compiles on 32bit. I'll post back as soon as i know.
I've considered contacting them that way, I was hoping the community would be interested in getting a few more devs going. I'm downloading the Ubuntu 32-bit ISO now. If you want to send them a message, cool. I'll fool with things a bit more and if I still can't get anywhere, I'll see if I can get in with thouse guys. If I do get it working, I'll try to document everything that's not covered elsewhere. I just hate to take time away from their work to help out a newb.
If you can't build, you can't contribute. The Android build system is somewhat custom and weird, so it can be off-putting to people that would be interested in helping. More people hopefully means we can get more done.
ttabal, seg fault during a "make" usually means it tried to access something that wasn't there. Make sure you have all dependencies installed. Someone said seg fault has to do with memory management ... yeah, only when running an app. When building (aka "make"), there are a lot of things being linked and each thing has a ton of dependencies and that continues recursively ... it's why I hated working with Unix back in the day. You change one thing, you have to change everything and its mother.
Still, I have been frustrated at the lack of progress recently that I am toying with the idea of jumping back in the pool and building things myself. I wish one of the more experienced folks here would offer a primer. I know what they're afraid of though ... every noob coming back with a million questions, like, "what's apt-get?" or "what's a make file?".
Yeah, maybe we should start up an invite-only dev forum and only allow public read-only access to a wiki or something so we can share with everyone. I'd love to be more open, but I do see why the big devs don't do their dev conversations here.
I did install the depandancies they listed on the Cyanogen Wiki, but it is possible they need something new that isn't listed. Hopefully someone can help us out. It's also possible my versions of the libraries need updating as I am on an older build of Ubuntu. I have another machine I can install the newer version on, and I'll try that first. May as well make sure I'm doing everything I can. I just can't install on the other machine as it's a production server for my home system. The wife gets mad if I break the TV server.
I know you are attempting to build the source, and I'm sorry I cannot help you with that. I just wanted to put a link up here for people that are getting inspired by you and are considering contributing to the rom development community.
http://forum.xda-developers.com/showthread.php?t=667298
It's a post by cyanogen about how you should go about getting in to rom development.
I managed to get it to build for Dream/Sapphire by first doing
Code:
#repo init -u git://android.git.kernel.org/platform/manifest.git
THEN
Code:
#repo init -u git://github.com/CyanogenMod/android.git -b froyo
#repo sync
#source build/envsetup.sh
on 64 bit Ubuntu. Did a bit more fidgeting after that to get it working, I'll see if
I can figure it out next time I'm home.
Interesting. I'll try pulling the aosp manifest first. Perhaps that will help. Did you do a repo sync on the aosp or just init?
There was a core dump, so if you have the core.dump file in the same directory where you ran "make" run strings against it, it might tell you what's segfaulted on you.
I got past make adb on Ubuntu 10.04 64-bit. Compile has been going for quite some time now. I haven't tried building a kernel yet.
Will be attempting a build on Monday with my secondary box at work running ubuntu. I have a knack for jury rigging things to work and more than willing to contribute, despite lacking the experience. For reference, you could try to converse with then on irc, freenode.net server, in #cyanogenmod or #sgs_dev, a bit more of a direct line to #teamdouche
Sent from my SGH-T959 using XDA App
ttabbal said:
The G1 was easy to dev for by the time 2.2 came out, and CM was already building on that platform. It's a lot easier to update an existing setup than trying to start on a new platform.
And proof-read, swype isn't perfect.
Click to expand...
Click to collapse
From what I understand (witch is very little) the G1 drivers have all been reverse engineered for some time and building it from source is incredibly easy at this point. While the Galaxy S is incredibly hard to develop for because all the drivers are wrapped up in all the kernel mods Samsung did, even though they open sourced much of it, its hard to unravel the code.
Build completed. Only issues I ran into:
1) repo sync didn't complete at first because I had never talked to android.git.kernel.org. Running "repo init -u git://android.git.kernel.org/platform/manifest.git" as anomalous3 said fixed that.
2) make complained about not being able to find RomManager.apk, so I went into vendor/cyanogen and ran get-rommanager. While I was in there i ran get-google-files and extract-google-files as well, but not sure if that was necessary.
At this point I'm not sure of the kernel requirements for attempting to run this system.img. Until I learn a bit more about the kernel and ramdisk I'm hesitant to do anything with this.
elderberry said:
Build completed. Only issues I ran into:
1) repo sync didn't complete at first because I had never talked to android.git.kernel.org. Running "repo init -u git://android.git.kernel.org/platform/manifest.git" as anomalous3 said fixed that.
2) make complained about not being able to find RomManager.apk, so I went into vendor/cyanogen and ran get-rommanager. While I was in there i ran get-google-files and extract-google-files as well, but not sure if that was necessary.
At this point I'm not sure of the kernel requirements for attempting to run this system.img. Until I learn a bit more about the kernel and ramdisk I'm hesitant to do anything with this.
Click to expand...
Click to collapse
Thanks! I'm running repo sync after the kernel.org init now. I'll see if that gets me building. I don't suggest installing anything you build yet, I want to see if we can get a couple people building before we take that step. Though it looks like we can create some nice update.zips now that flash the kernel and such. Very cool.
Anyone know how to replace parts of a local git with your own repo? I would like to clone my fork of wesgarner's vibrant tree into the main tree so I can do commits and such without messing with anyone else's stuff. git rebase? I'm a little new to git, I've only ever used it for basic stuff that SVN can do.
Looks like the sync is going to take a bit for me. Damn. I'll install the latest Ubuntu in a VM while I'm waiting on it. Who do I have to kill to get FIOS in Utah?
Hmmm... Still no joy for me. Must have done something wrong I guess. Build still segfaults and I don't get a coredump. Weird.
Thanks for the contact info for teamdouche, I'm trying to avoid bothering them until I at least have a working build. This isn't the sort of level one should bother them about IMO.
Looks like you guys are talking to wes and the others
If you guys get it working. I have a build env setup + a build bot. Just let me know
i'm installing the dev support packages right now. i'm worried, though. how much space are we looking at? my linux partition is only 8gb. so i may have to modify some things so it's all on my raid storage.
Ok, this goes out to any and all DEVs out there. We all know by now that we (some people not me) can run linux within android using the loop mounts, vnc viewer, etc... Now how about REPLACING android with a linux distro like debian or maybe even what these guys use http://openpandora.org/ ..... its linux based and has an arm CPU.. Any way I'm talking about flashing over android wiping the internal sorage and installing linux on it or even using the boot loader to flash over android???, of course this is getting rid of any 3g connection and phone usage. I understand that, I am talking about giving our RETIRED droid 1s a use. I wanna see my D1 run a linux distro in full hardware mode NO MORE ANDROID. now dont get me wrong I love android as much as the next guy, but why now flash something else to it???
Another link I found, this is for windows mobile but hey, similar idea.
http://wing-linux.sourceforge.net/trac/wiki/FAQ
P.S. I AM NOT A DEV JUST AN IDIOT WITH AN IDEA!! my ignorance is NOT bliss and I would love to know if this is even possible. I'm willing to help ANY WAY I CAN. lol
THANKS!!!
I don't think it's possible. Because of the locked bootloader we're forced to use Motorola's bug-ridden Kernel and as Android's Kernel is a heavily modified Linux Kernel it most likely won't run an ordinary Linux distro.
But I'm no expert either
Milestone is locked, Droid is not ...
Maybe this will help (if you don't know german, you can use Google Translate):
http://www.android-hilfe.de/anleitu...debian-chroot-mit-lxde-auf-dem-milestone.html
Thanks for the replies. Again the USA Droid 1 is nit locked or at least has been completely unlokcked. I've read a million "run debian on android" posts... I don't need to know German to see that the post above is the same thing. Like I said before I have NO INTEREST IN RUNNING LINUX ON ANDROID. I want TO REPLACE android completely with Linux to make a device like the openpandora handheld from my first link.
Any one up to the challenge????
Thanks again!
Really, no one??
I've been running Debian on my Droid booting from the SD card for a while, more recently trying Arch Linux after realizing that anything optimized for ARMv7, VFPv3, NEON, or Thumb-2 (I'm not sure which unfortunately) won't boot because of a page fault or something. Ubuntu, MeeGo, and Angstrom just kernel panic and don't give any useful information even at the highest debugging level. I'm back to using an ARMv5te Arch Linux build (http://archlinuxarm.org) although I could just as well use Debian. I really wish Ubuntu worked for multitouch.
Well, I got the touchscreen calibrated! I forgot that my screen rotation hack only rotated the framebuffer It's stuck in portrait for now. I decided to use mtev (MeeGo's multitouch X11 input driver) after being fed up with evdev's aversion to being rotated, but now that I'm back to the stock portrait rotation evdev should work fine.
If you want instructions, either PM me or wait until I post a full guide and/or my patched kernel tree. It's not super difficult, but it's a lot of command line use and compiling.
What works:
*CPU and SD card (obviously )
*Touchscreen (single touch/portrait only for now)
What needs work:
*Keyboard mapping is wrong, the number keys and symbols don't work. I need to figure out how Android handles Alt. I had to patch the GPIO keyboard driver because the keyboard worked in the console but not in X11, which expects EV_SYN.
*Sound is OSS only, but there is no mixer device, so aumix is useless and there's no volume control or sound output.
*I haven't tried the SGX driver, so I can't comment on hardware acceleration yet.
*Battery charging relies on battd, which is a proprietary Android binary from Motorola. It might run on Debian with "ls -s / /system" and the creation of the socket it expects (init.sholes.rc I believe), but I'm not getting my hopes up.
Untested:
*WiFi (needs firmware, but should work)
*Bluetooth
*Calls/data
*Sensors (although the accelerometer and compass seem to be recognized by evdev)
I'll upload my kernel, either as patches or on GitHub (or binaries if there's enough demand) once I get around to fixing the keyboard issue. Fingers crossed that I don't get carried away cleaning up the kernel, or worse yet, give up...
This is incredible news! I'm so glad to hear it. Of course you are running in hardware mode? Not through android? If so I'm super exited about this! I love arch Linux, I run it on all my computers and I understand it more than any other distro I've tried. I would love to give it a shot, though I'm not that great at compiling I think it will be worth it.
As I said before I am in no way a dev or even a Linux pro, but I can get by and if theres any way I can help this project become "complete" I'm willing to learn what ever is necessary to do so.
Also were u able to get an x server running? Possibly a DE? That would be crazy awesome.
Thanks a million, looking foreword to work with you and make this happen!
For anyone who's interested, I put together a quick package containing my kernel patches, configuration notes, and an automated kernel build script.
It's pretty self-explanatory aside from the installation of the root filesystem, which I leave up to your imagination
As I've probably repeated several times now, I've run Debian and Arch Linux natively on my Droid with my patched kernel (no chroot or VNC "hack"). With enough determination, it's possible to run practically anything on it - personally, I'm determined to get Ubuntu on it.
WOOT... insta-fail for me LOL you have it set up to work in specific directories? I thought i placed everything right but I guess not.. I got an error on the first line of output lol
Welcome to gTan64\'s lazy Droid kernel compiler\!
build.sh: line 5: [: missing `]'
build.sh: line 5: -z: command not found
build.sh: line 5: -z: command not found
Entering $WORK
Applying patches
build.sh: line 16: /*.patch: No such file or directory
mv: cannot stat `/arch/arm/boot/compressed': No such file or directory
cp: cannot stat `/compressed': No such file or directory
Setting up build
cp: cannot stat `/GNUmakefile': No such file or directory
cp: cannot stat `/sholes_config': No such file or directory
FIXME! No numeral or symbol input until someone finds a third-level
modifier key to use instead of AltGr for the keyboard.
cp $MISC/defkeymap.map $K_SRC/drivers/char
Building kernel!
make: *** No targets specified and no makefile found. Stop.
Kernel build done!
You have done something amazing, I'm just to stupid to figure it out my self. XD
I can understand why you would want ubuntu with all its pre-setup glory and support for nearly all hardware but dont you think its a little heavy for this hardware? lol I doubt you would try to use the Unity UI but I doubt that alone would even fit in ram LOL you could just use the ubuntu packages and drivers with debian maybe?
THANKS AGAIN!!!!
That's what happens when I don't test my own scripts
I was thinking too much about making it easy. Just try applying my patches to your tree manually.
Code:
cd kernel_src
patch -p1 <../patches/first.diff
patch -p1 <../patches/next.diff #and so on...
#Obviously, substitute the paths of the actual patches ;)
#Finally, copy sholes_config to .config and invoke 'make'.
It's actually much simpler than my script makes it, and you don't need my convoluted folder setup.
UM lol I cant find any patch files? are they in the ZIP? or do I have to obtain them elsewhere?
I can tell this is gonna be a hell of a project LOL
THANKS!!!
"Duh" moment - I used the .diff file extension instead of .patch
I'm such a scatterbrain... Remind me not to release anything before testing
EDIT: Strike that, reverse it. They're .patch files.
I AM BLIND lol I found them... BUT.. when I try to patch. terminal just seems to lock up... I press enter, the curser moves to the next line but it doesnt do anything. lol how long should 1 patch take?? its been about 10 minutes and I leave it be for now
EDIT:
LOL i forgot the "<" in the command OOPS but I'm not seeing any .config file or folder in the source to copy the sholes_config too. yes I have show hidden files on.. PS unfortatly usinf Fedora 15 gnome 2...... (on server so I can work on this anywhere through vnc )
THANKS
When I said "copy sholes_config to .config", that's literally what I meant. .config is the Linux kernel build configuration file, not a folder.
'cp /path/to/sholes_config .config' from your kernel tree should do it.
Oh, I forgot to mention that you need an ARM cross-compiler/toolchain. I use the gcc-arm-linux-gnueabi package in Ubuntu, but I don't know what the Arch equivalent is off the top of my head.
The "GNUmakefile" is just a convenience, it exports "ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-" before calling the actual makefile. If you don't have an ARM cross compiler in your path, it won't build at all. If you do, modify CROSS_COMPILE to point to it - on some systems it's called arm-unknown-linux-gnueabi, etc. etc.
Let me know if you get anywhere before it errors out.
OK I put the config file in the kernel_src but unfortainatly I'm using Fedora 15 XP I installed arm-gp2x-linux-gcc which is the fedora arm gcc I guess... lol so wha would I edit in the .config to make it point to arm-gp2x-linux-gcc. Its not my first attempt to compile an android kernel but I've never been succesfull LOLOL
thanks
I'm pretty sure that toolchain won't work - the GP2X was ARMv5 IIRC, so unless it's a newer build of GCC (4.3 or higher) and you're absolutely sure it supports the ARM EABI and the ability to generate ARMv7 instructions (which is unlikely if it's pre-4.1), I would recommend a newer toolchain.
CodeSourcery makes a pretty solid one: https://sourcery.mentor.com/sgpp/lite/arm/portal/release1803
If you end up using it, you can change the second line in GNUmakefile to "CROSS_COMPILE=arm-none-linux-gnueabi-". Don't worry about changing .config.
Well I DLed the linux/GNU installer and it gave me "arm-2011.03-41-arm-none-linux-gnueabi.bin" LOL
so I was thinking would it just be easier to just use my lappy with crunchbang (debian based) so I can follow ur instructions with deb / apt-get LOL fedora is a ***** and it dont have what I need... I cant find an arm v7 cross compiler for it
thanks
.bin files are the Linux equivalent of Windows EXE installers. Run it like this:
Code:
#cd /path/to/installer.bin
./installer.bin
#substitute the actual name, of course.
It needs root permissions if you want to install it to /usr/local (sudo ./installer.bin or su -c 'sh installer.bin'). You can also install it to /usr, but that will make it more tedious to uninstall later. If you decide to install it in your home folder - say ~/toolchain - you don't need root permissions, but you will need to add ~/toolchain/bin to your path:
Code:
export PATH=$PATH:$HOME/toolchain/bin
To be honest, I prefer Ubuntu to Fedora/OpenSUSE/$RPM_distro, so if you have access to a Debian or Ubuntu system, using that would make my life easier
Omg duh... the "non_Linux" part of the name true me off lol i'll start doing this on my laptop it's deb based crunchbang. I prefer anything over rpm distros too but it was a quick painless install on my server XP thanks ill try this when I get home
Sent from my DROIDX using XDA App
So, I've been doing some Android development tutorials, as I have almost no experience in any sort of coding. I'm working in Ubuntu 11.10 with android-sdk-linux, Eclipse IDE, & java version 1.6
Things are going ok, but...
I tried to export a signed apk of my application project from Eclipse yesterday, and when I try to install it on my D3 I get this error:
HTML:
Error Parsing Package
What am I doing wrong?
thanks in advance...
lunacie said:
So, I've been doing some Android development tutorials, as I have almost no experience in any sort of coding. I'm working in Ubuntu 11.10 with android-sdk-linux, Eclipse IDE, & java version 1.6
Things are going ok, but...
I tried to export a signed apk of my application project from Eclipse yesterday, and when I try to install it on my D3 I get this error:
HTML:
Error Parsing Package
What am I doing wrong?
thanks in advance...
Click to expand...
Click to collapse
Sorry bro, I have no idea. You might get more help Android Development and Hacking or more specifically Android Software Development which is a subforum of the first link. Sorry I personally can't help you out more than that, wish I could.
If your device is recognized as a development device, you should be able to just hit the 'Run' button and it should compile your app, install it to the device and automatically launch it. Your device needs to have USB debugging turned on and you need to have the ADB driver installed (need to get it from Motorola if this is a Moto device, it won't install automatically like the rest of the storage drivers).
My Droid3 shows up as ???????? in adb. I was exporting a signed apk to install because I can't get the device to recognize. Am I missing a configuration of some kind? I'm guessing there's some kind of vendor code or something that I need for ADB to work properly with my phone?
tnx
EDIT: think I figured it out. it's the udev rules, looks like i'm on the right track....
EDIT 2: Got it! Thanks for the heads up.