I looked into the ADW Launcher donut version,
It simply change SearchManager.SOURCE to source.
On Apr 13, 3:11 pm, Moose coatedmo...@gmail.com wrote:
Deleting the gen folder in the application's directory should clear up the
duplicate class errors. Not sure about the SearchManager.SOURCE
I looked into the ADW Launcher donut versio.
It simply changes SearchManager.SOURCE to string source.
On Apr 13, 3:11 pm, Moose coatedmo...@gmail.com wrote:
Deleting the gen folder in the application's directory should clear up the
duplicate class errors. Not sure about the
I just commented out the line. It didn't make a difference as far as I can
tell. I may go back and change it though.
On Apr 20, 2011 10:42 PM, Edison edison1...@gmail.com wrote:
I looked into the ADW Launcher donut version,
It simply change SearchManager.SOURCE to source.
On Apr 13, 3:11 pm,
Deleting the gen folder in the application's directory should clear up the
duplicate class errors. Not sure about the SearchManager.SOURCE though.
Looks like it doesn't exist...
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to
Thanks for that suggestion. I downloaded and compiled Cyanogenmod's tree and
it compiled the first time no problem. Now when compiling the application I
am trying to test and modify (ADWLauncher), I get the following errors
And actually, those errors are the same as the ones I was getting when
compiling the AOSP. It could be the problem with it was just the additional
package it was trying to build that had an error. I will try compiling the
AOSP version without the problematic package and see if it makes a
Did you install all the packages required from:
http://source.android.com/source/initializing.html
I'm able to build error free from the latest repo synced source.
I routinely use make -j8 on a 6 core AMD phenom box and only
see errors I introduce. :)
Have you run x86memtest? This build will
Yes, I did install all of the items from that website. (That is the tutorial
I used to set it up initially). There error with make -j4 seams to have
fixed itself - whether it was downloading a fresh repo or installing the
extra libraries or both, I don't know
I left it running before I hit the
I have seen builds break due to using the -j switch. Sometimes the Android
build system is very finicky. There's so many factors involved it's nuts, so
your errors could be due to the product your building, a missing dependency,
etc. Only thing really to do is read the error messages and try to
9 matches
Mail list logo
