tool chain tag setting for vs2017

tool chain tag setting for vs2017

["徐林]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 751 bytes --]

Hey guys,


I may found a problem here..


I'm trying to build tianocore with visual studio 2017, the tianocore commit id is 
df7c81b5b219c9aee776baa466dd64c9d318dd80(Tue Apr 30 10:16:01 2019),
after seting up the build environment and change TOOL_CHAIN_TAG to VS2017x86
according from https://github.com/tianocore/tianocore.github.io/wiki/Windows-systems-ToolChain-Matrix
, then build, the process will terminate with error message:
[VS2017x86] not defined. No toolchain available for build! 


After several tries, i change TOOL_CHAIN_TAG to VS2017 instead of VS2017x86, 
then the problem solved, i'm not sure if vs2017 setting is inconsistent with vs2015 or vs2010..
or i have wrong setting somewhere else?


Best regards,
Flynn

[-- Attachment #2: Type: text/html, Size: 1215 bytes --]

Re: [edk2-devel] tool chain tag setting for vs2017

[Pete Batard]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030; format=flowed, Size: 1414 bytes --]

Hi Flynn,

On 2019.05.08 09:00, "ÐìÁÖ wrote:
> Hey guys,
> 
> I may found a problem here..
> 
> I'm trying to build tianocore with visual studio 2017, the tianocore 
> commit id is
> df7c81b5b219c9aee776baa466dd64c9d318dd80(Tue Apr 30 10:16:01 2019),
> after seting up the build environment and change TOOL_CHAIN_TAG to VS2017x86
> according from 
> https://github.com/tianocore/tianocore.github.io/wiki/Windows-systems-ToolChain-Matrix

The first thing that needs to be pointed out is that the 
ToolChain-Matrix has not been updated for VS2017, so you need to be 
careful about extrapolating what applies for VS2015 or VS2013 to VS2017.

> , then build, the process will terminate with error message:
> *[VS2017x86] not defined. No toolchain available for build! *

Indeed. That's because we are now using a separate VS2017_HOST 
(currently set to 'x86' by default) to identify the architecture of the 
host platform tools, so we're not using VS2017x86 any more.

> After several tries, i change TOOL_CHAIN_TAG to *VS2017 *instead of 
> VS2017x86,
> then the problem solved, i'm not sure if vs2017 setting is inconsistent 
> with vs2015 or vs2010..
> or i have wrong setting somewhere else?

You should just use VS2017. And of course, we'll need to update the 
Matrix to make that information public as well.

If you are seeing issues after setting TOOL_CHAIN_TAG to VS2017, please 
let us know.

Regards,

/Pete

Re: [edk2-devel] tool chain tag setting for vs2017

["徐林]

[-- Attachment #1: Type: text/html, Size: 2575 bytes --]

Re: [edk2-devel] tool chain tag setting for vs2017

[Pete Batard]

On 2019.05.08 13:16, xulin wrote:
> Got it. BTW, do you have plan to support for higher version GCC? Such as 
> GCC8?

Well, I am not speaking for the project as a whole, but past experience 
seems to indicate that support for newer toolchain is added by 
contributors (which, really, can be anyone) on an ad hoc basis, when the 
need is identified and/or a new toolchain becomes popular, as well as 
*if* the definitions from the current toolchain (such as GCC5) do not 
work well enough to support the later versions.

So I don't think there are official plans with regards to adding such an 
such toolchain (such as GCC8 or VS2019) apart from waiting for 
contributors, who might have a vested interest in those, to provide 
patches where needed. For most Open Source projects, this usually happen 
organically, without any specific timeline, as each toolchain becomes 
more widespread.

Regards,

/Pete

Re: [edk2-devel] tool chain tag setting for vs2017

[Leif Lindholm]

On Wed, May 08, 2019 at 03:44:45PM +0100, Pete Batard wrote:
> On 2019.05.08 13:16, xulin wrote:
> > Got it. BTW, do you have plan to support for higher version GCC? Such as
> > GCC8?
> 
> Well, I am not speaking for the project as a whole, but past experience
> seems to indicate that support for newer toolchain is added by contributors
> (which, really, can be anyone) on an ad hoc basis, when the need is
> identified and/or a new toolchain becomes popular, as well as *if* the
> definitions from the current toolchain (such as GCC5) do not work well
> enough to support the later versions.
> 
> So I don't think there are official plans with regards to adding such an
> such toolchain (such as GCC8 or VS2019) apart from waiting for contributors,
> who might have a vested interest in those, to provide patches where needed.
> For most Open Source projects, this usually happen organically, without any
> specific timeline, as each toolchain becomes more widespread.

Correct.

Basically, GCC 4.x was an absolute mess in changing command line
options and behaviours (cetainly on the ARM* side, but I think also
for x86). Since GCC 5.0, this has stabilised a lot, so we
haven't needed to produce any version-specific profiles since that one.

GCC9 looks "interesting" in throwing up new buildtime warnings (from
looking at other projects), so it might be that it will need a new
profile, but it may also be that all those are genuine bugs and need
to be fixed.

Certainly, any issues people come across, please report.

Regards,

Leif

> Regards,
> 
> /Pete
> 
> 
> 

Re: [edk2-devel] tool chain tag setting for vs2017

["徐林]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 2257 bytes --]

>
 
>On Wed, May 08, 2019 at 03:44:45PM +0100, Pete Batard wrote:
 
>> On 2019.05.08 13:16, xulin wrote:
 
>> > Got it. BTW, do you have plan to support for higher version GCC? Such as
 
>> > GCC8?
 
>>
 
>> Well, I am not speaking for the project as a whole, but past experience
 
>> seems to indicate that support for newer toolchain is added by contributors
 
>> (which, really, can be anyone) on an ad hoc basis, when the need is
 
>> identified and/or a new toolchain becomes popular, as well as *if* the
 
>> definitions from the current toolchain (such as GCC5) do not work well
 
>> enough to support the later versions.
 
>>
 


 
Certainly.
 


 
GCC5 is working good on Ubuntu 16.04, but i have another PC with Ubuntu 18.10
 
installed, and i can't just install gcc-5 with apt-get install, i guess gcc-5
 
package is removed from apt source, i believe i can find a way to install
 
gcc-5 on Ubuntu 18.10 with some effort... but i would not try to, because 
 
VS2017 works good now :)
 


 
>> So I don't think there are official plans with regards to adding such an
 
>> such toolchain (such as GCC8 or VS2019) apart from waiting for contributors,
 
>> who might have a vested interest in those, to provide patches where needed.
 
>> For most Open Source projects, this usually happen organically, without any
 
>> specific timeline, as each toolchain becomes more widespread.
 
>
 
>Correct.
 
>
 
>Basically, GCC 4.x was an absolute mess in changing command line
 
>options and behaviours (cetainly on the ARM* side, but I think also
 
>for x86). Since GCC 5.0, this has stabilised a lot, so we
 
>haven't needed to produce any version-specific profiles since that one.
 
>
 
>GCC9 looks "interesting" in throwing up new buildtime warnings (from
 
>looking at other projects), so it might be that it will need a new
 
>profile, but it may also be that all those are genuine bugs and need
 
>to be fixed.
 


 
Oh..I didn't notice that GCC9 is available now, maybe i should check the
 
release News.




Thank you :)




Regards,

Flynn
 


 
>
 
>Certainly, any issues people come across, please report.
 
>
 
>Regards,
 
>
 
>Leif

[-- Attachment #2: Type: text/html, Size: 5147 bytes --]

Re: [edk2-devel] tool chain tag setting for vs2017

[Liming Gao]

[-- Attachment #1: Type: text/plain, Size: 2709 bytes --]

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of "徐林
Sent: Wednesday, May 8, 2019 11:49 PM
To: Leif Lindholm <leif.lindholm@linaro.org>; devel <devel@edk2.groups.io>; pete <pete@akeo.ie>
Subject: Re: [edk2-devel] tool chain tag setting for vs2017


>

>On Wed, May 08, 2019 at 03:44:45PM +0100, Pete Batard wrote:

>> On 2019.05.08 13:16, xulin wrote:

>> > Got it. BTW, do you have plan to support for higher version GCC? Such as

>> > GCC8?

>>

>> Well, I am not speaking for the project as a whole, but past experience

>> seems to indicate that support for newer toolchain is added by contributors

>> (which, really, can be anyone) on an ad hoc basis, when the need is

>> identified and/or a new toolchain becomes popular, as well as *if* the

>> definitions from the current toolchain (such as GCC5) do not work well

>> enough to support the later versions.

>>



Certainly.



GCC5 is working good on Ubuntu 16.04, but i have another PC with Ubuntu 18.10

installed, and i can't just install gcc-5 with apt-get install, i guess gcc-5

package is removed from apt source, i believe i can find a way to install

gcc-5 on Ubuntu 18.10 with some effort... but i would not try to, because

VS2017 works good now :)



You don’t need to install GCC5. You can try build the code with GCC5 tool chain.

If you find any issue, please submit BZ https://bugzilla.tianocore.org/. Current design is

to make GCC5 support GCC version 5 or above.



>> So I don't think there are official plans with regards to adding such an

>> such toolchain (such as GCC8 or VS2019) apart from waiting for contributors,

>> who might have a vested interest in those, to provide patches where needed.

>> For most Open Source projects, this usually happen organically, without any

>> specific timeline, as each toolchain becomes more widespread.

>

>Correct.

>

>Basically, GCC 4.x was an absolute mess in changing command line

>options and behaviours (cetainly on the ARM* side, but I think also

>for x86). Since GCC 5.0, this has stabilised a lot, so we

>haven't needed to produce any version-specific profiles since that one.

>

>GCC9 looks "interesting" in throwing up new buildtime warnings (from

>looking at other projects), so it might be that it will need a new

>profile, but it may also be that all those are genuine bugs and need

>to be fixed.



Oh..I didn't notice that GCC9 is available now, maybe i should check the

release News.



Thank you :)



Regards,

Flynn



>

>Certainly, any issues people come across, please report.

>

>Regards,

>

>Leif



[-- Attachment #2: Type: text/html, Size: 12199 bytes --]