On 10/04/2013 04:26 AM, duck wilson wrote:
> ... Really,
> all that is needed is to simply link to the need object files in
> MdeModulePkg/Universal/DevicePathDxe/. My problem is that I have not
> found a way to do this with build. I have included
> MdeModulePkg/MdeModulePkg.dec in the [Packages] section of the app .inf
> file. However, I don't see a way to instruct build to make
> MdeModulePkg/Universal/DevicePathDxe/.DevicePath.h part of the include
> path so I can simply statically link against the EDK2 library. Can this
> be done with build?
You could put a new .inf file in MdeModulePkg/Universal/DevicePathDxe
which builds the relevant .c files to generate a library. Then add the
library to your application in the usual way. That way you would only
have to maintain a new .inf file, rather than separate copies of the
source files. This would be what I'd recommend.
Or you could try modifying MdeModulePkg.dec to add
MdeModulePkg/Universal/DevicePathDxe to the [Includes] list. But that
may break other parts of the build, if it causes them to pick up the
wrong DevicePath.h.
Or you could hardcode stuff into the [BuildOptions] section of your
app's .inf file, but that sounds worse.
--
Brian Johnson
--------------------------------------------------------------------
To go fast, you may go alone. But to go far, you must go with others.
-- Norm Anderson
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
