Forum having major issues -- I tried to post this earlier -- hope it goes this time...
Quote:
Originally Posted by m_reyna_16
ive been trying to figure out how to use this type of kitchen...so then in order to have something cooked in you just place it in the OEM folder, open the kitchen (there wont be any option to select?) and then just cook the rom and it will be cooked just like that?
|
In a nutshell, yes. When you run the main batch file it is all automatic -- there are no options to adjust. If you don't have things prepared correctly you can get *some* useful feedback while watching it cook such as YELLOW warnings about files being overwritten (more on that below), but mostly you will not know what you may have done wrong until you flash it and see.
Anything within a subfolder of \OEM such as \OEM\MyProgramToCookIn\ will be 'included' by the kitchen when it runs. After the base (ROM/SYS) it processes OEMs, and then EXTs -- in that order -- which means that anything you add to \OEM which already has a corresponding file somewhere in \EXT will get overwritten by that EXT etc., so watch as the kitchen cooks for YELLOW warning messages and take note so you can resolve any version conflicts and so on.
Many other cook's OEMs can simply be dropped (the whole folder) into \OEM and as long as there is no file named _skip within them, the kitchen will try and include them. There are various other reasons why an OEM might not work right even if included, but this post is getting long already and there is a bit more to cover...
Quote:
|
Originally Posted by philliyxx
My kitchen is crashing if I try to place calkulin's apps in dcd's oem folder... maybe I am noob and doing it wrong. I tried just dragging and dropping google maps into the oem folder=crash and then into the oemapp folder=crash...
|
I am using the OEM of Google Maps 3.2.0 from Calkulin's last kitchen (8/21) and it works fine. The only things I changed are the folder the shortcut goes to within initflashfiles (you do
not need to do this), and I deleted option.xml (see below). Could you elaborate on 'crash' a bit? Try hitting pause/break on your keyboard while the kitchen is displaying any errors you might see flying by if they aren't normally around long enough to write down. You can drop the 'Navigation - Google Maps 3.2.0' folder in \OEM and it should work (you can also rename it if you like). The OEMAPP folder is basically its own OEM, it just has a confusingly similar name to the OEM root. Don't put anything else in that one, or OEMDrivers, or OEM_Lang_0409.
I do remove the option.xml files (which are for certain kitchens) from any OEMs that contain them, as they are not used by DCD's kitchen, but I don't think that it's required. It certainly doesn't crash the kitchen -- I have occasionally left them in by accident and the OEMs still processed without error as far as I could tell.