On 02/25/2014 07:14 PM, John Davis wrote:
> Hello Jaben,
>
> No I did not. Its odd. Sometimes you add packages and it seems to
> compile and link. Other times I have to add a library package. In this
> case, I added the GenericBdsLib in the [LibraryClasses] and now it
> links. Many thanks. I'll look into your suggestion on the other
> routine to get the path.
Sometimes you get lucky. If you call a function in library A, and you
have library B in your [LibraryClasses], and library B has library A in
its [LibraryClasses], then your code will be linked against both library
A and library B. So you won't get a linker error. But if library B
didn't already depend on library A, then your module wouldn't be linked
against library A, and you'd get an error.
It's best to list in your .inf file all the library classes which your
code calls directly. The rule of thumb is that if you include a
library's header file (#include <Library/SomeLib.h>), you should list
that library class in your [LibraryClasses]. The build system is smart
enough to handle dependencies, remove redundant items, etc.
--
Brian
--------------------------------------------------------------------
"I have discovered that all human evil comes from this, man's being
unable to sit still in a room."
-- Blaise Pascal
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
