yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
Git is content based, not name based. So it will just go to the repos and see if it has the objects. Any code that is shared between the two projects (i.e. mateorod and CyanogenMod. Which believe me, is a BUNCH of common code) will be registered as present and it will move on. Aftewards, when it checks out the files and syncs the work tree, it will delete any obsolete paths.

The upside of this is that it takes way less time. And you will keep the CM source as well. So when (hopefully) the Nook gets promoted to an Official device, you can just repo init right over it again.

I have bunches of different devices, all layered on top of each other this way. And I mean bunches. I build for aokp, pa, aosp and cm on an almost nightly basis. I have some of them separated into different repos for practical reasons, but thats it.

I also keep the different flavors on top of each other. So if I need ICS, I do a quick init of ics and then I can build. Same with Gingerbread.

It will come with the cost of a minimal amount of storage space, but really the only thing that is flat out doesn't exist is the vendor/pa. Now it may take a little time still, because if you synced from CM, you still don't have the kernel or the device.
[Nook Color Android Development] davidr415:
More problems...

After the lunch command, I get the message that dependencies not found, bailing out.. which I undestand is not uncommon.

When I did the make bacon I got the following:

david@david-VirtualBox:~$ make bacon

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.1.2

TARGET_PRODUCT=pa_encore

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.2.0-32-generic-x86_64-with-Ubuntu-12.04-precise

HOST_BUILD_TYPE=release

BUILD_ID=JZO54K

OUT_DIR=/home/david/out

============================================

build/core/base_rules.mk:171: *** android/system/abi/cpp: MODULE.TARGET.SHARED_LIBRARIES.libgabi++ already defined by abi/cpp. Stop.

david@david-VirtualBox:~$

What now?
[Nook Color Android Development] mateorod:
I would say that is an unintended consequence of the double repo init. Sorry, it is unlikely but does happen.

Just go into your tree, find the android directory, trash it, repo init and resync. Should take five minutes combined and hopefully all will be well.
[Nook Color Android Development] davidr415:
OK.. I did all that. When I ran make bacon I got:

find: `frameworks/base/core/java/android': No such file or directory

find: `frameworks/base/graphics/java/android': No such file or directory

find: `frameworks/base/location/java/android': No such file or directory

find: `frameworks/base/media/java/android': No such file or directory

find: `frameworks/base/media/mca/effect/java/android': No such file or directory

find: `frameworks/base/media/mca/filterfw/java/android': No such file or directory

find: `frameworks/base/media/mca/filterpacks/java/android': No such file or directory

find: `frameworks/base/drm/java/android': No such file or directory

find: `frameworks/base/opengl/java/android': No such file or directory

find: `frameworks/base/opengl/java/javax/microedition/khronos': No such file or directory

find: `frameworks/base/sax/java/android': No such file or directory

find: `frameworks/base/telephony/java/android': No such file or directory

find: `frameworks/base/wifi/java/android': No such file or directory

find: `frameworks/base/keystore/java/android': No such file or directory

find: `frameworks/base/icu4j/java/android': No such file or directory

find: `frameworks/base/voip/java/android': No such file or directory

find: `frameworks/base/core/java/android': No such file or directory

find: `frameworks/base/graphics/java/android': No such file or directory

find: `frameworks/base/location/java/android': No such file or directory

find: `frameworks/base/media/java/android': No such file or directory

find: `frameworks/base/media/mca/effect/java/android': No such file or directory

find: `frameworks/base/media/mca/filterfw/java/android': No such file or directory

find: `frameworks/base/media/mca/filterpacks/java/android': No such file or directory

find: `frameworks/base/drm/java/android': No such file or directory

find: `frameworks/base/opengl/java/android': No such file or directory

find: `frameworks/base/opengl/java/javax/microedition/khronos': No such file or directory

find: `frameworks/base/sax/java/android': No such file or directory

find: `frameworks/base/telephony/java/android': No such file or directory

find: `frameworks/base/wifi/java/android': No such file or directory

find: `frameworks/base/keystore/java/android': No such file or directory

