public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Andrew Fish <afish@apple.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: edk2-devel <edk2-devel@lists.01.org>
Subject: Re: Can I do this in an INF file?
Date: Tue, 16 May 2017 19:43:24 -0700	[thread overview]
Message-ID: <D8DC458C-C765-42B5-B800-AC5BB861EB74@apple.com> (raw)
In-Reply-To: <9C5BAB2F-5013-416E-B8A7-1F606DCCE1CB@apple.com>

Liming,

Why does INF syntax support [LibraryClasses.common.DXE_RUNTIME_DRIVER] if it does nothing? 

https://edk2-docs.gitbooks.io/edk-ii-inf-specification/content/3_edk_ii_inf_file_format/36_[libraryclasses]_sections.html

Thanks,

Andrew Fish


> On May 16, 2017, at 6:46 PM, Andrew Fish <afish@apple.com> wrote:
> 
>> 
>> On May 16, 2017, at 6:41 PM, Gao, Liming <liming.gao@intel.com <mailto:liming.gao@intel.com>> wrote:
>> 
>> Andrew:
>> There is no such usage. INF can specify source files for the different ARCHs, but not specify source files for the different module type. In fact, INF module type is fixed. It can't be changed to other type in build time. If you expect the library to be linked to the different type driver with the different sources, you may create two version INF files to include the different source files.  
>> 
> 
> Liming,
> 
> Thanks. Yes given how the build system works what I asked is not possible. 
> 
> I ended up doing it the correct way and made an instance of the UefiRuntimeLib to link against. 
> 
> Thanks,
> 
> Andrew Fish
> 
>> Thanks
>> Liming
>>> -----Original Message-----
>>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>>> Andrew Fish
>>> Sent: Wednesday, May 17, 2017 7:43 AM
>>> To: edk2-devel <edk2-devel@lists.01.org>
>>> Subject: [edk2] Can I do this in an INF file?
>>> 
>>> I'm trying to cross compile a runtime library to work in an Application (for
>>> testing). I can't seem to restrict files and libs to specific module types?
>>> 
>>> [Sources.common.UEFI_APPLICATION]
>>> FakeRuntime.c
>>> 
>>> 
>>> [LibraryClasses.common.DXE_RUNTIME_DRIVER]
>>> UefiRuntimeLib
>>> 
>>> Am I using the wrong syntax?
>>> 
>>> Thanks,
>>> 
>>> Andrew Fish
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://lists.01.org/mailman/listinfo/edk2-devel
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org <mailto:edk2-devel@lists.01.org>
>> https://lists.01.org/mailman/listinfo/edk2-devel <https://lists.01.org/mailman/listinfo/edk2-devel>
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org <mailto:edk2-devel@lists.01.org>
> https://lists.01.org/mailman/listinfo/edk2-devel <https://lists.01.org/mailman/listinfo/edk2-devel>


  reply	other threads:[~2017-05-17  2:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 23:42 Can I do this in an INF file? Andrew Fish
2017-05-17  1:41 ` Gao, Liming
2017-05-17  1:46   ` Andrew Fish
2017-05-17  2:43     ` Andrew Fish [this message]
2017-05-17 14:00       ` Gao, Liming
2017-05-17 15:41         ` Andrew Fish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D8DC458C-C765-42B5-B800-AC5BB861EB74@apple.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox