From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lersek@redhat.com>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=66.187.233.73; helo=mx1.redhat.com; envelope-from=lersek@redhat.com;
 receiver=edk2-devel@lists.01.org 
Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.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 3821122106DD3
 for <edk2-devel@lists.01.org>; Wed, 28 Mar 2018 11:26:07 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com
 [10.11.54.3])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id 3338CEB700;
 Wed, 28 Mar 2018 18:32:45 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-75.rdu2.redhat.com
 [10.10.120.75])
 by smtp.corp.redhat.com (Postfix) with ESMTP id 982C710B0089;
 Wed, 28 Mar 2018 18:32:44 +0000 (UTC)
To: edk2-lists@mc2research.org, edk2-devel@lists.01.org
References: <000401d3c6c0$aef61660$0ce24320$@mc2research.org>
From: Laszlo Ersek <lersek@redhat.com>
Message-ID: <51a644fe-dc27-8153-628b-c13bd37970f9@redhat.com>
Date: Wed, 28 Mar 2018 20:32:43 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <000401d3c6c0$aef61660$0ce24320$@mc2research.org>
X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.11.55.1]); Wed, 28 Mar 2018 18:32:45 +0000 (UTC)
X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]);
 Wed, 28 Mar 2018 18:32:45 +0000 (UTC) for IP:'10.11.54.3'
 DOMAIN:'int-mx03.intmail.prod.int.rdu2.redhat.com'
 HELO:'smtp.corp.redhat.com' FROM:'lersek@redhat.com' RCPT:''
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  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2018 18:26:08 -0000
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

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_inf_overview/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. :)

Thanks
Laszlo