You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 4, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 4, 2020. It is now read-only.
Assess variables to emit in generated config.gypi #71
I'm not a python guy. I just took it because we have it in DEPS anyways. I found replacing stuff in a template easier to read than programmatically altering an object like Node.js' configure script does.
Activity
hashseed commentedon Feb 2, 2019
I implemented a way to generate
config.gypiusing a Jinja2 template here to fix Node.js tests failures.nornagon commentedon Feb 4, 2019
Hm, jinja2 is an odd choice.
config.gypiis just a python data structure, sorepr()should be sufficient, no?hashseed commentedon Feb 4, 2019
I'm not a python guy. I just took it because we have it in DEPS anyways. I found replacing stuff in a template easier to read than programmatically altering an object like Node.js' configure script does.