From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.120]) by mx.groups.io with SMTP id smtpd.web12.5387.1573139550322348940 for ; Thu, 07 Nov 2019 07:12:30 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=F3aVkvPX; spf=pass (domain: redhat.com, ip: 207.211.31.120, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573139549; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/fI6rGEzp78sAP9iIlVLzJGODu2NouixyGkTqACIxps=; b=F3aVkvPXMORfnjXLNuos2Gd6xDrJ3B4lXHYmAsBTcD95OMP8cYQpBwT2Gq+CcE8qv7AWpJ I8KXlqiqNeJrqF7+Y5YmEHnhLg6XF8XOKZFTOHTk6m2EwW08mf0clxNIYhLAlt4qDyVMYg CFf7nt+M4vWlnX5fkPVcS8JpsJmx9H4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-211-c0E-D7v-OYuUSGfw5ylZwA-1; Thu, 07 Nov 2019 10:12:25 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EE6531005500; Thu, 7 Nov 2019 15:12:24 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (unknown [10.36.118.71]) by smtp.corp.redhat.com (Postfix) with ESMTP id 364015D6D8; Thu, 7 Nov 2019 15:12:23 +0000 (UTC) Subject: Re: [edk2-devel] [edk2] DSC file : override FILE_GUID rule To: "Gao, Liming" , "devel@edk2.groups.io" , "tigerliu@zhaoxin.com" References: <44ad448fba40477f83fcb614df6880b7@zhaoxin.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E5395F2@SHSMSX104.ccr.corp.intel.com> From: "Laszlo Ersek" Message-ID: <0929b662-0447-ed46-1bc7-c53b26804408@redhat.com> Date: Thu, 7 Nov 2019 16:12:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E5395F2@SHSMSX104.ccr.corp.intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: c0E-D7v-OYuUSGfw5ylZwA-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 11/07/19 15:59, Gao, Liming wrote: > In FDF, you also need to specify this file guid and match the one in DSC= . The syntax is like below: >=20 > INF FILE_GUID=3D D1D74FE9-7A4E-41D3-A0B3-67F13AD34D94 UefiCpuPkg/PiSmmCp= uDxeSmm/PiSmmCpuDxeSmm.inf Thanks! (I assume there is no space character right after "FILE_GUID=3D".) Cheers Laszlo > Thanks > Liming >> -----Original Message----- >> From: devel@edk2.groups.io On Behalf Of Laszlo E= rsek >> Sent: Thursday, November 7, 2019 6:56 PM >> To: devel@edk2.groups.io; tigerliu@zhaoxin.com >> Subject: Re: [edk2-devel] [edk2] DSC file : override FILE_GUID rule >> >> On 11/07/19 05:51, Tiger Liu(BJ-RD) wrote: >>> Dear All: >>> I have a question about FILE_GUID override rule in dsc file. >>> For example: >>> ...... >>> UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf { >>> >>> FILE_GUID =3D D1D74FE9-7A4E-41D3-A0B3-67F13AD34D94 >>> ...... >>> } >>> >>> Usually, will define FILE_GUID in PiSmmCpuDxeSmm.inf . >>> >>> Why override it in dsc file? >> >> IIRC, such overrides allow the platform DSC file to build the same >> module multiple times, most likely with other overrides too (such as PC= D >> and lib class resolution). The resultant binaries will not conflict in >> any firmware volume / firmware file-system, by FILE_GUID. >> >> I don't remember the syntax, to be used in the FDF file, for refering t= o >> all of the builds of the same module INF file. >> >> Thanks >> Laszlo >> >> >>=20 >=20