| OLD | NEW |
| 1 Name: yasm | 1 Name: yasm |
| 2 URL: http://www.tortall.net/projects/yasm/ | 2 URL: http://www.tortall.net/projects/yasm/ |
| 3 Version: 1.1.0 | 3 Version: 1.1.0 |
| 4 With these patches merged: | 4 With these patches merged: |
| 5 * https://github.com/yasm/yasm/commit/a2cbb10ee1b90b73647667ac849c74d65761d412 | 5 * https://github.com/yasm/yasm/commit/a2cbb10ee1b90b73647667ac849c74d65761d412 |
| 6 * https://github.com/yasm/yasm/commit/01ab853e68ef8aeded716d6f5b34895200f66a51 | 6 * https://github.com/yasm/yasm/commit/01ab853e68ef8aeded716d6f5b34895200f66a51 |
| 7 * https://github.com/yasm/yasm/commit/82fafa7b5619e702c8681c959ade0746498e3cbc | 7 * https://github.com/yasm/yasm/commit/82fafa7b5619e702c8681c959ade0746498e3cbc |
| 8 | 8 |
| 9 License File: source/patched-yasm/COPYING | 9 License File: source/patched-yasm/COPYING |
| 10 Security Critical: no | 10 Security Critical: no |
| (...skipping 12 matching lines...) Expand all Loading... |
| 23 | 23 |
| 24 3) Next, capture all the output from a build of yasm. We will use the build | 24 3) Next, capture all the output from a build of yasm. We will use the build |
| 25 log as a reference for making the yasm.gyp file. | 25 log as a reference for making the yasm.gyp file. |
| 26 | 26 |
| 27 make yasm > yasm_build_log 2> yasm_build_err | 27 make yasm > yasm_build_log 2> yasm_build_err |
| 28 | 28 |
| 29 4) Check yasm_build_err to see if there are any anomalies beyond yasm's | 29 4) Check yasm_build_err to see if there are any anomalies beyond yasm's |
| 30 compiler warnings. | 30 compiler warnings. |
| 31 | 31 |
| 32 5) Grab the generated Makefile, libyasm-stdint.h, config.h, and put into | 32 5) Grab the generated Makefile, libyasm-stdint.h, config.h, and put into |
| 33 the correct platform location. | 33 the correct platform location. For android platform, copy the files |
| 34 generated for linux. |
| 34 | 35 |
| 35 src/third_party/yasm/source/config/[platform] | 36 src/third_party/yasm/source/config/[platform] |
| 36 | 37 |
| 37 While we do not directly use the "Makefile" to build, it is needed by | 38 While we do not directly use the "Makefile" to build, it is needed by |
| 38 the "genmodule" subprogram as input for creating the available modules | 39 the "genmodule" subprogram as input for creating the available modules |
| 39 list. | 40 list. |
| 40 | 41 |
| 41 6) Make sure all the subprograms are represented in yasm.gyp. | 42 6) Make sure all the subprograms are represented in yasm.gyp. |
| 42 | 43 |
| 43 grep '^gcc' yasm_build_log | | 44 grep '^gcc' yasm_build_log | |
| (...skipping 77 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 121 Yasm uses python scripts to generate the assembly code description | 122 Yasm uses python scripts to generate the assembly code description |
| 122 files in C++. Make sure to get these put into the gyp file properly as | 123 files in C++. Make sure to get these put into the gyp file properly as |
| 123 well. An example is gen_x86_insn.py for x86 assembly. | 124 well. An example is gen_x86_insn.py for x86 assembly. |
| 124 | 125 |
| 125 Note that at least the gen_x86_insn.py script suffers from the same | 126 Note that at least the gen_x86_insn.py script suffers from the same |
| 126 problem as genmacro in that it outputs to the current directory by | 127 problem as genmacro in that it outputs to the current directory by |
| 127 default. The yasm.gyp build patches this file before invoking it to | 128 default. The yasm.gyp build patches this file before invoking it to |
| 128 allow specifying an output directory. | 129 allow specifying an output directory. |
| 129 | 130 |
| 130 10) If all that's is finished, attempt to build....and cross your fingers. | 131 10) If all that's is finished, attempt to build....and cross your fingers. |
| OLD | NEW |