Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.
someone needs to close this thread before this flame war gets any bigger
tekgek said:
Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.
Click to expand...
Click to collapse
Have you tried just pushing with adb? By development do you mean cooking or compiling your own?
Please be respectful of others ...
I taken the time to cleanup this thread and move to Q&A where it should have been. If someone has an answer post a reply; plans to respond using trolling tactics are ill-advised.
If the thread goes OT again, a moderator will be forced to close it and likely remove it ... would be nice if it didn't have to come to that.
Regards,
I am building this directly from AOSP, from scratch. Thanks to the mod for cleaning up the flame war, by the way
Oh, from AOSP. How are you adding them in? AOSP does NOT include the Google Apps by default, I'm not expert in ROM building but I am sure there are some .libs needed (I know GTalk requires some) and possibly need the other Google Apps as well.
And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
./adb install alpha-1-signed/system/app/Vending.apk
898 KB/s (1274068 bytes in 1.384s)
pkg: /data/local/tmp/Vending.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Click to expand...
Click to collapse
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
EDIT: For all of you who are currently viewing this thread, how many of you would like a very fast (possibly faster than OpenEclair), stable, no-frills Android 2.1 ROM? I would like your opinions, because this will give me a good idea of how many people would be interested in this kind of thing.
Tekgek
tekgek said:
And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
Tekgek
Click to expand...
Click to collapse
It's good to know that you are missing libraries
Your best bet is to compile your rom, and then compare it to a rom that already has the google apps included (WesGarner build, CSDI, etc...) and see what libs are missing from yours, add them in and then try again
I was having the same problem too. I am gonna try this too.
And ya besides the libraries, the aosp build doesn't include some of the framework files and permission files too, like the framework files relating to gtalk and google maps should be added as well to the system/framework folder and the permission files in system/etc/permissions relating to gtalk and maps should be added as well.
I tried with all the missing libraries but with no luck...there must be some other files tooo. Gonna continue on Thursday.
Did you try resigning the apk file?
Not really. I am gonna try that too. Got coll tomorrow so may be later tomorrow. By the way did you got the video working?? I tried pushing some libraries from supereclair. But not workin till date. it works in his build though.
College is more important than android, imho. whenever you get the chance .
I hope to get video working in the future, but not right now. My primary computer (the core i7 rig I use for all my computer work) needed an OS reinstall, so I have made no progress since my post on ADB. My fist priority is to get the basics working, then I'll work on the other issues, like video playback and the camera. However, as of right now, I am re-downloading the source, and hopefully building it in the very near future, expect an update tomorrow, and maybe even a finished product (keep in mind that this is ALPHA, so don't expect anything wonderful).
Alright, I got it... mostly. The market appears installed, now all I need to do is make it not crash. Whenever I select the market app, I get a white screen, and then the home screen. I'm also getting a force close on the gapps process. What am I doing wrong
How did you got market show up???
The gapps framework file is also missin in the /system/framework folder in AOSP build.
Did you tried pushing the missing file?
I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.
tekgek said:
I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.
Click to expand...
Click to collapse
ya its com.google.android.gtalkservice.jar
okay, added it in, still getting a force close on the gapps. Where to go now???
As i mentioned earlier there are some files missing in system/etc/permissions. Did u tried pushing those files.
All permission files are in place, all gapps are resigned. The framework is in place. The setup wizard i also resigned, which now crashes. If anyone has any suggestions please post them. I am at my wit's end here.
For those of you who have a need for the URLs of new Chromecast updates without actually updating your device, you can manually perform a checkin by POSTing the following XML to https://tools.google.com/service/update2 (make sure to set Content-Type to text/xml):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<o:gupdate xmlns:o="http://www.google.com/update2/request" version="GoogleTvEureka-0.1.0.0" updaterversion="GoogleTvEureka-0.1.0.0" protocol="2.0" ismachine="1">
<o:os version="3.0.8" platform="Linux" sp=""></o:os>
<o:app appid="{45ab3f62-be86-44be-9799-faa6a1229396}" version="12940" lang="en-US" track="stable-channel" board="eureka-b3"
hardware_class="">
<o:updatecheck targetversionprefix=""></o:updatecheck>
</o:app>
</o:gupdate>
The fields are pretty self-explanatory. If you use Linux, you can save the XML to a file called update2.req and make the request using the command
Code:
curl -s https://tools.google.com/service/update2 -d [PLAIN]@update2.req[/PLAIN] -H 'Content-Type: text/xml'
Note: build 13300 is rolling out slowly, so don't complain if you don't get the URL right away. It's entirely up to Google who gets it and who doesn't.
anyone gotten this yet and unpacked it to see what files have changes made to them?
Thank you! I wish I would have seen this sooner.
Now, with a little bit of python, I can automate the making of my rooted images
Ashcunak said:
anyone gotten this yet and unpacked it to see what files have changes made to them?
Click to expand...
Click to collapse
Here's the update if anyone wants it...
http://wreckage.johndenverschooloff....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip
dev-channel ota?
Any idea how to get the dev-channel update zip?
I tried changing to track="beta-channel" in the xml, but that doesnt help.
It seems like there should be atleast one zip file for the below channels
stable-channel
beta-channel
canary-channel
dev-channel
developer-channel
dogfood-channel
Also found this interesting link in the updater binary.
http://omaha.sandbox.google.com/service/update2
morchu said:
Any idea how to get the dev-channel update zip?
I tried changing to track="beta-channel" in the xml, but that doesnt help.
It seems like there should be atleast one zip file for the below channels
stable-channel
beta-channel
canary-channel
dev-channel
developer-channel
dogfood-channel
Also found this interesting link in the updater binary.
http://omaha.sandbox.google.com/service/update2
Click to expand...
Click to collapse
As far as I can tell, none of those channels (except for beta which seems to just be an alias for stable) are active for a stock device. I'm guessing that to receive updates from those channels, your device has to be configured to send its serial number, which also has to be whitelisted on Google's servers. If you want to send a request with a serial number, just add a line like
Code:
serial_num="XXXXXXXXXXXX"
after line 4 (<o:app ...) in the XML. Unless you have access to a development unit's serial number, I doubt it will do much good though.
I had requeseted for whitelisting my device some time back. But never got a response from google.
Can anybody who already had their device whitelisted try the download using your device serial number, and let me know if it works?
I dont think there is anything device specific in the dev-channel system image. So I wonder why that system image is not shared already?
tchebb said:
As far as I can tell, none of those channels (except for beta which seems to just be an alias for stable) are active for a stock device. I'm guessing that to receive updates from those channels, your device has to be configured to send its serial number, which also has to be whitelisted on Google's servers. If you want to send a request with a serial number, just add a line like
Code:
serial_num="XXXXXXXXXXXX"
after line 4 (<o:app ...) in the XML. Unless you have access to a development unit's serial number, I doubt it will do much good though.
Click to expand...
Click to collapse
Just to conclude, it seems like there is no more separate dev-channel firmware download. Emulated my whitelisted devices update request, and received the regular stable-channel update.
morchu said:
I had requeseted for whitelisting my device some time back. But never got a response from google.
Can anybody who already had their device whitelisted try the download using your device serial number, and let me know if it works?
I dont think there is anything device specific in the dev-channel system image. So I wonder why that system image is not shared already?
Click to expand...
Click to collapse
If you are on Windows, then use same XML update2.req file, as @tchebb on 1st post and download cURL for Windows here.
Then use following command, since Linux one is not working in Windows (just place update2.req file in same directory as curl.exe):
Code:
curl -k https://tools.google.com/service/update2 -d @update2.req -H "Content-Type: text/xml"
This thread is for FlashCast image developers ONLY. If you are not developing a FlashCast image, please do not post here. Post in the main thread instead.
Hello developers! I hope that this thread can serve as a place for you to ask any questions you may have about FlashCast development or internals, make feature requests, and report issues you're having. I will edit this post with FAQs as they come up. Until then, take a look at my documentation on GitHub, which contains documentation and sample code to help you create FlashCast mods.
tchebb said:
This thread is for FlashCast image developers ONLY. If you are not developing a FlashCast image, please do not post here. Post in the main thread instead.
Hello developers! I hope that this thread can serve as a place for you to ask any questions you may have about FlashCast development or internals, make feature requests, and report issues you're having. I will edit this post with FAQs as they come up. Until then, take a look at my flashcast-samples repository on GitHub, which contains documentation and sample code to help you create FlashCast mods.
Click to expand...
Click to collapse
So far its working great! Plan on releasing a rooted 13300 system image with this soon, but I was wondering, is there a possibility you could create a partition backup option? so like
Code:
backup_mtd_partition 'rootfs' 'system.img'
Where it will make a folder called backup on the jump drive, and store the rootfs file system with the name of system.img? also a md5 for each file would be nice. I know I could just have a script dd the mount point, but would be nice to see a function to call.
ddggttff3 said:
So far its working great! Plan on releasing a rooted 13300 system image with this soon, but I was wondering, is there a possibility you could create a partition backup option? so like
Code:
backup_mtd_partition 'rootfs' 'system.img'
Where it will make a folder called backup on the SD card, and store the rootfs file system with the name of system.img? also a md5 for each file would be nice. I know I could just have a script dd the mount point, but would be nice to see a function to call.
Click to expand...
Click to collapse
This would definitely be a useful feature. I can see a few implementation details that would need to be worked out in a non-obvious fashion, though:
There is currently no way for a imager script to directly access the root of the user partition. This is intended to prevent multiple scripts from having access to the same filesystem and possibly overwriting each others' files. Instead, scripts are executed in a temporary directory whose contents are discarded on device shutdown. It seems like the solution to this would be to create numbered backup directories, like there are numbered logs now, for mods to place their backups in.
It wouldn't be desirable for a mod to take a backup every time it was flashed, as not everyone cares about backups and they take up lots of space. There would need to be some way for the user to decide whether or not they wanted backups. Maybe another flag file?
Finally, taking a backup of an MTD partition using nanddump (dd should not be used to image NAND partitions, since it is not bad-block aware) images the entire partition, when (in the case of squashfs) only a small part actually has a filesystem on it. This means that a single rootfs backup will take up 400MB on the USB drive. I would want to implement something which can back up only the part of a partition which squashfs is using before I release backup functionality.
Obviously, this is a prime candidate for a new helper function, because of these non-trivial complications. I'll see if I can make the necessary changes to FlashCast and release backup functionality as part of v1.1. Thanks for the suggestion!
One more suggestion, if you do not mind.
How about the ability to flash multiple zips at once? So, if I have 2 files I want to flash, first one will stay eureka_image.zip, and then the next one would be eureka_image1.zip, or some similar process to allow multiple zips.
The issue here would be a naming scheme that would be easy for users to use and understand. so maybe if you flash a single file, just use eureka_image.zip, and if multiple, each would have a number added, starting from 1 and counting up in the order you want them flashed?
ddggttff3 said:
One more suggestion, if you do not mind.
How about the ability to flash multiple zips at once? So, if I have 2 files I want to flash, first one will stay eureka_image.zip, and then the next one would be eureka_image1.zip, or some similar process to allow multiple zips.
The issue here would be a naming scheme that would be easy for users to use and understand. so maybe if you flash a single file, just use eureka_image.zip, and if multiple, each would have a number added, starting from 1 and counting up in the order you want them flashed?
Click to expand...
Click to collapse
This is something I intend to implement. My current plan is to support a eureka_images directory, which can contain any combination of zipped and unzipped mods which will be flashed in alphabetical order. Mod authors can distribute their mods with a prefixed number, so, for example, you could distribute 00_13300_rooted.zip and 59_unlocator_dns.zip. I'll write a standard for how to determine the numbers (e.g. full system images get 00-09, major/minor filesystem changes get 40-49/50-59 respectively depending on how many files they affect, etc). It's not perfect and there can still be conflicts, but it should allow most mods to be flashed in a mostly sane order. I'm open to any suggestions or improvements you might have.
tchebb said:
This is something I intend to implement. My current plan is to support a eureka_images directory, which can contain any combination of zipped and unzipped mods which will be flashed in alphabetical order. Mod authors can distribute their mods with a prefixed number, so, for example, you could distribute 00_13300_rooted.zip and 59_unlocator_dns.zip. I'll write a standard for how to determine the numbers (e.g. full system images get 00-09, major/minor filesystem changes get 40-49/50-59 respectively depending on how many files they affect, etc). It's not perfect and there can still be conflicts, but it should allow most mods to be flashed in a mostly sane order. I'm open to any suggestions or improvements you might have.
Click to expand...
Click to collapse
Sounds great to me! Only other suggestion I have is to add another flag file which would allow Flashcast to continue flashing the multiple zips, even if one errors out.
So, by default if multiple zips are going to be flashed, and it errors on the first, it would stop, get a red LED, and then reboot.
with a flag file present, maybe ignore_errors, even if it errors out on the first zip, it would continue down the chain of zips until it finishes all of them.
Anyone got any idea how to get started with some themes for the chromecast? Will be more than happy to help, as soon i know where to start.
bormeth said:
Anyone got any idea how to get started with some themes for the chromecast? Will be more than happy to help, as soon i know where to start.
Click to expand...
Click to collapse
Most of the resources seem to be kept in the .pak files contained in /chrome. The first step to theming would be figuring out what format those are in and how to unpack and repack them. You might want to start by taking a look at the content_shell source code, as it might have some documentation or scripts for working with .pak files.
tchebb said:
Most of the resources seem to be kept in the .pak files contained in /chrome. The first step to theming would be figuring out what format those are in and how to unpack and repack them. You might want to start by taking a look at the content_shell source code, as it might have some documentation or scripts for working with .pak files.
Click to expand...
Click to collapse
Im gonna dive into it
Have a little bug report.
If a person has more then 85~MB in their eureka_image folder, and then they start a SquashFS File system edit, flashcast will report an error saying out of space. Now, here is the error part. Even though it failed to mount with an error, the imager.sh file will continue to run, and will then attempt to flash back a corrupt file, causing a non-bootable chromecast until the system partition is re-flashed.
bormeth said:
Anyone got any idea how to get started with some themes for the chromecast? Will be more than happy to help, as soon i know where to start.
Click to expand...
Click to collapse
The first script on THIS SITE will unpack the .PAK files, although it unpacks everything as a .png as it was made for a different Chromium device. So you would have to manually go rename all the files to their correct extension for the files, but because it expects everything to be a .png it won't pack back properly. The second script, technically should unpack/pack as proper file extensions, but I never got it to work right as I have little to no knowledge of Python.
The chromium source has a script,data_pack.py (which I can't link to since I'm a new user ATM) which can be used to pack and unpack .PAK files. The script posted above seems to be lifted from this source and modified to detect a few filetypes and write the unpacked files. But if you want to modify or add images and need to repack them, this script will help you figure it out. I'll work on adding and making some changes to the theme and give some instructions.
how to mount usb drive
Haven't used linux in years. Thanks!
Hey, want to do some poking around in the flashcast .bin file...how do I go about doing that? What is the file format, and is the image mountable in linux? Even better might be to extract files/folders from the image...what tool can I use to do that?
Ok, so I'm doing some dinking around...I've looked into buildroot, and I think for the most part I understand what is going on. I also tried building from source, and it appears to have worked. So, from this poking around I have a few assumptions I've made and a few questions. Correct me if I'm wrong anywhere but.......
Basically, you've built a generic bootloader for the device using buildroot. This is not related at all to the stock CC bootloader (although maybe you borrowed a few drivers, etc). I would guess that the buildroot bootloader has just what you need to display a picture on the TV and do some basic file system operations, and I would also guess that the buildroot bootloader is missing a few features that the stock bootloader has - therefore, it wouldn't be possible to run a full-fledged ROM off of this bootloader. Am I right so far? If so, what is missing from the buildroot bootloader? Libraries? Binaries? No idea?
Also, to access something like USB storage, the buildroot bootloader is able to include the required /dev devices, whereas it wouldn't be possible to include this on CC's stock bootloader without the source. So, doing something like accessing a ROM from an external flash drive isn't feasible because of these limitations? Basically, all that is possible with the current bootloader (of course, the insecure one which allows for unsigned code to run) is to add a few binaries to the stock CC ROM (things like adb, dropbear, etc), maybe add some access to those binaries through Web GUI, etc.
Am I on the right track? Is there anything you would add/correct? Thanks for the help. I'm trying to understand
tomg09 said:
Ok, so I'm doing some dinking around...I've looked into buildroot, and I think for the most part I understand what is going on. I also tried building from source, and it appears to have worked. So, from this poking around I have a few assumptions I've made and a few questions. Correct me if I'm wrong anywhere but.......
Basically, you've built a generic bootloader for the device using buildroot. This is not related at all to the stock CC bootloader (although maybe you borrowed a few drivers, etc). I would guess that the buildroot bootloader has just what you need to display a picture on the TV and do some basic file system operations, and I would also guess that the buildroot bootloader is missing a few features that the stock bootloader has - therefore, it wouldn't be possible to run a full-fledged ROM off of this bootloader. Am I right so far? If so, what is missing from the buildroot bootloader? Libraries? Binaries? No idea?
Also, to access something like USB storage, the buildroot bootloader is able to include the required /dev devices, whereas it wouldn't be possible to include this on CC's stock bootloader without the source. So, doing something like accessing a ROM from an external flash drive isn't feasible because of these limitations? Basically, all that is possible with the current bootloader (of course, the insecure one which allows for unsigned code to run) is to add a few binaries to the stock CC ROM (things like adb, dropbear, etc), maybe add some access to those binaries through Web GUI, etc.
Am I on the right track? Is there anything you would add/correct? Thanks for the help. I'm trying to understand
Click to expand...
Click to collapse
Buildroot does not let us build a bootloader, it lets us build a custom linux distribution that runs on the chromecast. The reason it is unable to do anything "graphical" minus the static image is due to licensing of the marvell GPU driver the chromecast uses. It is currently closed source, so it is unable to be compiled. We can use the blob from the stock OS, but ATM there is no need, and this can cause licensing issues.
Also, you can still access /dev and such on the stock OS. The big thing is the stock OS has usb input disabled at a kernel level, so it doesn't mount or detect any devices plugged in when the OS is running. This is circumvented though if you build and use your own custom kernel. For the features Eureka-ROM adds to the stock OS, we add those by using googles open source cross compiler for the device to build supported binaries.
Hmm...interesting. So, if I understand the booting process properly, upon power-on, a small bit of code called the bootloader is run, loading the kernel into memory (where, among other things, the graphics driver is located). From there, other components of the operating system are loaded on "top" of the kernel. So, it's not the bootloader that's rebuilt - but the kernel - with buildroot. Now, what sort of things would be possible if an open source alternative for the graphics driver were available (bear with me in the hypothetical), or even if one were to take the blob from the stock CC kernel? Turn CC into an android stick, complete with USB input device compatibility maybe?
Now on another note. I want to learn about cross-compiling. I am thinking of trying my hand at cross-compiling samba for the chromecast. Now if I understand the buildroot compiling process correctly, the right compiler for making chromecast-runnable binaries is compiled (or do you include it externally), and in theory, it should be possible to compile samba, right? I've been poking around the buildroot directory tree with the chromecast source superimposed over the top, and as of yet, I havent found the compiling binary (gcc, maybe?). I will look in a bit more depth. Once I find this, it should be as simple as specifying host and target architecture, putting the compiler for the CC in PATH, and compiling, right?
Thanks again for your help, and if you feel this isn't the appropriate place to post this, let me know.
tomg09 said:
Hmm...interesting. So, if I understand the booting process properly, upon power-on, a small bit of code called the bootloader is run, loading the kernel into memory (where, among other things, the graphics driver is located). From there, other components of the operating system are loaded on "top" of the kernel. So, it's not the bootloader that's rebuilt - but the kernel - with buildroot. Now, what sort of things would be possible if an open source alternative for the graphics driver were available (bear with me in the hypothetical), or even if one were to take the blob from the stock CC kernel? Turn CC into an android stick, complete with USB input device compatibility maybe?
Now on another note. I want to learn about cross-compiling. I am thinking of trying my hand at cross-compiling samba for the chromecast. Now if I understand the buildroot compiling process correctly, the right compiler for making chromecast-runnable binaries is compiled (or do you include it externally), and in theory, it should be possible to compile samba, right? I've been poking around the buildroot directory tree with the chromecast source superimposed over the top, and as of yet, I haven't found the compiling binary (gcc, maybe?). I will look in a bit more depth. Once I find this, it should be as simple as specifying host and target architecture, putting the compiler for the CC in PATH, and compiling, right?
Thanks again for your help, and if you feel this isn't the appropriate place to post this, let me know.
Click to expand...
Click to collapse
If we had a fully working open source graphics driver, lots could be accomplished. Full custom linux distributions could run x11 shells, we could have xbmc working with hardware decoding, and yes android would technically be possible if enough people wanted to put the time and effort into it. You can take the blob from the rom to do some of this, but things like hardware accelerated decoding will still not be possible due to the fact there is no documentation on how to use the blobs properly for things like that. (this is my understanding so I may be off on some small details, @tchebb can probably explain it more in depth.)
As for cross compiling, you just need to use googles prebuilt toolchain as the compile source.
Link: https://code.google.com/p/chromecast-mirrored-source/source/browse?repo=prebuilt
Mind if I ask why you want to compile samba? do you want to host media or files from a chromecast device? I actually have CIFS added to the eureka-kernel configs on our repo, so if you compile our kernel from source, you can mount samba shares on the chromecast device using the CLI.
ddggttff3 said:
As for cross compiling, you just need to use googles prebuilt toolchain as the compile source.
Link: https://code.google.com/p/chromecast-mirrored-source/source/browse?repo=prebuilt
Mind if I ask why you want to compile samba? do you want to host media or files from a chromecast device? I actually have CIFS added to the eureka-kernel configs on our repo, so if you compile our kernel from source, you can mount samba shares on the chromecast device using the CLI.
Click to expand...
Click to collapse
Cool. Thanks for the link. Basically, I'm just looking to learn about cross compiling for mobile devices. I figure samba seems easy enough. It was the first thing that came to mind. Any other ideas for something to cut my teeth on? Other binaries that would be well suited to CC, but are easy to compile?
tomg09 said:
Cool. Thanks for the link. Basically, I'm just looking to learn about cross compiling for mobile devices. I figure samba seems easy enough. It was the first thing that came to mind. Any other ideas for something to cut my teeth on? Other binaries that would be well suited to CC, but are easy to compile?
Click to expand...
Click to collapse
One more question...I've looked through the toolchain...the way it's set up is somewhat confusing. In the root directory of the toolchain: bin=gcc, g++, everything else I need to compile. What are the two folders entitled "arm-unknown-linux-gnueabi" and "target-arm-unknown-linux-gnueabi"? They seem to have relevant stuff (one has gcc, g++, etc except without the arm-unk... prefix, and other binaries which seem important). How do I use these/should I use these/why are they kept separate?
Thanks for the help.