From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=69.167.158.73; helo=host12.webserveralpha.com; envelope-from=darylm@mc2research.com; receiver=edk2-devel@lists.01.org Received: from host12.webserveralpha.com (host12.webserveralpha.com [69.167.158.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 8733721E08173 for ; Fri, 6 Apr 2018 15:01:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mc2research.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=lbV8TMiPe8AyhX14a0WspbLJZqNBjRTFmScqBaEinlw=; b=2eEwdYogg6UxVbKfIJMAbOdDW3 P1tebS2HT8unwoSmgwA+sZqRdLxoWrvSzI4RjV8Hfn4xUAfP7pIISDqUHW4gBxPIzuLv1c6dgK+Kt sdNKTmZBROr4MnXjwxsHAY0nt; Received: from mobile-166-176-184-188.mycingular.net ([166.176.184.188]:49187 helo=DWIM) by host12.webserveralpha.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1f4ZPz-0003TE-HP; Fri, 06 Apr 2018 18:01:11 -0400 From: To: "'Gao, Liming'" , References: <000401d3c6c0$aef61660$0ce24320$@mc2research.org> <51a644fe-dc27-8153-628b-c13bd37970f9@redhat.com> <3afc6f92-81aa-a90c-289e-2868caade361@redhat.com> <002001d3c6e6$d67d4cf0$8377e6d0$@mc2research.org> <4A89E2EF3DFEDB4C8BFDE51014F606A14E1EF9AF@SHSMSX104.ccr.corp.intel.com> <00f301d3c7b3$117aa4c0$346fee40$@mc2research.org> <4A89E2EF3DFEDB4C8BFDE51014F606A14E1EFD58@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1EFD58@SHSMSX104.ccr.corp.intel.com> Date: Fri, 6 Apr 2018 15:01:10 -0700 Message-ID: <000001d3cdf2$c6cb5370$5461fa50$@mc2research.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHw8jyUM++hGKuaad5p0gnKeR0aiQLOIJusAfCXsaQBMVb7iQK/txowAcQfut8BuvXvIKNYiapw X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host12.webserveralpha.com X-AntiAbuse: Original Domain - lists.01.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - mc2research.com X-Get-Message-Sender-Via: host12.webserveralpha.com: authenticated_id: darylm@mc2research.com X-Authenticated-Sender: host12.webserveralpha.com: darylm@mc2research.com X-Source: X-Source-Args: X-Source-Dir: X-Mailman-Approved-At: Fri, 06 Apr 2018 16:19:10 -0700 Subject: Re: Dependency expression inheritance problems X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2018 22:01:13 -0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Language: en-us Liming, I don't remember whether I replied to you. I submitted Bugzilla report #914 - DEPEX not inherited from binary libraries - on 30 March 2018. Thanks, Daryl -----Original Message----- From: edk2-devel On Behalf Of Gao, Liming Sent: Thursday, March 29, 2018 5:36 PM To: edk2-lists@mc2research.org; edk2-devel@lists.01.org Subject: Re: [edk2] Dependency expression inheritance problems Daryl: Could you submit one tracker in bugzillar? We will check it in BaseTools. Thanks Liming > -----Original Message----- > From: darylm@mc2research.com [mailto:darylm@mc2research.com] On Behalf > Of edk2-lists@mc2research.org > Sent: Friday, March 30, 2018 7:10 AM > To: Gao, Liming ; edk2-devel@lists.01.org > Subject: RE: [edk2] Dependency expression inheritance problems > > Liming, > > This is only a problem with binary libraries. If I do everything from > sources, the generated .depex is correct. > > Daryl > > -----Original Message----- > From: Gao, Liming > Sent: Thursday, March 29, 2018 12:08 AM > To: edk2-lists@mc2research.org; 'Laszlo Ersek' ; > edk2-devel@lists.01.org > Subject: RE: [edk2] Dependency expression inheritance problems > > Daryl: > Do you try the source library INF file? EDK2 build system will > inherit the depex section from its library. Seemly, this is an issue > when the module is the binary library. > > Thanks > Liming > >-----Original Message----- > >From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf > >Of edk2-lists@mc2research.org > >Sent: Thursday, March 29, 2018 6:48 AM > >To: 'Laszlo Ersek' ; edk2-devel@lists.01.org > >Subject: Re: [edk2] Dependency expression inheritance problems > > > >Laszlo, > > > >I think you are thinking of the old .dxs files. EDK II supports > >them, but their use is discouraged. > >From the "EDK II Build Specification", v1.27: > >"For EDK II modules, the build tools will create the complete > >dependency expression using the information in the [Depex] section > >along with all [Depex] sections from the linked in library instances." > > > >and > > > >"Once all files are parsed, the build tools will do following work > >for each EDK II > >module: > > ... > > * Inherit library instance dependency ( [Depex] sections) > >expressions > > >if a module does not list a separate dependency file." > > > >So, use of the [Depex] sections in the .DSC and .INF files is > >supposed to be the way to go. > > > >The spec. also states that if a .dxs file is specified, inheritance > >will not be used and the .dxs file must specify every dependency. > >"Use of a separate file for describing the dependencies is discouraged. ... > >Libraries may also have a dependency, [Depex] , section. These > >dependencies must be appended to the module's DEPEX sections unless > >the module includes a depex (.dxs) file - even if the module does not > >contain a [Depex] section. When a developer chooses to write the .dxs > >file, the developer is responsible for specifying all dependencies in > >the > .dxs file." > > > >I believe that according to the spec., what I am attempting should > >work. The EDK II build tools should generate a .depex file for the > >module that contains the module's depex as well as depex' inherited > >from the module's component libraries. > > > >But, I could be misinterpreting the spec. or doing something wrong in > >the build files (.DSC and .INF). > > > >Has anyone actually looked at the .depex that the tools produce and > >compared it to what the expected contents are for binary and hybrid > >(binary + > >source) builds? > > > >Thanks much, > >Daryl > > > > > >-----Original Message----- > >From: Laszlo Ersek > >Sent: Wednesday, March 28, 2018 11:34 AM > >To: edk2-lists@mc2research.org; edk2-devel@lists.01.org > >Subject: Re: [edk2] Dependency expression inheritance problems > > > >On 03/28/18 20:32, Laszlo Ersek wrote: > >> On 03/28/18 20:14, edk2-lists@mc2research.org wrote: > >>> Hopefully someone on the list can help with this problem. > >>> > >>> > >>> > >>> I have a DXE_DRIVER that links with several libraries. Some of > >>> these libraries are from a binary distribution. I checked the > >>> binary library's .INF file and it has the [LibraryClasses] and > >>> [Depex] sections present in the same format as for a source .INF. > >>> (not > >>> comments) > >> > >> Isn't that wrong (from the binary distribution)? The INF spec makes > >> me think think that library instances provided in binary format > >> should ship their standalone .depex files as well, and they should > >> be referenced in the [Binaries] section of the respective lib > >> instance INF > file. > >> > >> https://edk2-docs.gitbooks.io/edk-ii-inf-specification/content/2_in > >> f_ o verview/215_[depex]_section.html#215-depex-section > >> > >> "Binary .depex files are listed in [Binaries] sections of the INF files." > >> > >> I vaguely recall seeing an example somewhere, but nothing specific. > >> I could be totally wrong. :) > > > >I should have looked a but further in the same spec :) See the "Example" > >section here: > > > >https://edk2-docs.gitbooks.io/edk-ii-inf- > >specification/content/3_edk_ii_inf_file_format/315_[binaries]_section > >.h > >tml > > > >Laszlo > > > >_______________________________________________ > >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 https://lists.01.org/mailman/listinfo/edk2-devel