> -----Original Message----- > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of > Schmauss, Erik > Sent: Thursday, April 11, 2019 7:10 PM > Subject: Re: [edk2-devel] ASL build tools - EDKII trim tool questions
> Yes, the current iASL preprocessor implementation is incomplete > but we might be able to either develop our own or import an existing > preprocessor if it has the correct license. Eric, It depends on the end goal. If the goal is to display correct line numbers in the error messages, just adding support for #line directive is enough. If the goal is to compile ASL file with a single iasl run without usage of other tools such as Trim, I don't think even having a full-fledged preprocessed would suffice. In edk2, header files included into ASL files may contain C constructs, such as typedef's, alien to ASL compiler. The Trim tool cleans them up prior to running IASL. So even if iasl will be able to perform full preprocessing , Trim would still be required unless edk2 conventions are changed to require ASL-friendly include headers. Please consider the environment before printing this email. The information contained in this message may be confidential and proprietary to American Megatrends, Inc. This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
