Details | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
1498 | serge | 1 | |
2 | |||
3 | |||
4 | |||
5 | |||
6 | to compile ASL source files. The output is sent to the VC output |
||
7 | window. |
||
8 | |||
9 | |||
10 | |||
11 | |||
12 | |||
13 | |||
14 | will see an empty rectangle. Click in the rectangle to enter a |
||
15 | name for this tool. |
||
16 | |||
17 | |||
18 | the other fields for this new custom tool. |
||
19 | |||
20 | |||
21 | |||
22 | |||
23 | Arguments: -e "$(FilePath)" |
||
24 | Initial Directory "$(FileDir)" |
||
25 | Use Output Window |
||
26 | |||
27 | |||
28 | "-e" instructs the compiler to produce messages appropriate for VC. |
||
29 | Quotes around FilePath and FileDir enable spaces in filenames. |
||
30 | |||
31 | |||
32 | |||
33 | |||
34 | By enabling "Use Output Window", you can click on error messages in |
||
35 | the output window and the source file and source line will be |
||
36 | automatically displayed by VC. Also, you can use F4 to step through |
||
37 | the messages and the corresponding source line(s). |
||
38 | |||
39 | |||
40 | |||
41 | |||
42 | |||
43 | |||
44 | |||
45 | |||
46 | |||
47 | Project/Settings/CustomBuild with the following settings (or similar): |
||
48 | |||
49 | |||
50 | c:\acpi\libraries\iasl.exe -vs -vi "$(InputPath)" |
||
51 | |||
52 | |||
53 | $(InputDir)\$(InputPath).aml |
||
54 | |||
55 | |||
56 | |||
57 | |||
58 | |||
59 | |||
60 | |||
61 | |||
62 | |||
63 | 1) The Flex (or Lex) lexical analyzer generator. |
||
64 | 2) The Bison (or Yacc) parser generator. |
||
65 | 3) An ANSI C compiler. |
||
66 | |||
67 | |||
68 | |||
69 | |||
70 | |||
71 | generate the compiler: |
||
72 | |||
73 | |||
74 | 2) The ACPI CA Core Subsystem source. In particular, the Namespace Manager |
||
75 | component is used to create an internal ACPI namespace and symbol table, |
||
76 | and the AML Interpreter is used to evaluate constant expressions. |
||
77 | 3) The Common source for all ACPI components. |
||
78 |