On 02/12/2013 11:18 PM, Jaejyn Shin wrote:
I used my own codes.
There are many changed codes but the building was successed before
applying the seandroid codes.

My code is based on Jelly Bean, and I use Ubuntu 10.04.

Because I am using my customized code, I applied seandroid like below
procedures.

1. Downloading Android JB AOSP codes => code_1

When you downloaded AOSP, what branch/tag did you download? master, android-4.2.1_r1, or what?

2. Downloading Android JB AOSP codes with SEAndroid codes => code_2

Ditto for SE Android - seandroid, seandroid-4.2, or what?

3. Making diff file between code_1 and code_2. => seandroid.diff
   (I did it in order to file out the changing points of SEAndroid)

That's a fairly monolithic diff that may include changes unrelated to SE Android if you didn't use the same starting point. As master is constantly changing, you can't do that for master, only for a release tag.

4. Appling the seandroid.diff to my own android codes.

5. building


If This procedure is not correct, how can I apply SEAndroid to my
customized Android?

First, I would suggest just trying to download SE Android and building it as described on the wiki. Make sure that works before trying to port it over to your customized Android. Otherwise it is hard to tell the source of your errors.

For porting, what you describe might work if you are using a specific version, e.g. android-4.2.1_r1 of AOSP and seandroid-4.2 of our code, that shares a common baseline. It won't work for master because that is constantly changing so the diff may include unrelated changes. But if it were me, I would port it by extracting the changes from each project and applying them on a project-by-project basis rather than creating a monolithic diff. The wiki provides some notes on how to generate such changes under Git Trees and Branches.


--
This message was distributed to subscribers of the seandroid-list mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe seandroid-list" without quotes as the message.

Reply via email to