Nicolas,
I think the terminology in the build spec. is confusing. Using the classic
definition of static linking, like your example, all EFI modules are statically
linked.
Libraries are linked as objects, that can be linked into Modules. Modules are
linked into relocatable PE/COFF images.
Andrew Fish
On Aug 30, 2012, at 8:04 PM, nicolas wrote:
> hi, experts:
> i am studying edkii build spec.
> It talked about static link/dynamic link in chapter 9.4 .
> It said:
> 1. for lib modules, it used static link as the last step.
> 2. for non-lib modules, such as drivers/app, static link step is optional.
>
> so, it made me confused!
> based on my understanding, uefi drivers/applications are all static linked.
>
> take an example:
> 1. App1 and App2 used a same lib "BasePrintLib".
> so, if App1/App2 are not static linked, there should be only one instance
> "BasePrintLib".
>
> best wishes
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> edk2-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
