Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
A
AndroidSystemSEPolicy
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container registry
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Werner Sembach
AndroidSystemSEPolicy
Commits
bf539bf3
Commit
bf539bf3
authored
12 years ago
by
Geremy Condra
Committed by
Gerrit Code Review
12 years ago
Browse files
Options
Downloads
Plain Diff
Merge "Fix makefile error with ANDROID_BUILD_TOP"
parents
edf7b4c8
52fc95d1
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
Android.mk
+1
-1
1 addition, 1 deletion
Android.mk
keys.conf
+2
-2
2 additions, 2 deletions
keys.conf
with
3 additions
and
3 deletions
Android.mk
+
1
−
1
View file @
bf539bf3
...
...
@@ -182,7 +182,7 @@ $($(MAC_PERMISSION_FILE).tmp) : $(call build_policy, $(MAC_PERMISSION_FILE))
$(LOCAL_BUILT_MODULE)
:
$($(MAC_PERMISSION_FILE).tmp) $(mac_perms_keys.tmp) $(HOST_OUT_EXECUTABLES)/insertkeys.py
@
mkdir
-p
$(
dir
$@
)
$(
HOST_OUT_EXECUTABLES
)
/insertkeys.py
-t
$(
TARGET_BUILD_VARIANT
)
-c
$(
ANDROID_BUILD_
TOP
)
$(
mac_perms_keys.tmp
)
-o
$@
$<
$(
HOST_OUT_EXECUTABLES
)
/insertkeys.py
-t
$(
TARGET_BUILD_VARIANT
)
-c
$(
TOP
)
$(
mac_perms_keys.tmp
)
-o
$@
$<
$(MAC_PERMISSION_FILE).tmp
:=
##################################
...
...
This diff is collapsed.
Click to expand it.
keys.conf
+
2
−
2
View file @
bf539bf3
#
# Maps an arbitrary tag [TAGNAME] with the string contents found in
# TARGET_BUILD_VAR
A
INT. Common convention is to start TAGNAME with an @ and
# TARGET_BUILD_VARI
A
NT. Common convention is to start TAGNAME with an @ and
# name it after the base file name of the pem file.
#
# Each tag (section) then allows one to specify any string found in
# TARGET_BUILD_VARIANT. Typcially this is user, eng, and userdebug. Another
# option is to use ALL which will match ANY TARGET_BUILD_VAR
A
INT string.
# option is to use ALL which will match ANY TARGET_BUILD_VARI
A
NT string.
#
[@
PLATFORM
]
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment