Re: Wacky crash in Clone()
Marc Branchaud via Scons-users <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Organization | XipLink |
| Message-ID | <[email protected]> |
On 2022-01-21 17:43, Mats Wichmann wrote: > On 1/21/22 14:39, Marc Branchaud via Scons-users wrote: >> >> The code is basically structured as follows. The custom builder >> uses functions from a "BaseBuilder" module defined in site_scons. >> (I've elided a lot of setup work in the real code, which is >> sprinkled among several different files, many of which are exec()'d >> by the SConstruct. I'm trying not to suspect the reliance on exec() >> to split up what would otherwise be a giant SConstruct file.) > > that has a bit of a smell to it... why would you need to exec things > manually? things that need to do setup can go in site_scons, and > SCons will arrange to pull them in. Yes, smelly. It's really just a literal breaking-up of the overall SConstruct into different parts, and historically different parts were exec'd depending on what was being built. At this point it's an if-it-ain't-broke situation. > My faulty memory is telling me we heard about something like this > fairly recently, where something doesn't get set up right in an > OverrideEnvironment. Might take a little bit of prospecting to find > that, if indeed it was related (which is hard to tell from your > example, since the example works). Hopefully the problem is just Cloning inside an Action. M.