RE: [Edk2 Dev] Pcds in AutoGen.h vs AutoGen.c

Subject: RE: [Edk2 Dev] Pcds in AutoGen.h vs AutoGen.c

From: Penny Gao <penny.gao@intel.com>

To: dev@edk2.tianocore.org, dev@buildtools.tianocore.org

Date: 2009-06-12 22:03:39

Hi, Carl,

It seems I cannot fully understand your question. In general, PCD informati=
on goes into Autogen.h and Autogen.c because a simple PcdGet() can support =
different type of PCDs (fix at build, patchable, and dynamic). The PCD type=
 is chosen by DSC file, so we need Autogen code (be different when differen=
t type get chosen) to handle the difference at build time.

Can you let us know what kind you changes you made, and what kind of tool b=
ehavior you are expecting for?

Best Regards,
Penny

-----Original Message-----
From: Carl Norum [mailto:carl.norum@apple.com]=20
Sent: Friday, June 12, 2009 2:43 AM
To: dev@edk2.tianocore.org; dev@buildtools.tianocore.org
Subject: [Edk2 Dev] Pcds in AutoGen.h vs AutoGen.c

Hi everybody,

I'm doing some build system experimentation with Edk2.  What's the =20
reasoning behind some PCDs ending up in AutoGen.h vs. AutoGen.c, and =20
where does that decision get made?  Right now my changes are getting =20
output through to the AutoGen.h files for any driver/library that =20
directly includes a .dec file where my feature has been added, but any =20
implicit ones don't come through.  Where in the build system does that =20
hierarchical step take place?

Thanks for any help!

--=20
Carl Norum
Firmware Engineer
Apple, Inc.
Cupertino, CA

------------------------------------------------------
https://edk2.tianocore.org/ds/viewMessage.do?dsForumId=3D135&dsMessageId=3D=
44405

To unsubscribe from this discussion, please e-mail [unsubscribeURL]

------------------------------------------------------
https://edk2.tianocore.org/ds/viewMessage.do?dsForumId=3D135&dsMessageId=3D=
44459

To unsubscribe from this discussion, please e-mail [unsubscribeURL]