Repository navigation
Expansions not working for 'includes' list items? #130
Description
I noticed if I try any kind of expansion (e.g. command or variable) in 'includes' list items, they don't get expanded or replaced but gyp instead tries to use them literally.
Am I doing something wrong, is this intentional, or is it a bug?
Activity
mscdex commentedon Oct 14, 2021
Additionally it seems that
'includes'is eagerly evaluated, even before any dependency targets are executed. This is a problem for me since I have a dependency target that generates an include file for the main target. Is there a way around this?targos commentedon Oct 14, 2021
I'm not sure you're going to find someone who knows the answers to your questions.
This repository is not actively developed and we are just making our best to keep it working for Node.js and node-gyp.
Is there a specific reason you have for still using gyp instead of other systems like CMake to build addons?
mscdex commentedon Oct 14, 2021
Because gyp is bundled with node/node-gyp and people complain about needing to install things like cmake or other utilities to build addon dependencies and/or node addons themselves. All I'm trying to do is execute some build-time checks (a la autoconf) to generate some gyp output and include that and so far I haven't found any real way to do that within gyp.