Is there a way to add the DCD kitchen into the PPCgeeks BuildOS? - Page 2

**gguruusa** · #1 (**permalink**) 08-08-2008, 07:19 PM

Quote:

Originally Posted by azclown

Why not the other way around, I find it's easier to drop the OEM into DCD's kitchen and edit the options.xml and remove the ppckitchen extras....

Because that doesn't work so well for some OEMs as of the last couple of releases. Those OEMs WILL NOT build properly with any other buildos. This will become more and more common, moving forward.

Quote:

Originally Posted by azclown

I have ported DCD to the ppckitchen and it was not as easy, but can be done.....

Can't imagine what trouble you had. It should be practically trivial...a lot easier than the other way around. Perhaps you are trying to hard?

There isn't a manual (though I've seen posts tailored to integrating DCD's kitchen) because one really isn't needed. What exactly did you guys try to do?

ajm144k · #2 (**permalink**) 08-08-2008, 04:19 PM

How about the Oemizer output OEM? it was my first go around with oemizer and i put my oem folder into the "OEM" folder for dcds kitchen. i expected it to come up as a selectable option with all those other thigns but it didnt....

does it just automatically get built in then?

**gguruusa** · #3 (**permalink**) 08-08-2008, 07:42 PM

Quote:

Originally Posted by ajm144k

How about the Oemizer output OEM? it was my first go around with oemizer and i put my oem folder into the "OEM" folder for dcds kitchen. i expected it to come up as a selectable option with all those other thigns but it didnt....

does it just automatically get built in then?

If it doesn't have an option.xml, yes.

PapstDFrisco · #4 (**permalink**) 08-08-2008, 04:27 PM

After dealing with the kitchens and the like, GC14 recommended simplifying the kitchen process to doing the base DCD build and using UC script to install the cabs of what you want to add. This seems to work very well in most cases/applications/programs. Then if you don't want a program remove it and install its replacement. Of course if you find stuff that you are always using you can add the oem to the build.

This takes a lot of variables out of the loop. Helps to keep is simple.

Click on the UC link on DCD's rom pages to learn about UC customization. It's fairly easy to do.

**gguruusa** · #5 (**permalink**) 08-08-2008, 07:30 PM

Quote:

Originally Posted by PapstDFrisco

After dealing with the kitchens and the like, GC14 recommended simplifying the kitchen process to doing the base DCD build and using UC script to install the cabs of what you want to add. This seems to work very well in most cases/applications/programs. Then if you don't want a program remove it and install its replacement. Of course if you find stuff that you are always using you can add the oem to the build.

This takes a lot of variables out of the loop. Helps to keep is simple.

As an alternative, you can also use nuepackage to install oems after the fact. I hear it doesn't work with everything (can't imagine why), but sometimes its easier than searching for a .cab.

miguelfp1 · #6 (**permalink**) 08-08-2008, 04:30 PM

I personally like more the eye candy in the PPCKitchen, plus, there's something I can do from the PPCKitchen that I can't do in dcd's kitchen, change the Windows Mobile splash screen (stupid reason, I know). Nonetheless, I go back and forth between PPCKitchen and dcd's. Anyways, say I wanted a bit of a weekend project trying to adapt dcd's kitchen base to the PPCKitchen BuildOS, is there a walkthrough or instructions? Last time I tried, I got it packaged in the proper locations (or so I think) but couldn't get it to build...

ajm144k · #7 (**permalink**) 08-08-2008, 04:39 PM

Quote:

Originally Posted by PapstDFrisco

After dealing with the kitchens and the like, GC14 recommended simplifying the kitchen process to doing the base DCD build and using UC script to install the cabs of what you want to add. This seems to work very well in most cases/applications/programs. Then if you don't want a program remove it and install its replacement. Of course if you find stuff that you are always using you can add the oem to the build.

This takes a lot of variables out of the loop. Helps to keep is simple.

Click on the UC link on DCD's rom pages to learn about UC customization. It's fairly easy to do.

not so much in my opinion. if you really use UC and flash any rom other than dcd you are going to have to change some things out of your sdconfig. for instance, the carrier cab might cause problems if you run the same UC for a dcd from on a nuerom. UC is helpful to make the changes that can be rom specific. but what if your mms needs won't function without an arcsoft install on dcd, but on a nuerom it doesnt need that install? more changes.

i figured the best route would be to make a UC with a rom specific sdconfig and then make an oem using the oemizer that i should be able to put on every rom i flash. (hopefully)

...but since i just started using the oemizer, i could use help on where to put my finished oem for DCDs kitchen??