On 09/19/2013 02:40 AM, David F. wrote:
> Hi,
>
> What is the recommended method for building to different binaries from
> the same code base package. The only difference is the defines used on
> building that package, all the other support packages stay the same.
>
> I thought about having two different .inf files with [buildoptions]
> giving the different defines and [Defines] giving a different base name.
> Would liked to !include the packages, sources, libraryclasses,
> protocols, but can't !include in .inf files.
That's exactly the strategy we've used. I'm not sure there's a better
way.... You could potentially use PCDs instead of defines to control
the build, which would be more portable than overriding [buildoptions]
directly. But you'd still need two .inf files.
You could move your common code into a library, and share it between two
modules containing the varying code. But that would be even more
complicated.
--
Brian Johnson
--------------------------------------------------------------------
"My bicycle is an elegant form of transportation. It carries me
far faster than I can run, yet I can carry it with one hand."
-- me
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
edk2-buildtools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel
