[Scons-users] Problem upgrading from 3.0.1 to 3.1.2

[Steve Hill (Wireless)]

Thanks Mats. I'm happy to provide whatever extra information would help but the situation appears to be identical to that shown in the manual:

- I have a callable class (Cygwinify vs. foo)
- I define an environment variable equal to the class (CYGWINIFY vs. FOO)
- I put the constructor between ${ and } (in CCCOM vs. BAR)

The manual claims that the object should be called when the environment variable is expanded but I am getting the stringified version of the object.

FYI, I have installed 3.1.2 with Python 2 and don't see the problem. So this does seem to be a Python 3 issue but I seem to be doing exactly what the manual specifies...

S.

-----Original Message-----
From: Scons-users <scons-users-bounces at scons.org> On Behalf Of Mats Wichmann
Sent: 14 May 2020 16:30
To: scons-users at scons.org
Subject: Re: [Scons-users] Problem upgrading from 3.0.1 to 3.1.2

On 5/14/20 3:26 AM, Steve Hill (Wireless) via Scons-users wrote:

> I am now trying to upgrade to 3.1.2 and Python 3.6.3 and get this:
>  
> powerpc-eabi-gcc <stuff...> -o <edk_v10_1.Cygwinify object at
> 0x000001E1FEE95EB8> -c <edk_v10_1.Cygwinify object at 
> 0x000001E1FEE95EB8> 0x000001E1FEE95E10>
> 
> Have I missed something in my Python 2 -> Python 3 port or has 
> something changed in SCons between 3.0 and 3.1?

As a general note, it's not uncommon when converting from Py2 to Py3 to run into things that give back an object reference instead of what you were used to getting.

That said, for me at least, there's too much information omitted in your snips to be able to tell more.

_______________________________________________
Scons-users mailing list
Scons-users at scons.org
https://urldefense.com/v3/__https://pairlist4.pair.net/mailman/listinfo/scons-users__;!!Aa6LgkyVeQ!8BgfgCYFWmA1R2JP-PtcIlEc4rRggeZDeTW39cFGrl9cGviuJeRr8AK7YGehQVimtEktW-iD$