| f290793bc65b8483332ac8b568962395c4a63927 |
13-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine SHA-1 related stuffs.
1. Introduce libbcc.sha1.so instead of raw file libbcc.so.sha1
* Now tools/build/gen-sha1-stamp.py generated assembly contains
symbols libbcc_so_SHA1 and libRS_so_SHA1 associated with their
SHA-1 digests.
* In that way, their SHA-1 information can be obtained via
dlopen().
2. Refine Sha1Helper to Sha1Util.
2. Remove unused tools/build/dataconvert.py by the way.
Change-Id: I345e1a09e6206748fb8dfabf891154de97a063ec
ataconvert.py
en-sha1-stamp.py
|
| 7a5d423014e1cc95e34764b3ddf8e80ace3509b8 |
12-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Get build information in C++ way.
Change-Id: I5d2d2c18192bf9e5d2b9aa5a2bc1cce331191572
en-build-info.py
en-build-stamp.py
|
| ddf5661793de8fb4e16906b7f7822972fcb13c6d |
12-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine the makefiles.
* Introduce libbcc.mk which defines the path for makefiles and libbcc
configuration.
* Introduce libbcc-{device,host}-build.mk which defines the build
flags for building libbcc itself and/or for building module using
libbcc.
* Add header guard for generated ConfigFromMk.h.
Change-Id: I892f6d3637f628ea6aa0116d92ebc54770ce3a47
en-build-stamp.py
en-config-from-mk.py
en-sha1-stamp.py
|
| b8ef690813bf3b32f996afb0ddc048c5bb23c8f5 |
03-May-2012 |
Stephen Hines <srhines@google.com> |
Revert "Refine the makefiles."
This reverts commit fa52e2083927dd4ea543528c557d52ab578ad34c.
en-build-stamp.py
en-config-from-mk.py
en-sha1-stamp.py
|
| aa72a210b0f73671b01984020a74360c10427e31 |
03-May-2012 |
Stephen Hines <srhines@google.com> |
Revert "Get build information in C++ way."
This reverts commit 44d991658dbd5b80648a3944f1760ad19bbcac09.
en-build-info.py
en-build-stamp.py
|
| 6975a6653f5c433ba2fc009b4400c1c8157b512f |
03-May-2012 |
Stephen Hines <srhines@google.com> |
Revert "Refine SHA-1 related stuffs."
This reverts commit 6378d8f50449d79b8937c238b968ceeb9dbd4ee1.
Conflicts:
Android.mk
Change-Id: Ib8988583a0b916d21e9314e919269f02c4dd600e
ataconvert.py
en-sha1-stamp.py
|
| 6378d8f50449d79b8937c238b968ceeb9dbd4ee1 |
13-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine SHA-1 related stuffs.
1. Introduce libbcc.sha1.so instead of raw file libbcc.so.sha1
* Now tools/build/gen-sha1-stamp.py generated assembly contains
symbols libbcc_so_SHA1 and libRS_so_SHA1 associated with their
SHA-1 digests.
* In that way, their SHA-1 information can be obtained via
dlopen().
2. Refine Sha1Helper to Sha1Util.
2. Remove unused tools/build/dataconvert.py by the way.
ataconvert.py
en-sha1-stamp.py
|
| 44d991658dbd5b80648a3944f1760ad19bbcac09 |
12-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Get build information in C++ way.
en-build-info.py
en-build-stamp.py
|
| fa52e2083927dd4ea543528c557d52ab578ad34c |
12-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine the makefiles.
* Introduce libbcc.mk which defines the path for makefiles and libbcc
configuration.
* Introduce libbcc-{device,host}-build.mk which defines the build
flags for building libbcc itself and/or for building module using
libbcc.
* Add header guard for generated ConfigFromMk.h.
en-build-stamp.py
en-config-from-mk.py
en-sha1-stamp.py
|
| b4db722b7e400d9ce93f41b3d4243fd4f20ef300 |
06-Feb-2012 |
Zonr Chang <zonr.net@gmail.com> |
Move the build-related script under tools/build.
ataconvert.py
en-build-stamp.py
en-config-from-mk.py
en-sha1-stamp.py
|