PPCGeeks - Create oem packages

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- HTC Apache Development (http://forum.ppcgeeks.com/forumdisplay.php?f=53)

- - Create oem packages (http://forum.ppcgeeks.com/showthread.php?t=13027)

Create oem packages

I'm sorry if this has already been addressed (i'm certain it has)....but I cannot find it anywhere. I need to be directed in the area where you learn how to create oems...if there is anyone who can help me out it would be greatly appreciated...thanks

Quote:

Originally Posted by cheeb (Post 135491)

If you are using the kitchen, you can find the instructions in the "PPCGeeks Kitchen Tutorial" located in the kitchen folder here:
"\BuildOS\Help & Support Files\Apache Kitchen Walkthrough r1.0.pdf"

Quote:

Originally Posted by bobonit (Post 135513)

If you are using the kitchen, you can find the instructions in the "PPCGeeks Kitchen Tutorial" located in the kitchen folder here:
"\BuildOS\Help & Support Files\Apache Kitchen Walkthrough r1.0.pdf"

Anyone know if that document will be updated for the latest kitchen since there are new features you can add into option.xml?

Probably not as the guys who created this kitchen, by their own admission, don't like doing documentation all that much. They have, however, stated that if anyone wanted to do an updated document then they'd be more than happy to include it! Wanna take it on?

Here's a quick overview of the new info you can add to option.xml added by GGuruUSA.

Code:

<OEMVersion>1.0</OEMVersion>

This is used to show the version or revision of the OEM. If you're going to keep the same AppVersion, you'll want to change this each time you make a change.

Code:

<OEMDate>10/23/2007</OEMDate>

This is the last date you modified the OEM.

Code:

<ButtonType>GroupRadioNone</ButtonType>

This is how you would like your list item to "act" in buildOS. It has 5 possible types:

Hidden doesn't show on the list. Used for hidden requirements only.
NoButton shows up with no button.
Check shows up as a normal old checkbox.
GroupRadioNone shows up as a radio button, but none of the "GroupRadioNone" items in that OEM group must be selected. They can be "unchecked".
GroupRadioOne shows up as a radio button and one of the "GroupRadioOne" items in that OEM group must be selected.

Code:

<OEMAuthor>YourName</OEMAuthor>

This is used to give yourself credit for the OEM you're creating.

Code:

<AppVersion>2.0</AppVersion>

This shows the versions of the application itself. For example if your OEM contains Slide2Unlock 0.85, then it would be 0.85.

Code:

<AppAuthorURL>http://www.somesite.com</AppAuthorURL>

This is used to give the original application's author credit. It should link to either the application author's homepage, the application's homepage, or a decent thread or page with info about the application.

Code:

<AdditionalInfo>A bunch of info can go in here that you would like people to know about the OEM or application.

It can be single or multi-line.</AdditionalInfo>

Code:

    <Exclude>331439cf-a636-4243-8424-e501be3a39d2</Exclude>

    <Exclude>3dca3381-3564-4380-8f56-05ccbe08d080</Exclude>

    <Exclude>6226602c-2ba3-40bf-83e4-ea9173088ac9</Exclude>

    <Exclude>1d9a869a-f37e-479b-adc7-dc128ebcf707</Exclude>

    <Require>612345cd-2ba3-40bf-83e4-ea9173088ac9</Require>

Now this is really cool... You can add requirements and exclude other OEMs:
This example comes from the split version of Microsoft Office Mobile.
The Exclude lines tell buildOS that this OEM is not compatible with the old Office version and to exclude it if it's checked already on the list.
The Require line tells it to include some shared Office components that it will need which are included in a hidden OEM.

The easy way is to put a cab into Tiermann's OEMiser and turn it into an OEM!

Quote:

Originally Posted by Wizzard (Post 135859)

The easy way is to put a cab into Tiermann's OEMiser and turn it into an OEM!

Hehe.. yeah. That'll get it done, but always good to learn the idea behind it for when things go wrong.
We're working on some actual documentation now, btw. Not sure when, but we'll have some more modernized info available eventually.
I'm almost done with OEMizer's help file and I'm sure we'll all be having fun adding to the pdf, hehe.

thanks alot for all the answers...much appreciated