From 847793d31b2ee057dd9f069c5d354063396aff3b Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 9 Sep 2020 07:31:47 +0200 Subject: Expand notes on issues with build system modules that require bootstrap --- libbuild2/module.cxx | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'libbuild2') diff --git a/libbuild2/module.cxx b/libbuild2/module.cxx index bb471a4..11b32cb 100644 --- a/libbuild2/module.cxx +++ b/libbuild2/module.cxx @@ -283,6 +283,12 @@ namespace build2 // places other than the default options file) we would have to propagate // things explicitly. So for now the thinking is that one shouldn't write // such tests except in controlled cases (e.g., module's *-tests). + // + // And another case is the bdep-sync hook which also doesn't have the + // global overrides propagated to it. + // + // It does feel right to propagate global overrides to all the nested + // build system invocations. Maybe we should set an environment variable? module_load_function* r (nullptr); -- cgit v1.1