(Preface: I am running on a Qualcomm AOSP build tree for Android-Q, and not
sure how different it is from an unmodified Android release.)
It doesn't look to me like symlinks work for cc_prebuilt_binary the way
they work for cc_binary.
Android.bp for the source case:
cc_binary {
name: "world",
strip: {
none: true,
},
srcs: [
"world.c",
],
symlinks: [
"hello"
],
}
Android.bp for the prebuilt case:
cc_prebuilt_binary {
name: "world_bin",
strip: {
none: true,
},
srcs: [
"world_bin",
],
symlinks: [
"hello_bin",
],
}
The results when both of these are built:
-rwxrwxr-x 1 builder group 14784 Apr 25 14:28 world_bin*
lrwxrwxrwx 1 builder group 5 Apr 25 14:28 hello -> world*
-rwxrwxr-x 1 builder group 14784 Apr 25 14:28 world*
It even appears that such symlinks declarations that are in AOSP/
system/core/logcat/Android.bp don't work:
cc_prebuilt_binary {
name: "logpersist.start",
srcs: ["logpersist"],
init_rc: ["logcatd.rc"],
required: ["logcatd"],
symlinks: [
"logpersist.stop",
"logpersist.cat",
],
strip: {
none: true,
},
}
Yields logpersist.start, but no links as logpersist.stop or logpersist.cat
Has the symlinks feature of cc_prebuilt_binary not been implemented yet?
Thanks in advance,
Chris
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/android-building/b747284a-513c-4b54-893b-4f506b996f75%40googlegroups.com.
