Thank you, sir for the helpful reply.  It was my own misunderstanding of your 
19 August post to Richard Haines that caused me to believe in error that they 
weren't updated for 4.3. After re-reading your prior message and this reply, I 
now understand that they are and have always been 4.3-based and you were only 
discussing the question of if and how they might be folded in as opposed to 
remaining separate feature branches.

Cloning AOSP's master branch now. Thanks again for the remedial help and 
apologies for increasing tedium levels. Hope to contribute something 
interesting soon...

Paul





----- Original Message -----
From: Stephen Smalley [mailto:[email protected]]
Sent: Monday, September 09, 2013 09:06 AM
To: RATAZZI, EDWARD P DR-04 USAF AFMC AFRL/AFRL/RIGA
Cc: [email protected] <[email protected]>
Subject: Re: Trouble Building intent_mac on seandroid-4.2

On 09/08/2013 09:15 PM, RATAZZI, EDWARD P DR-04 USAF AFMC AFRL/AFRL/RIGA
wrote:
> Greetings,
> 
> Earlier in 2013, when 4.2 was on master, I successfully built intent_mac
> on top of the then-master AOSP and seandroid branches.  Now, I'd like to
> build a new, clean installation, but have read that intent_mac (and the
> other experimental MMACs) have not been moved to 4.3 yet.  So, I
> proceeded to clone android-4.2.2_r1.2 and seandroid-4.2, and
> successfully built the base SE system for the emulator (full-eng).
> 
> However, when I clone the intent_mac branch onto the above, the build no
> longer works, resulting in the following error almost right off the bat:
> 
> make: *** No rule to make target `prebuilts/sdk/api/.txt', needed by
> `out/target/common/obj/PACKAGING/checkapi-last-timestamp'.  Stop.
> 
> Curiously, after syncing intent_mac, my PLATFORM string changes to
> 4.3.2.1, where it was at 4.2.2 for the emulator build before cloning
> intent_mac.  Have these branches been moved to 4.3, and now no longer
> functioning with 4.2 and prior?  Or am I just doing something else wrong?

intent_mac and cp_mac track master, not a specific release version.
Don't know who told you that they haven't been updated for 4.3, but they
were wrong.  Use master as your base for the repo init and use the
local_manifest.xml file from the intent_mac (or cp_mac) branch of the
manifests project.

However, as we have noted previously, our intent is to re-implement
intent MAC on top of the 4.3 IntentFirewall, so the current
implementation is unlikely to remain relevant in the long term.




--
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