find: `frameworks/base/icu4j/java/android': No such file or directory

find: `frameworks/base/voip/java/android': No such file or directory

find: `src': No such file or directory

build/core/base_rules.mk:171: *** abi/cpp: MODULE.TARGET.SHARED_LIBRARIES.libgabi++ already defined by .local/share/Trash/files/android/system/abi/cpp. Stop.

david@david-VirtualBox:~$

Any thoughts?

---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------

[/COLOR]sorry.. I mean make bacon.. not lunch
[Nook Color Android Development] mateorod:
Well, something is messed up in your source. It doesn 't have anything to do with the double repo init, those files are needed in both projects and are identical in each.

Those framework files are the files that end up comprising the framework2.jar, That was my patch that ended up moving those VOIP files to framework2, I am intimately acquainted with that process, since I struggled with it so much.

You could try and debug, or you could start fresh. But you are missing files that are needed for jellybean, certainly. You could try another repo sync, it is possible that you haven't pulled down all the files yet. But I don't know why you are missing those files.
[Nook Color Android Development] davidr415:
I tried another repo sync ... lunch ... make bacon and got the same result.

When you say "start fresh".. what does that mean.. how far back in the processs do I need to go.. or what do I need to remove, etc..

Thanks so much for the help. I had done am earlier PA JB build that went very smooth and worked fine. I had some sort of a "melt down" in my xubuntu VB and had to reinstall it along with java and android.. this is first build attempt since then.
[Nook Color Android Development] mateorod:
Well, I just had to nuke my source as well. This isn't your fault (or mine either) but it looks like there is some sort of problem with one of the latest 'repo' that just got released. I couldn't repo sync really at all. Someone in the dev thread said they fixed it by updating git-core, but that didn't do it for me.

My guess is that you pulled down a bad repo as well. You might be able to debug it without removing all of the objects you've already pulled down, but I don't know how personally. Deleting your .repo folder and starting again may just be the easiest way.

press ctrl-h to see hidden folders if you are going to delete through the file explorer.

What a hassle
[Nook Color Android Development] WJThomas:
I've had an issue with building for several days now. It wasn't much of a concern, as I figured that it would smooth itself out. With the progress on the CM10 Alpha, I tought I would try to build again, but I still get the same error.

I've tried clobber, I've tried deleting everything and stating over; but the issue persists.

I tried deleting just the system/core/libion directory and repo sync. This appears to work, but I still see find issue the message about 'src'. The build is progressing, so it may be OK. If the build finishes OK, and I don't see anything posted, I'll try to flash and see what happens.
[Nook Color Android Development] mateorod:
The src warning is normal.

See, the problem we're having here is that I switched from fat-tire's device repo to NookieDevs. I saw that they were working on some improvements that weren't being committed to fattire's repo. So I switched. I didn't realize how aggressive they were being in that project, and that commits to it frequently leave it unbuildable (as is).

(One of)The problem(s) we're having here is that I switched from fat-tire's device repo to NookieDevs. I saw that they were working on some improvements that weren't being committed to fattire's repo. So I switched. I didn't realize how aggressive they were being in that project, and that commits to it frequently leave it unbuildable (as is).

Thanks for the reports, I am gonna work on this source some tonight. I have to fix some color codes in vendor for things like the new nav bar and whatnot, and while I am there I will run checks on the projects and see how they are building.

Really, I was just trying to incorporate krylon's work on video, but then unknown_world posted a manifest, and steven posted a defconfig and now we're all over the place, you know?

I will stabilize the repo tonight and run a build while I am sleeping and will report back when it is stable. Sorry for the confusion, I actually held off on switching to the NookieDevs until they reported it building and stable. It just descended back into instability right afterwards.

Edit/Update: I switched our device back to fat-tire. I almost went with steven676's kernel, but decided to wait for keyodi. I have been using his kernels for almost a year. There is no real reason to get antsy and switch at the last moment.

Besides, fat-tire's repo will remain stable. We can switch to the NookieDevs project when it stabilizes for good.

Builders- back at it. I will be editing stuff perodically over the next 48 hours, so if you get a build error, repo sync and then make bacon again. If you get the same error, report back. That process does NOT require you to start all the way over, so don't worry about that. It will just pick up any new changes rebuild anything they apply to, and then pick back up where it left off.
[Nook Color Android Development] WJThomas:
No problem, take your time. I know you have been busy with AP.

I'll just take a look at unknown_world's build for a bit.
[Nook Color Android Development] mateorod:
Sorry, meant to post this yesterday, but the build system is in a buildable state- I will maintain it as such. When I saw they were only commiting to NookieDevs, I moved over which I regret to a degree.

Note that if you try and mix in some of the other branches that are floating around, you may (more likely will have problems).

We're back on fat-tire's device repo and keyodi's kernel. That device branch doesn't have the ti-connectivity stuff in firmware that steven676, unknown_world and krylon have been working with and will be needed by their kernels. That will give you the immediate errors as it tries and copies over the necessary binaries if you try and use those kernels with the wrong device repo.

Basically, the point is that should you want to try and build those latest (and as we saw sometimes unstable) changes, make sure you change all the relevant projects and delete any local_manifest.xml that may be lurking in your .repo folders.

Or, just sync and run exactly as described in the third post. I am working on some of the preferences/overlays for our device, managing the toggles and color codes and that sort of thing, but that won't get checked in until probably tomorrow night and those are semi-superficial things that hopefully won't break anything.

I am going to keep an eye on keyodi's kernel repo. There will be some theoretical sweet spot, where he starts checking in the video stuff and then we'll need to switch back to the NookieDevs device.

This kind of crap is why they tried to hard to keep things to one manifest. But that went to hell and there is probably no cramming the genie back in the bottle. I will attempt to keep us as clean as possible going forward. We never left the official repos, btw, but even then playing catch up broke things for awhile.

Thanks for playing...xD
[Nook Color Android Development] eyeballer:
At this point all the nookiedevs repos are up to date and absolutely buildable. There may be some lag time between the device/kernel repos as updates are pushed (results in unbuildable states for short periods) but the nookiedevs ones should be considered most stable at this point. We're using keyodi's (and sometimes sluo's) repos for staging kernel changes which may or may not be stable.

tl:dr go back to the nookiedevs stuff :)
[Nook Color Android Development] leapinlar:
I've finally given up on CM10 for now and gone back to PA 1.6. I loved it but too many SODs on my old Nook. Will wait till that is solved. PA is perfect.
[Nook Color Android Development] mateorod:
Is this your first compile? When did you pull the source?

Those errors have been floating around the last week or so, but I am pretty sure I weeded those projects out of our manifest.

If you pulled the source sometime before yesterday, delete the out/target/product/encore/obj/SHARED_LIBRARIES/libOMX.TI.Video.Decoder_intermediates folder, repo sync and make bacon again.

If you really want to make sure, repo sync, make clobber and build

anndd shoot. Found it. This is related to their commits to vendor (the proprietary files). I had pulled them from my device locally and wasn't personally pulling them from the repo. So I didn't personally incorporate this change into my tree.

Dang it. Okay folks. There is no choice but to go with the flow. I really, really wanted to wait until these commits went to...a more stable tree I guess. I was hoping to shield us from the hoops that have been necessary to build the dev branch at times.

Lots of people with write capability, so the manifests keep getting shuffled. Which is cool, I mean they are doing some great work, making it easy for us to manage our manifest is likely really low on their list of priorities.

/ takes 15 minutes

Okay, we're back on NookieDevs and sluo's kernel. I would have liked to stay on keyodi's kernel, but I haven't followed the OMX stuff closely enough to know how many of the device changes need the more current commits in sluo's kernel. So we're going all the way...repo sync is being checked but it should go through. So delete that folder still, repo sync and try to make bacon again. Hopefully we can avoid you having to clobber, but is you still get errors, that would be the next step.

Sorry for the confusion...

Edit2: Eyeballer and I cross-posted, I guess. The tl;dr version- Did as he suggested already, so as he says, it should be buildable. Let us know, I won't be able to test this source until later tonight.
[Nook Color Android Development] eyeballer:
The current manifest which points to the device/kernel on nookiedevs and the prop files on my github is correct. You can't pull props because they have been updated since cm9 and even alpha1.

The best move right now is to use our published manifest in the alpha thread since that should be the most up to date and stable (this was our attempt to make it simpler for everyone - although again, at any given time things could still be in flux there too). If you hit a build error with the nookiedevs repos, I'd suggest just waiting a little bit and checking for new commits then re-syncing and rebuilding.

The other thing to try is to rm -rf device/bn/encore, kernel/bn/encore and vendor/bn/encore then re-sync to ensure you dumped all the old stuff.
[Nook Color Android Development] mateorod:
Well, wait. Krylon has a posted manifest that pulls from sluo's kernel. Is that what you mean? The latest posted manifest in dev that I know about is unknown_worlds.

Right now I have mimiced krylon's suggestions. are you suggesting going back to keyodi's?

edit: I have been updating my extract-files, I ust hadn't updated it in maybe two weeks. [Which I was doing because before I put together the sources for everybody, the PA repos are set up by default to pull proprietary files from a designated repo. Earlier in the thread, you will see my first builder and I struggling with getting an old prop repo out of his pull. I had removed it, but it was hiding in his local_manifest.

which is a long way of explaining I was not doing the extract-files thing because it is 'better' just because I had set it up as a test-case and kept doing it. Pulling from the repo, which all builds of PA do, is by far the best procedure.]

Edit2: Okay. I see. The one from the release thread, I guess. Okay, I will commit again.
[Nook Color Android Development] eyeballer:
This is the one to use: http://pastebin.com/vZFKdc8m

You will still see commits pushing to sluo/keyodi but those are usually us testing and not considered stable, we'll push things up to nookiedevs once we're confident-ish that it's stable.
[Nook Color Android Development] mateorod:
Okay. Completely on NookieDev. I don't know if anyone can even tell, but my only goal was to stay with the official repos in the first place. I switched from fat-tire to NookieDevs when I saw fat-tire was no longer pulling the commits. I didn't realize that keyodi's kernel was going the same way.

Thanks eyeballer. Hopefully we're set. Any build errors can and should still be reported here only guys, thanks for continuing that...
[Nook Color Android Development] anapospastos:
@mateorod

You made a mistake when you changed repos. Revision of nookiedevs kernel is "encore-omap3-3" not "encore-omap3-3-dsscomp".
[Nook Color Android Development] mateorod:
Thanks. Hold over from krylon's manifest, using sluo's kernel branches. The whole situation is making me crazy....thanks for the heads up, it's fixed.
[Nook Color Android Development] davidr415:
materod,

You and I exchanged some posts a few days ago about some bad builds that I was getting. To start over do I just need to do a make clobber? or a make clean? or something else?
[Nook Color Android Development] mateorod:
Well, make clobber is the surest way, although perhaps not the fastest.

If you just want to set it to build and then get it tomorrow, I would recommend that.

If you are going to be available to interact with it, you can repo sync, and if it complains, you delete the intermediate files by hand whenever you hit a complaint.

The repo wasn't working because I switched to NookieDevs device w/o switching the NookieDevs kernel. I wasn't able to test a clobber build because I was in the middle of a huge Auto-Patcher update and needed the ram. But eyeballer came by this morning and pointed me to the correct repos, so it should be essentially the new beta, but with our frameworks on top.

I am going to build from a clobber myself tonight, so that tomorrow I can begin checking in the more advanced device preference stuff that came down with PA 2.5+. So anyone putting together a build over the next 30 hours or so will only have to update their frameworks when they build next to have the very latest, encore optimized, PA. Which takes minutes after a full build as opposed to hours.
[Nook Color Android Development] grayfoxmg1:
Though this isn't the thread I am posting this to inform everyone and anyone who is interested, that the CM10 Beta 1 has been released by fattire. The BIGGEST thing for this build is that, in addition to some stability updates, Netflix is working. So though I am a HUGE fan of the Paranoid Android port that mateorod, eyeballer, et. all have made, I also believe that everyone should try different builds for themselves to see what they like best. I know most of you are probably subscribed to both threads, however I know that there are atleast a few of you that are not. So this post is for your benefit.

Now for something more relevant, @mateorod have you heard of the 'Pac-Man' ROM? XDA TV host Jordan talked about it, it is supposedly a build(I forget for which device) that cherry picks the best from Cyanogen Mod, AOKP, Paranoid Android, and AOSP to make a ROM with the best features possible for that device. Now while when something is the 'best' is subjective, this build got me thinking, how hard is it to integrate features from another platform(for want of a better word) into another? is it fairly easy if it is based on the same release of android (GB, ICS, JB)? Say for example, the new CM10 Beta supports an older copy of Netflix, can we pull there code and than support Netflix? If so is it a straight transition, or is there a lot of editing involved?
[Nook Color Android Development] mateorod:
I don't know much about PacMan, outside of the users who come through the Auto-Patcher thread with it. I have worked a little bit with agrabren, who is a Nvidia tech and puts out Disarmed Toaster (for the Evo 3D, I think?) and he does something like that as well.

But we don't really have a need for this. PA, just about anywhere, on a device level, is just a framework shell around CM10. So I would think that any porting of PA features would be something that was done on top of the AOKP or maybe AOSP sources.

I have been meaning to look into these things a little more closely, mostly because sooner or later some more of the developers are likely to want to incorporate the intermediate step of working with the auto-patcher, at minimum using our patches if not the functions as well.

But let me say this load and clear: we are completely using the CM10 teams work here. So anything that the new beta can do, we will do. But the only reason that PA exists at all is because those guys put their time into the CM10 build. All that is happening in this thread is a general organizing of other people's work. Which is ROM building in a nutshell, in many cases. But in our CM10 team's case, they have worked long hours putting their build together and we are the beneficiaries of that.

Which is one of the reasons I have maintained the no zip policy around here. They deserve the kudos and the development is still on-going. So the more testers they get, the better PA will be, by proxy. I put the sources up to encourage more people to build as well as perhaps inspire some people to give troubleshooting a shot, when and if troubles arise.

I will take a closer look at PacMan, though greyfox, so thanks for the tip...
[Nook Color Android Development] grayfoxmg1:
I understand that we exist at the whims of the CM team over in the other thread, it was just something that was in my mind and I only used Netflix as an example as I figured we would get that, sorry if I came off as sounding ungrateful to the CM10 team, you know that, that isn't the case with me.
[Nook Color Android Development] mateorod:
Oh, no I was just using your comment as another chance to shout them out. You have been around forever, you know what's up. I am Looking at the pacman rom right now.
[Nook Color Android Development] grayfoxmg1:
not really forever, I'm only 20, but yeah check it out, I don't know any specifics of it but when I heard it's description on XDA TV it sounded like it was the end result of all android work. So i figured it was worth mentioning, even if we(read you and the other builders) can't really integrate anything from it or in the same way, it should still be a really good framework for a future direction for ROMs on our Nook Colors, because lets face it. Our Nooks are old in comparison to other android tablets, we will eventually plateau and I am fearful that JB might be it, so we should do everything possible to make our Nooks appealing not just to ourselves, but other people who want cheap and efficient tablets.
[Nook Color Android Development] davidstre:
is this thread some kind of joke?

i have spent the last 4 hours reading through every post and can still not get past boot loops. i have flashed every build in all of the specified orders.

this must be a joke, no conclusive download instructions, no functioning builds...this is xda.

come on.

waste of time.
[Nook Color Android Development] kcls:
Calm down man. A few pages back they were saying the JB Builds are a WIP. We still don't even have a stable CM10 build and this is infinitely more complex. It'll come in time, have patience :)

Tapatalk² from my Optimus V