First of all, thanks a lot for tackling all of modern C++ building/packaging issues and for tremendous effort put into this project!

This is the first build system since Make that gave me hope for a better tomorrow. However, I'm questioning some decisions and I'd like to discuss/clarify them or find out how to achieve something closest to my desired project setup.

After running bdep new -l c++,cpp -t lib,split libproject, the project looks like this:

> tree -a -I .git* libproject
libproject/
├── .bdep
│   └── bdep.sqlite3
├── build
│   ├── bootstrap.build
│   ├── export.build
│   └── root.build
├── buildfile
├── include
│   └── libproject
│       ├── buildfile
│       ├── export.hpp
│       ├── project.hpp
│       └── version.hpp.in
├── manifest
├── README.md
├── repositories.manifest
├── src
│   └── libproject
│       ├── buildfile
│       └── project.cpp
└── tests
    ├── basics
    │   ├── buildfile
    │   └── driver.cpp
    ├── build
    │   ├── bootstrap.build
    │   └── root.build
    └── buildfile

There is quite a lot of clutter for this simplest project that I find quite unappealing.

1. build directory is traditionally used for the output of the build systems and it's quite misleading and unexpected to find it to be a config directory for build2. In my opinion, much better name for it would be build_config, build2_config or something along the line. What do you think?

2. I have read in the documentaiton that creating build configurations/output anywhere inside of project is forbidden, but I still don't understand why? It's one thing to forbid build configurations to be mixed with code, but I don't see any reason nor limitation not to have build/{gcc,clang++,...} configurations/output inside of self-contained project.

3. There are just too many "config" files scattered across the project, does it has to be that way? Can't we group everything except buildfiles in (hidden) directorires to reduce the clutter?

4. Public include directory contains 3 generated headers just for the build system. Do they have to be there for the installation (probably only for Windows)? If yes, can we name them differently to distinguish them and ignore for non-Windows platforms? If no, I would prefer to have configuration inside of some buildfile for that and expect build2 to provide them for Windows builds.

5. I get that build2's targets are directories and that's probably why each directory that has anything user-created also has buildfile and even additional configuration for it. I assume this is done to give full control to the users who want for each directory to do different kind of magic and that's fine. However, I'm wondering if these things could be done from top-level configuration in one place rather than having build files all over the project? Can this be achieved by something like Make's target-specific variables (and in case of build2, target-specific configuration)?

For the reference, I would prefer following project structure:

ideal_libproject
├── README.md
├── include                                  # Public module interfaces ready for installation (with minimal clearly distinguished clutter).
│   └── ideal_libproject
│       ├── ideal_libproject.mpp
│       └── ...
├── src                                      # Source code for library and its tests.
│   ├── ideal_libproject
│   │   ├── ideal_libproject.cpp
│   │   └── ...
│   └── tests                                # Tests should probably follow same project structure if we want incremental testing.
│       ├── unit
│       │   ├── ideal_libproject_test.cpp
│       │   └── ...
│       └── ...
├── buildfile                                # Top-level configuration that describes rules for project subdirectories as well.
├── build2_config                            # Whole project/repository configuration.
│   ├── .hidden_build2_stuff                 # Hidden part of build2 stuff that shouldn't be touched.
│   │   └── ...
│   └── ...
└── build                                    # Build configurations for the project.
    ├── gcc
    │   └── ...                              # Should not contain "recursive" `build` and optionally top-level `ideal_libproject` directories.
    └── ...

Sorry for dumping all the questions/ideas like this! It would be nice if you can help me understand what is reasonable (and already configurable) to expect and what isn't (and why). Also, I don't mind helping out with the implementation.

I have a project with three packages:

[~/src/atomic_queue] $ tree
.
├── benchmark
│   ├── benchmark
│   │   ├── benchmark.cxx
│   │   ├── buildfile
│   │   └── moodycamel.hxx
│   ├── build
│   │   ├── bootstrap
│   │   │   └── out-root.build
│   │   ├── bootstrap.build
│   │   └── root.build
│   ├── buildfile
│   └── manifest
├── libatomic_queue
│   ├── build
│   │   ├── bootstrap
│   │   │   └── out-root.build
│   │   ├── bootstrap.build
│   │   ├── export.build
│   │   └── root.build
│   ├── buildfile
│   ├── libatomic_queue
│   │   ├── atomic_queue.cxx
│   │   ├── atomic_queue.hxx
│   │   ├── atomic_queue_mutex.hxx
│   │   ├── barrier.hxx
│   │   ├── buildfile
│   │   ├── cpu_base_frequency.cxx
│   │   ├── cpu_base_frequency.hxx
│   │   ├── defs.hxx
│   │   ├── export.hxx
│   │   ├── spinlock.hxx
│   │   └── version.hxx.in
│   └── manifest
├── LICENSE
├── Makefile
├── packages.manifest
├── README.md
├── repositories.manifest
├── test
│   ├── build
│   │   ├── bootstrap
│   │   │   └── out-root.build
│   │   ├── bootstrap.build
│   │   └── root.build
│   ├── buildfile
│   ├── manifest
│   └── test
│       ├── buildfile
│       └── test.cxx
└── buildfile

I would like b to build all packages when invoked from the top level project directory. When I add a buildfile to the top level directory with the following content:

./: {*/ -build/} doc{README.md LICENSE}

And run b it dumps core:

[~/src/atomic_queue] $ b --version
build2 0.11.0
libbutl 0.11.0
host x86_64-linux-gnu
Copyright (c) 2014-2019 Code Synthesis Ltd
This is free software released under the MIT license.

[~/src/atomic_queue] $ cat buildfile 
./: {*/ -build/} doc{README.md LICENSE}

[~/src/atomic_queue] $ b
Segmentation fault (core dumped)

[~/src/atomic_queue] $ mv {,x}buildfile
[~/src/atomic_queue] $ b
error: no buildfile in ./
  info: consider explicitly specifying its src_base

[~/src/atomic_queue] $ cd ../atomic_queue-gcc/
[~/src/atomic_queue-gcc] $ b
mkdir libatomic_queue/fsdir{libatomic_queue/}
mkdir test/fsdir{test/}
mkdir benchmark/fsdir{benchmark/}
version.in ../atomic_queue/libatomic_queue/libatomic_queue/version.hxx.in
c++ ../atomic_queue/libatomic_queue/libatomic_queue/cxx{atomic_queue}@libatomic_queue/libatomic_queue/
c++ ../atomic_queue/libatomic_queue/libatomic_queue/cxx{atomic_queue}@libatomic_queue/libatomic_queue/
c++ ../atomic_queue/libatomic_queue/libatomic_queue/cxx{cpu_base_frequency}@libatomic_queue/libatomic_queue/
c++ ../atomic_queue/libatomic_queue/libatomic_queue/cxx{cpu_base_frequency}@libatomic_queue/libatomic_queue/
c++ ../atomic_queue/benchmark/benchmark/cxx{benchmark}@benchmark/benchmark/
c++ ../atomic_queue/test/test/cxx{test}@test/test/
ar libatomic_queue/libatomic_queue/liba{atomic_queue}
ld libatomic_queue/libatomic_queue/libs{atomic_queue}
ld test/test/exe{test}
ld benchmark/benchmark/exe{benchmark}

Stacktrace:

(gdb) r -V
Starting program: /usr/local/bin/b 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff6803700 (LWP 12432)]
[New Thread 0x7ffff5fb2700 (LWP 12451)]
[New Thread 0x7ffff5761700 (LWP 12452)]

Thread 2 "b" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff6803700 (LWP 12432)]
0x000055555587e944 in butl::project_name const& build2::cast<butl::project_name>(build2::value const&) ()
(gdb) bt
#0  0x000055555587e944 in butl::project_name const& build2::cast<butl::project_name>(build2::value const&) ()
#1  0x000055555587c78b in build2::import(build2::scope&, build2::name, build2::location const&) ()
#2  0x00005555557c3c47 in build2::parser::parse_import(build2::token&, build2::token_type&) ()
#3  0x00005555557cd425 in build2::parser::parse_clause(build2::token&, build2::token_type&, bool) ()
#4  0x00005555557ce959 in build2::parser::parse_buildfile(std::istream&, butl::basic_path<char, butl::any_path_kind<char> > const&, build2::scope&, build2::scope&) ()
#5  0x00005555558769cb in build2::source(build2::scope&, build2::scope&, butl::basic_path<char, butl::any_path_kind<char> > const&, bool) ()
#6  0x0000555555876d90 in build2::source_once(build2::scope&, build2::scope&, butl::basic_path<char, butl::any_path_kind<char> > const&, build2::scope&) ()
#7  0x00005555556f28ff in build2::dir_search(build2::target const&, build2::prerequisite_key const&) ()
#8  0x0000555555839a5d in build2::search(build2::target const&, build2::prerequisite_key const&) ()
#9  0x000055555565db9b in build2::search(build2::target const&, build2::prerequisite const&) ()
#10 0x000055555583f83b in build2::match_prerequisites(build2::action, build2::target&, std::function<build2::prerequisite_target (build2::action, build2::target const&, build2::prerequisite const&, build2::include_type)> const&, build2::scope const*) ()
#11 0x0000555555845582 in build2::alias_rule::apply(build2::action, build2::target&) const ()
#12 0x000055555583a20d in build2::apply_impl(build2::action, build2::target&, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::reference_wrapper<build2::rule const> > const&) ()
#13 0x000055555583b8a5 in build2::match_impl(build2::target_lock&, bool, bool) ()
#14 0x000055555583bb28 in build2::match(build2::action, build2::target const&, unsigned long, std::atomic<unsigned long>*, bool)::{lambda(build2::diag_frame const*, build2::target_lock const*, build2::target&, unsigned long)#1}::operator()(build2::diag_frame const*, build2::target_lock const*, build2::target&, unsigned long) const ()
#15 0x000055555583bc33 in void build2::scheduler::task_thunk<build2::match(build2::action, build2::target const&, unsigned long, std::atomic<unsigned long>*, bool)::{lambda(build2::diag_frame const*, build2::target_lock const*, build2::target&, unsigned long)#1}, build2::diag_frame const*&, build2::target_lock const*&, std::reference_wrapper<build2::target>, unsigned long&>(build2::scheduler&, std::unique_lock<std::mutex>&, void*) ()
#16 0x00005555557eece1 in build2::scheduler::helper(void*) ()
#17 0x00007ffff773f6db in start_thread (arg=0x7ffff6803700) at pthread_create.c:463
#18 0x00007ffff6ec788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

(gdb) info registers
rax            0x7ffff67fc5a0	140737328956832
rbx            0x7ffff67fcf30	140737328959280
rcx            0x0	0
rdx            0x0	0
rsi            0x5f626173	1600282995
rdi            0x0	0
rbp            0x7ffff67ff0e0	0x7ffff67ff0e0
rsp            0x7ffff67fc3d0	0x7ffff67fc3d0
r8             0x0	0
r9             0x555555b622a0	93824998580896
r10            0x7ffff00008d0	140737219922128
r11            0x5555558c6bd4	93824995847124
r12            0x555555b636c8	93824998586056
r13            0x555555b636d8	93824998586072
r14            0x7ffff67fc5a0	140737328956832
r15            0x7ffff67fcd10	140737328958736
rip            0x55555587e944	0x55555587e944 <butl::project_name const& build2::cast<butl::project_name>(build2::value const&)+4>
eflags         0x10202	[ IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
(gdb) disassemble
Dump of assembler code for function _ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE:
   0x000055555587e940 <+0>:	sub    $0x8,%rsp
=> 0x000055555587e944 <+4>:	cmpb   $0x0,0x8(%rdi)
   0x000055555587e948 <+8>:	jne    0x55555587e9b9 <_ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE+121>
   0x000055555587e94a <+10>:	mov    (%rdi),%rdx
   0x000055555587e94d <+13>:	test   %rdx,%rdx
   0x000055555587e950 <+16>:	je     0x55555587e96e <_ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE+46>
   0x000055555587e952 <+18>:	lea    0x2b65e7(%rip),%rcx        # 0x555555b34f40 <_ZN6build212value_traitsIN4butl12project_nameEE10value_typeE>
   0x000055555587e959 <+25>:	cmp    %rcx,%rdx
   0x000055555587e95c <+28>:	jne    0x55555587e965 <_ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE+37>
   0x000055555587e95e <+30>:	jmp    0x55555587e990 <_ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE+80>
   0x000055555587e960 <+32>:	cmp    %rcx,%rdx
   0x000055555587e963 <+35>:	je     0x55555587e990 <_ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE+80>
   0x000055555587e965 <+37>:	mov    0x10(%rdx),%rdx
   0x000055555587e969 <+41>:	test   %rdx,%rdx
   0x000055555587e96c <+44>:	jne    0x55555587e960 <_ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE+32>
   0x000055555587e96e <+46>:	lea    0x4a36b(%rip),%rcx        # 0x5555558c8ce0 <_ZZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueEE19__PRETTY_FUNCTION__>
   0x000055555587e975 <+53>:	mov    $0x9d,%edx
   0x000055555587e97a <+58>:	lea    0x20b4f(%rip),%rsi        # 0x55555589f4d0
   0x000055555587e981 <+65>:	lea    0x20c2f(%rip),%rdi        # 0x55555589f5b7
   0x000055555587e988 <+72>:	callq  0x5555555c36e0 <__assert_fail@plt>
   0x000055555587e98d <+77>:	nopl   (%rax)
   0x000055555587e990 <+80>:	mov    (%rdi),%rax
   0x000055555587e993 <+83>:	cmpq   $0x0,0x58(%rax)
   0x000055555587e998 <+88>:	je     0x55555587e9b0 <_ZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueE+112>
   0x000055555587e99a <+90>:	mov    (%rdi),%rax
   0x000055555587e99d <+93>:	lea    0x2b659c(%rip),%rsi        # 0x555555b34f40 <_ZN6build212value_traitsIN4butl12project_nameEE10value_typeE>
   0x000055555587e9a4 <+100>:	mov    0x58(%rax),%rax
   0x000055555587e9a8 <+104>:	add    $0x8,%rsp
   0x000055555587e9ac <+108>:	jmpq   *%rax
   0x000055555587e9ae <+110>:	xchg   %ax,%ax
   0x000055555587e9b0 <+112>:	lea    0x10(%rdi),%rax
   0x000055555587e9b4 <+116>:	add    $0x8,%rsp
   0x000055555587e9b8 <+120>:	retq   
   0x000055555587e9b9 <+121>:	lea    0x4a320(%rip),%rcx        # 0x5555558c8ce0 <_ZZN6build24castIN4butl12project_nameEEERKT_RKNS_5valueEE19__PRETTY_FUNCTION__>
   0x000055555587e9c0 <+128>:	mov    $0x95,%edx
   0x000055555587e9c5 <+133>:	lea    0x20b04(%rip),%rsi        # 0x55555589f4d0
   0x000055555587e9cc <+140>:	lea    0x3087b(%rip),%rdi        # 0x5555558af24e
   0x000055555587e9d3 <+147>:	callq  0x5555555c36e0 <__assert_fail@plt>
End of assembler dump.

I can manually build a simple c++ modules TS project with my clang++ (7.0.0 trunk), but when i try to use build2 b command it prints "compiler does not support modules" message.

$ clang++ --version
clang version 7.0.0- (trunk)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

What can be wrong?

To enable modules support I added following lines to root buildfile:

cxx.std = experimental

using cxx

assert $cxx.features.modules 'compiler does not support modules'

mxx{*}: extension = mxx
cxx{*}: extension = cxx

bdep --version
bdep 0.14.0
libbpkg 0.14.0
libbutl 0.14.0

I'm seeing this issue (scroll to bottom) when using the build2 ci on virtually all builds.

I created a new project using bdep new -l c++ -t lib [...]. I diffed it against another build2 project I have (which works fine) and really the only two noteworthy differences are that the former has hxx{export}@./: cxx.importable = false specified (which was autogenerated by bdep v0.14, and I tried removing it to no success), but also it has some more files under it's ./tests subfolder (again, autogenerated). I suspect the tests diff is the trigger in this newer project since it does specify import libs = threadable%lib{threadable}.

Unrelated question undefined reference to 'pthread_create' Any tip on how to (using build2 practices) correctly setup so that consumers (including tests) link pthread (supporting gcc, clang, clang-apple, clang-emscripten etc)? Getting confused by -pthread & -lpthread, which goes to cxx.coptions or cxx.loptions or cxx.libs etc (google is not super clear, and want to avoid spamming the ci).

Thanks in advance!

Context

Consider a simple project with two libraries and an executable.

# Root dependency library buildfile

lib{libA}: include/{hxx}{**}

lib{libA}:
{
  cxx.export.poptions += "-I$src_base"
}

# Intermediate library buildfile

intf_libs = # Interface dependencies.

import intf_libs += lib{libA}

lib{libB}: $intf_libs

lib{libB}:
{
  cxx.export.poptions += "-I$src_base"
  cxx.export.libs = $intf_libs
}

# Consuming executable buildfile

impl_libs = # Implementation dependencies.

import impl_libs += lib{libA} lib{libB}

exe{example}: {cxx}{example} $impl_libs

Observed

The output from b --verbose=4 shows the following (simplified) commandline. Note that the include path exported by libA is duplicated due to the combination of direct and transitive dependency. clang++ -IX:/.../libA -IX:/.../libB -IX:/.../libA

Expected

Ideally, redundant duplicated options should be removed to simplify the command lines. With a number of interdependent libraries, with some libraries occurring as both direct and indirect dependencies of many others, the command line will explode exponentially; even to the point of causing the compiler invocation to fail.

Suggestion

There would appear to be two distinct levels at which this could be addressed, perhaps ideally both should be, but the first seems a priority:

• Remove duplicate library dependencies I couldn't deduce much from a first look at the code so am not clear on the process of variable concatenation with library imports. However, conceptually it would seem to make sense to just accumulate the list of dependencies, which could be done in such a way as to avoid duplicates, and only expand and append their exported variables at the last step, when needed. This seems cleaner than trying to remove redundancies at the level of raw option strings.
• Remove duplicate options While the above should fix the issue for include paths, other options are not library-specific and therefore can still end up duplicated. So it would be nice to have duplicate removal at the options string level too. This may be less trivial, however, since it's not clear that duplicate entries are necessarily always redundant?

dup-poptions-repro.zip

Error building a new project on Fedora

Any help in helping me understand the issue would be greatly appreciated. (Didn't know what to title the issue so feel free to change it.)

Environment

b|2 build2 0.13.0-a.0.2756e66940d1 libbutl 0.13.0-a.0.2c67d8c6bb8d host x86_64-redhat-linux

Note that I first tried version 0.12.0 (installed using dnf) as well and got the same symptoms. Decided to try out the staged version before digging in further.

Compiler g++ (GCC) 10.1.1 20200507 (Red Hat 10.1.1-1)

Operating system Fedora 32. A fresh install.

Setup

Followed the instruction on the main page to create the project and build configuration.

$ bdep new -t exe -l c++ hello
$ cd hello
$ bdep init -C ../hello-gcc cc config.cxx=g++

Then built using b. Which resulted in an error log of about 4.7k lines. Will only post an exert of the logs for now hoping it might be enough.

c++ hello/cxx{hello}@../hello-gcc/hello/hello/
In file included from /usr/include/c++/10/bits/exception_ptr.h:39,
                 from /usr/include/c++/10/exception:147,
                 from /usr/include/c++/10/ios:39,
                 from /usr/include/c++/10/ostream:38,
                 from /usr/include/c++/10/iostream:39,
                 from /home/cairns/workspace/hello/hello/hello.cxx:1:
/usr/include/c++/10/typeinfo:76:5: error: stray ‘#’ in program
   76 |     #define __GXX_TYPEINFO_EQUALITY_INLINE 1
      |     ^
In file included from /usr/include/c++/10/iostream:38,
                 from /home/cairns/workspace/hello/hello/hello.cxx:1:
/usr/include/c++/10/x86_64-redhat-linux/bits/c++config.h:2355:11: error: ‘__SIZE_TYPE__’ does not name a type
 2355 |   typedef __SIZE_TYPE__  size_t;
      |           ^~~~~~~~~~~~~
/usr/include/c++/10/x86_64-redhat-linux/bits/c++config.h:2356:11: error: ‘__PTRDIFF_TYPE__’ does not name a type
 2356 |   typedef __PTRDIFF_TYPE__ ptrdiff_t;
      |           ^~~~~~~~~~~~~~~~

...

/usr/include/c++/10/initializer_list:47:11: fatal error: definition of ‘class std::initializer_list<_E>’ does not match ‘#include <initializer_list>’
   47 |     class initializer_list
      |           ^~~~~~~~~~~~~~~~
compilation terminated.
info: failed to update ../hello-gcc/dir{hello/}

Debugging

Attempt Nr. 1

To verify that something wasn't wrong with my environment I decided to compile the file alone. Which turned out to work.

$ cd ..
$ mkdir test
$ cd test
$ cp ../hello/hello/hello.cxx test.cxx
$ g++ test.cxx -o test
$ ./test World
Hello, World!

Attempt Nr. 2

I was then wondering if b wasn't using the correct compiler or some other environmental variable so increased the verbosity.

$ cd ../hello
$ b -v
bpkg -v build -d /home/cairns/workspace/hello-gcc --no-fetch --configure-only --keep-out --plan "synchronizing /home/cairns/workspace/hello-gcc/:" --yes hello@/home/cairns/workspace/hello
g++ -I/home/cairns/workspace/hello-gcc/hello -I/home/cairns/workspace/hello -std=c++2a -o ../hello-gcc/hello/hello/hello.o -c -x c++ /home/cairns/workspace/hello/hello/hello.cxx
...

The rest of the logs where the exact same as above.

Decided to try the commands manually to see if I might get some other logs that way. To my surprise neither of the commands yielded any errors at all. So I tried building using b after that and it worked.

$ bpkg -v build -d /home/cairns/workspace/hello-gcc --no-fetch --configure-only --keep-out --plan "synchronizing /home/cairns/workspace/hello-gcc/:" --yes hello@/home/cairns/workspace/hello
$ g++ -I/home/cairns/workspace/hello-gcc/hello -I/home/cairns/workspace/hello -std=c++2a -o ../hello-gcc/hello/hello/hello.o -c -x c++ /home/cairns/workspace/hello/hello/hello.cxx
$ b -v
bpkg -v build -d /home/cairns/workspace/hello-gcc --no-fetch --configure-only --keep-out --plan "synchronizing /home/cairns/workspace/hello-gcc/:" --yes hello@/home/cairns/workspace/hello
g++ -std=c++2a -L /usr/local/lib -o ../hello-gcc/hello/hello/hello ../hello-gcc/hello/hello/hello.o
ln -s /home/cairns/workspace/hello-gcc/hello/hello/hello /home/cairns/workspace/hello/hello/hello
$ hello/hello World
Hello, World!

Making any changes and then building again resulted in the original error. While testing combinations of the commands I narrowed it down to that the important line was:

g++ -I/home/cairns/workspace/hello-gcc/hello -I/home/cairns/workspace/hello -std=c++2a -o ../hello-gcc/hello/hello/hello.o -c -x c++ /home/cairns/workspace/hello/hello/hello.cxx

Attempt Nr. 3

Still suspected that something was different with the environment so increased the verbosity further.

$ b -V
git -C /home/cairns/workspace/hello status --porcelain
git -C /home/cairns/workspace/hello cat-file commit HEAD
bdep sync --hook=1 --verbose 3 --config /home/cairns/workspace/hello-gcc
mkdir /tmp/bdep-58563-0/
bpkg --verbose 3 rep-list -d /home/cairns/workspace/hello-gcc
mkdir /home/cairns/workspace/hello-gcc/.bpkg/tmp/
rmdir -r /home/cairns/workspace/hello-gcc/.bpkg/tmp/
bpkg --verbose 3 fetch -d /home/cairns/workspace/hello-gcc --shallow dir:/home/cairns/workspace/hello
mkdir /home/cairns/workspace/hello-gcc/.bpkg/tmp/
b --verbose 3 -s info: '/home/cairns/workspace/hello/'
git -C /home/cairns/workspace/hello status --porcelain
git -C /home/cairns/workspace/hello cat-file commit HEAD
sha256sum --version
info: using 'sha256sum' as the sha256 program, use --sha256 to override
sha256sum -b /home/cairns/workspace/hello/./manifest
1 package(s) in 1 repository(s)
rmdir -r /home/cairns/workspace/hello-gcc/.bpkg/tmp/
bpkg --verbose 3 build -d /home/cairns/workspace/hello-gcc --no-fetch --configure-only --keep-out --plan "synchronizing /home/cairns/workspace/hello-gcc/:" --yes hello@/home/cairns/workspace/hello
mkdir /home/cairns/workspace/hello-gcc/.bpkg/tmp/
rmdir -r /home/cairns/workspace/hello-gcc/.bpkg/tmp/
b --verbose 3 configure: '/home/cairns/workspace/hello/'@'/home/cairns/workspace/hello-gcc/hello/',forward
git -C /home/cairns/workspace/hello status --porcelain
git -C /home/cairns/workspace/hello cat-file commit HEAD
cat >/home/cairns/workspace/hello/build/bootstrap/out-root.build
rmdir -r /tmp/bdep-58563-0/
LC_ALL=C g++ -v
g++ -print-multiarch
g++ -dumpmachine
g++ -x c++ -E -
g++ -x c++ -E -
LC_ALL=C g++ -print-search-dirs
LC_ALL=C g++ -x c++ -v -E -
cxx @/home/cairns/workspace/hello-gcc/
  cxx        g++@/usr/lib64/ccache/g++
  id         gcc
  version    10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)
  major      10
  minor      1
  patch      1
  build      20200507 (Red Hat 10.1.1-1) (GCC)
  signature  gcc version 10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)
  checksum   1be04c9eec935b0c2af11992367e83c0aba213e47a0add3d24d07dd19867536e
  target     x86_64-redhat-linux
  runtime    libgcc
  stdlib     libstdc++
  c stdlib   glibc
  inc dirs
    /usr/include/c++/10/
    /usr/include/c++/10/x86_64-redhat-linux/
    /usr/include/c++/10/backward/
    /usr/lib/gcc/x86_64-redhat-linux/10/include/
    /usr/local/include/
    /usr/include/
  lib dirs
    /usr/lib/gcc/x86_64-redhat-linux/10/
    /usr/x86_64-redhat-linux/lib/x86_64-redhat-linux/10/
    /usr/x86_64-redhat-linux/lib64/
    /usr/lib/x86_64-redhat-linux/10/
    /usr/lib64/
    /lib/x86_64-redhat-linux/10/
    /lib64/
    /usr/x86_64-redhat-linux/lib/
    /usr/lib/
    /lib/
    --
    /usr/local/lib/
bin @/home/cairns/workspace/hello-gcc/
  target     x86_64-redhat-linux
LC_ALL=C ar --version
bin.ar @/home/cairns/workspace/hello-gcc/
  ar         ar@/usr/bin/ar
  id         gnu
  version    2.34.0-3.fc32
  major      2
  minor      34
  patch      0
  build      -3.fc32
  signature  GNU ar version 2.34-3.fc32
  checksum   dce91e0e0bbb68b751b8e51742920d3d10076b51b7e6fc5fb888dfead3efc4cf
LC_ALL=C gcc -v
gcc -print-multiarch
gcc -dumpmachine
gcc -x c -E -
LC_ALL=C gcc -print-search-dirs
LC_ALL=C gcc -x c -v -E -
c @/home/cairns/workspace/hello-gcc/
  c          gcc@/usr/lib64/ccache/gcc
  id         gcc
  version    10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)
  major      10
  minor      1
  patch      1
  build      20200507 (Red Hat 10.1.1-1) (GCC)
  signature  gcc version 10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)
  checksum   10adf4494d036626a3d072d0d78f6118d7f4759500d6f28f519f02d584fc3b80
  target     x86_64-redhat-linux
  runtime    libgcc
  stdlib     glibc
  inc dirs
    /usr/lib/gcc/x86_64-redhat-linux/10/include/
    /usr/local/include/
    /usr/include/
  lib dirs
    /usr/lib/gcc/x86_64-redhat-linux/10/
    /usr/x86_64-redhat-linux/lib/x86_64-redhat-linux/10/
    /usr/x86_64-redhat-linux/lib64/
    /usr/lib/x86_64-redhat-linux/10/
    /usr/lib64/
    /lib/x86_64-redhat-linux/10/
    /lib64/
    /usr/x86_64-redhat-linux/lib/
    /usr/lib/
    /lib/
    --
    /usr/local/lib/
LC_ALL=C g++ -std=c++2a -print-search-dirs
LC_ALL=C g++ -std=c++2a -x c++ -v -E -
cxx hello@/home/cairns/workspace/hello-gcc/hello/
  cxx        g++@/usr/lib64/ccache/g++
  id         gcc
  version    10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)
  major      10
  minor      1
  patch      1
  build      20200507 (Red Hat 10.1.1-1) (GCC)
  signature  gcc version 10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)
  checksum   1be04c9eec935b0c2af11992367e83c0aba213e47a0add3d24d07dd19867536e
  target     x86_64-redhat-linux
  runtime    libgcc
  stdlib     libstdc++
  c stdlib   glibc
  std        -std=c++2a
  inc dirs
    /usr/include/c++/10/
    /usr/include/c++/10/x86_64-redhat-linux/
    /usr/include/c++/10/backward/
    /usr/lib/gcc/x86_64-redhat-linux/10/include/
    /usr/local/include/
    /usr/include/
  lib dirs
    /usr/lib/gcc/x86_64-redhat-linux/10/
    /usr/x86_64-redhat-linux/lib/x86_64-redhat-linux/10/
    /usr/x86_64-redhat-linux/lib64/
    /usr/lib/x86_64-redhat-linux/10/
    /usr/lib64/
    /lib/x86_64-redhat-linux/10/
    /lib64/
    /usr/x86_64-redhat-linux/lib/
    /usr/lib/
    /lib/
    --
    /usr/local/lib/
bin hello@/home/cairns/workspace/hello-gcc/hello/
  target     x86_64-redhat-linux
LC_ALL=C ar --version
bin.ar hello@/home/cairns/workspace/hello-gcc/hello/
  ar         ar@/usr/bin/ar
  id         gnu
  version    2.34.0-3.fc32
  major      2
  minor      34
  patch      0
  build      -3.fc32
  signature  GNU ar version 2.34-3.fc32
  checksum   dce91e0e0bbb68b751b8e51742920d3d10076b51b7e6fc5fb888dfead3efc4cf
g++ -I/home/cairns/workspace/hello-gcc/hello -I/home/cairns/workspace/hello -std=c++2a -x c++ -MQ ^ -MD -E -fdirectives-only -MF /home/cairns/workspace/hello-gcc/hello/hello/hello.o.t -o /home/cairns/workspace/hello-gcc/hello/hello/hello.o.ii /home/cairns/workspace/hello/hello/hello.cxx
g++ -I/home/cairns/workspace/hello-gcc/hello -I/home/cairns/workspace/hello -std=c++2a -E -x c++ -fpreprocessed -fdirectives-only /home/cairns/workspace/hello-gcc/hello/hello/hello.o.ii
g++ -I/home/cairns/workspace/hello-gcc/hello -I/home/cairns/workspace/hello -std=c++2a -o ../hello-gcc/hello/hello/hello.o -c -fdirectives-only /home/cairns/workspace/hello-gcc/hello/hello/hello.o.ii
...

Turned out that the commands aren't quite the same with it split into three parts. Running them manually the first part doesn't log anything. The second produced a massive blob that looks like the final code. The third produces the errors as expected.

Now I don't know how to proceed which is why I'm reaching out for help.

I didn't manage to reproduce this with a simpler case for now (lack of time, I'll try to do more soon). I don't think it's relative to the actual library used, but that's how I got there.

How to reproduce:

0. On Windows, with build2 v0.11.0, using msvc 16.1 (used for all the following and the build2 install).
1. build and install boost 1.69.0 somewhere on the disk (using b2) (or mayb just download a binary package? I didn't try that yet)
2. Add a pkg-config file for boost in the lib/pkgconfig directory of your boost install. Here is what I used: https://pastebin.com/7A01nCw7
3. bdep new boostuser && cd boostuser
4. Add depends: libboost >= 1.69.0 in manifest.
5. Create the configuration this way, just replace the paths to boost install (yep, this is weird):

bdep init ?sys:libboost/* -C ../build-boostuser cc config.cxx.loptions="/LIBPATH:G:\tools\boost\boost_install\lib" config.cxx.poptions="/I G:\tools\boost\boost_install\include\boost-1_69"

This leads to an error because for some reason ?sys:libboost/* is ignored even if put at the end of the line. (see #39 )

6. Insist again: bdep init ?sys:libboost/* => lead to the error

Observed:

PS G:\tmp\test_build2_unpackaged\boostuser> bdep init ?sys:libboost/* -C ../build-boostuser cc config.cxx.loptions="/LIBPATH:G:\tools\boost\boost_install\lib" config.cxx.poptions="/I G:\tools\boost\boost_install\include\boost-1_69"   initializing in project G:\tmp\test_build2_unpackaged\boostuser\
created configuration G:\tmp\test_build2_unpackaged\build-boostuser\ 1 default,forwarded,auto-synchronized
error: unknown dependency libboost >= 1.69.0 of package boostuser
  info: repository dir+file:///G:/tmp/test_build2_unpackaged/boostuser appears to be broken
  info: or the repository state could be stale
  info: run 'bpkg rep-fetch' to update
info: while satisfying boostuser/0.1.0-a.0.19700101000000
PS G:\tmp\test_build2_unpackaged\boostuser> bdep init ?sys:libboost/*                                                initializing in project G:\tmp\test_build2_unpackaged\boostuser\
synchronizing:
  configure sys:libboost/*
  new boostuser/0.1.0-a.0.19700101000000
error: process b terminated abnormally: stack buffer overrun

With --verbose 4 : https://pastebin.com/zGWukPx0

I recently realized I'd been building a number of libs in both static and shared mode, despite only needing to consume them as shared. I modified build/config.build in my configuration to specify config.bin.lib = shared, and set config.bin.lib = static in the config.build of one specific package. These combined changes have resulted in the following output from b update:

trace: create_new_target: new target C:\Kantan\build\msvc-debug-asan\kantan\kantan\component-core\source\dbg\obj{visualizer_state} for prerequisite C:\Kantan\build\msvc-debug-asan\kantan\kantan\component-core\source\dbg\obj{visualizer_state}
Assertion failed: m != nullptr, file C:\build2\build\build2-toolchain-0.15-a.0\build2-0.15.0-a.0.20220511070701.53234fea9cd6\libbuild2\algorithm.cxx, line 354

I'll try to update to the latest staged toolchain soon, but let me know if there's any other tests I could do to provide some more information.

in libpkgconf-1.6.3+4\libpkgconf\config.h.in version.in libbutl-0.13.0\libbutl\version.hxx.in version.in libodb-sqlite-2.5.0-b.19\odb\sqlite\version-build2.hxx.in version.in libodb-2.5.0-b.19\odb\version-build2.hxx.in in build2-0.13.0\libbuild2\config.hxx.in version.in libbpkg-0.13.0\libbpkg\version.hxx.in version.in build2-0.13.0\libbuild2\version.hxx.in C:\Users\Documents\build2\build2-toolchain-0.13\bdep-0.13.0\bdep\new-options.cxx(3617): error C2220: C:\Users\Documents\build2\build2-toolchain-0.13\bdep-0.13.0\bdep\new-options.cxx(3617): warning C4819

Output

> bpkg fetch
fetching dir:D:\Coding\Kantan\kantan-build2
[various prerequisite fetches here]
fetching dir:D:\coding\kantan\build2-repro
fetching dir:D:\coding\kantan\kantan-build2
error: external package kantan/0.1.0 is available from two repositories
  info: repository dir+file:///D:/Coding/Kantan/kantan-build2
  info: repository dir+file:///D:/coding/kantan/kantan-build2
warning: repository state is now broken and will be cleaned up
  info: run 'bpkg rep-fetch' to update

> bpkg list
dir:D:\Coding\Kantan\kantan-build2 dir+file:///D:/Coding/Kantan/kantan-build2
dir:D:\coding\kantan\build2-repro dir+file:///D:/coding/kantan/build2-repro
dir:D:\coding\kantan\kantan-build2 dir+file:///D:/coding/kantan/kantan-build2

Further info/questions

I'm on Windows 10, and using Powershell. It's not clear precisely what sequence of actions leads to this, though it has happened a number of times, mostly after adding a new external git prerequisite to my project's repositories.manifest and then trying to update. I'm also reasonably confident that at no point would I have directly typed the lower case version of the above paths in any command.

Two other minor things:

• Does external package have some specific meaning in the above output? It seems a little strange to me since this is a package that lives inside the project repository.
• The diagnostic's suggestion to run the exact same command that just gave the error is a little confusing!

When compiling, b attempts to scan every cpp file in an external non-build2 dependency (which is only included via -I), and it incorrectly throws the error:

…/opt/ace/build/x86_64-apple-darwin/ace/Task_T.cpp:101:43: error: module name expected instead of <punctuation>
  info: while scanning …/RACM_Interfc/cxx{RACM_Utils.cpp}

while scanning this line:

template<ACE_SYNCH_DECL, class TIME_POLICY> ACE_Module<ACE_SYNCH_USE, TIME_POLICY> *
ACE_Task<ACE_SYNCH_USE, TIME_POLICY>::module (void) const
{
  ACE_TRACE ("ACE_Task<ACE_SYNCH_USE, TIME_POLICY>::module");
  return this->mod_;
}

It's incorrectly recognizing module as a keyword. I have cxx.std = c++14 in my root.build. How do I stop this?

This pull request primarily adds the constexpr specifier to identifiers in action.hxx and includes a minor improvement by replacing the explicit action constructor with an initializer list for improved readability and maintainability.

When cloning build2 on Windows ( with the appropriate bootstrapped environments already configured ), some rules won't be able to proceed. Ignoring the doc/ directory will proceed properly.

error: no rule to update doc\man1{b}
  info: target doc\man1{b} is not declared in any buildfile
  info: perhaps it is a missing source file?
  info: re-run with --verbose=4 for more information
  info: while applying rule build.alias to update dir{doc\}
  info: while applying rule build.alias to update dir{.\}
error: no rule to update doc\xhtml{b}
  info: target doc\xhtml{b} is not declared in any buildfile
  info: perhaps it is a missing source file?
  info: re-run with --verbose=4 for more information
  info: while applying rule build.alias to update dir{doc\}
  info: while applying rule build.alias to update dir{.\}
error: no rule to update doc{INSTALL}
  info: target doc{INSTALL} is implicitly declared in a buildfile
  info: re-run with --verbose=4 for more information
  info: while applying rule build.alias to update dir{.\}

Ignoring the build directory will allow build2 to build correctly:

# file      : buildfile
# license   : MIT; see accompanying LICENSE file

./: {*/ -build/ -config/ -old-tests/ -doc/}                    \
    doc{NEWS README} legal{LICENSE AUTHORS}      \
    file{INSTALL.cli bootstrap* config.guess config.sub} \
    manifest

# Don't install tests or the INSTALL file.
#
tests/:          install = false
doc{INSTALL}@./: install = false

> b
c++ libbuild2\cxx{utility-uninstalled} -> libbuild2\objs{utility-uninstalled}
c++ libbuild2\cxx{utility-uninstalled} -> libbuild2\obje{utility-uninstalled}
c++ libbuild2\cxx{scheduler.test} -> libbuild2\obje{scheduler.test}
c++ libbuild2\cxx{name.test} -> libbuild2\obje{name.test}
c++ libbuild2\test\script\cxx{parser.test} -> libbuild2\test\script\obje{parser.test}
c++ libbuild2\in\cxx{target} -> libbuild2\in\objs{target}
c++ libbuild2\cxx\cxx{target} -> libbuild2\cxx\objs{target}
c++ libbuild2\cxx{make-parser.test} -> libbuild2\obje{make-parser.test}
c++ tests\test\simple\generated\cxx{driver} -> tests\test\simple\generated\obje{driver}
c++ libbuild2\cxx{lexer.test} -> libbuild2\obje{lexer.test}
c++ libbuild2\c\cxx{init} -> libbuild2\c\objs{init}
c++ libbuild2\script\cxx{lexer.test} -> libbuild2\script\obje{lexer.test}
c++ libbuild2\cc\cxx{pkgconfig-libpkg-config} -> libbuild2\cc\objs{pkgconfig-libpkg-config}
c++ libbuild2\cc\cxx{parser.test} -> libbuild2\cc\obje{parser.test}
c++ libbuild2\version\cxx{utility} -> libbuild2\version\objs{utility}
c++ build2\cli\cxx{target} -> build2\cli\obje{target}
ld tests\test\simple\generated\exe{driver}
c++ libbuild2\cxx{function.test} -> libbuild2\obje{function.test}
c++ libbuild2\cc\cxx{windows-rpath} -> libbuild2\cc\objs{windows-rpath}
c++ libbuild2\cxx\cxx{init} -> libbuild2\cxx\objs{init}
c++ libbuild2\cxx{utility-installed} -> libbuild2\objs{utility-installed}
c++ libbuild2\script\cxx{regex.test} -> libbuild2\script\obje{regex.test}
c++ libbuild2\build\script\cxx{lexer.test} -> libbuild2\build\script\obje{lexer.test}
c++ libbuild2\build\script\cxx{parser.test} -> libbuild2\build\script\obje{parser.test}
c++ libbuild2\test\script\cxx{lexer.test} -> libbuild2\test\script\obje{lexer.test}
c++ libbuild2\in\cxx{init} -> libbuild2\in\objs{init}
c++ libbuild2\version\cxx{snapshot} -> libbuild2\version\objs{snapshot}
c++ libbuild2\in\cxx{rule} -> libbuild2\in\objs{rule}
c++ build2\cxx{b} -> build2\obje{b}
c++ build2\cli\cxx{rule} -> build2\cli\obje{rule}
c++ build2\cli\cxx{init} -> build2\cli\obje{init}
c++ libbuild2\version\cxx{init} -> libbuild2\version\objs{init}
c++ libbuild2\version\cxx{module} -> libbuild2\version\objs{module}
c++ libbuild2\config\cxx{utility} -> libbuild2\config\objs{utility}
c++ libbuild2\version\cxx{rule} -> libbuild2\version\objs{rule}
c++ libbuild2\version\cxx{snapshot-git} -> libbuild2\version\objs{snapshot-git}
c++ tests\libbuild2\cxx{driver} -> tests\libbuild2\obje{driver}
c++ libbuild2\bash\cxx{target} -> libbuild2\bash\objs{target}
c++ libbuild2\bash\cxx{init} -> libbuild2\bash\objs{init}
c++ libbuild2\bash\cxx{rule} -> libbuild2\bash\objs{rule}
c++ libbuild2\bin\cxx{utility} -> libbuild2\bin\objs{utility}
c++ libbuild2\cc\cxx{windows-manifest} -> libbuild2\cc\objs{windows-manifest}
c++ libbuild2\bin\cxx{def-rule} -> libbuild2\bin\objs{def-rule}
c++ libbuild2\cc\cxx{common} -> libbuild2\cc\objs{common}
c++ libbuild2\cc\cxx{compile-rule} -> libbuild2\cc\objs{compile-rule}
c++ libbuild2\cc\cxx{functions} -> libbuild2\cc\objs{functions}
c++ libbuild2\bin\cxx{functions} -> libbuild2\bin\objs{functions}
c++ libbuild2\cc\cxx{gcc} -> libbuild2\cc\objs{gcc}
c++ libbuild2\cc\cxx{guess} -> libbuild2\cc\objs{guess}
c++ libbuild2\config\cxx{host-config} -> libbuild2\config\objs{host-config}
c++ libbuild2\cc\cxx{init} -> libbuild2\cc\objs{init}
c++ libbuild2\dist\cxx{init} -> libbuild2\dist\objs{init}
c++ libbuild2\cc\cxx{install-rule} -> libbuild2\cc\objs{install-rule}
c++ libbuild2\cc\cxx{lexer} -> libbuild2\cc\objs{lexer}
c++ libbuild2\bin\cxx{guess} -> libbuild2\bin\objs{guess}
c++ libbuild2\bin\cxx{init} -> libbuild2\bin\objs{init}
c++ libbuild2\bin\cxx{target} -> libbuild2\bin\objs{target}
c++ libbuild2\cc\cxx{utility} -> libbuild2\cc\objs{utility}
c++ libbuild2\bin\cxx{rule} -> libbuild2\bin\objs{rule}
c++ libbuild2\cc\cxx{link-rule} -> libbuild2\cc\objs{link-rule}
c++ libbuild2\cc\cxx{module} -> libbuild2\cc\objs{module}
c++ libbuild2\cc\cxx{msvc} -> libbuild2\cc\objs{msvc}
c++ libbuild2\cc\cxx{parser} -> libbuild2\cc\objs{parser}
c++ libbuild2\cc\cxx{pkgconfig} -> libbuild2\cc\objs{pkgconfig}
c++ libbuild2\cc\cxx{target} -> libbuild2\cc\objs{target}
c++ libbuild2\cc\cxx{types} -> libbuild2\cc\objs{types}
c++ tests\test\config-test\cxx{driver} -> tests\test\config-test\obje{driver}
c++ tests\test\script\runner\cxx{driver} -> tests\test\script\runner\obje{driver}
c++ libbuild2\dist\cxx{module} -> libbuild2\dist\objs{module}
c++ libbuild2\cxx{adhoc-rule-buildscript} -> libbuild2\objs{adhoc-rule-buildscript}
c++ libbuild2\cxx{adhoc-rule-cxx} -> libbuild2\objs{adhoc-rule-cxx}
ld tests\test\config-test\exe{driver}
c++ libbuild2\cxx{adhoc-rule-regex-pattern} -> libbuild2\objs{adhoc-rule-regex-pattern}
c++ libbuild2\cxx{algorithm} -> libbuild2\objs{algorithm}
c++ libbuild2\cxx{b-cmdline} -> libbuild2\objs{b-cmdline}
c++ libbuild2\cxx{buildspec} -> libbuild2\objs{buildspec}
c++ libbuild2\cxx{context} -> libbuild2\objs{context}
c++ libbuild2\cxx{depdb} -> libbuild2\objs{depdb}
ld tests\test\script\runner\exe{driver}
c++ libbuild2\cxx{diagnostics} -> libbuild2\objs{diagnostics}
c++ libbuild2\cxx{dump} -> libbuild2\objs{dump}
c++ libbuild2\cxx{dyndep} -> libbuild2\objs{dyndep}
c++ libbuild2\cxx{file-cache} -> libbuild2\objs{file-cache}
c++ libbuild2\cxx{file} -> libbuild2\objs{file}
c++ libbuild2\cxx{filesystem} -> libbuild2\objs{filesystem}
c++ libbuild2\test\script\cxx{runner} -> libbuild2\test\script\objs{runner}
c++ libbuild2\cxx{function} -> libbuild2\objs{function}
c++ libbuild2\cxx{functions-bool} -> libbuild2\objs{functions-bool}
c++ libbuild2\cxx{functions-builtin} -> libbuild2\objs{functions-builtin}
c++ libbuild2\cxx{functions-filesystem} -> libbuild2\objs{functions-filesystem}
c++ libbuild2\cxx{functions-integer} -> libbuild2\objs{functions-integer}
c++ libbuild2\cxx{functions-name} -> libbuild2\objs{functions-name}
c++ libbuild2\cxx{functions-path} -> libbuild2\objs{functions-path}
c++ libbuild2\cxx{functions-process-path} -> libbuild2\objs{functions-process-path}
c++ libbuild2\cxx{functions-process} -> libbuild2\objs{functions-process}
c++ libbuild2\cxx{functions-project-name} -> libbuild2\objs{functions-project-name}
c++ libbuild2\cxx{functions-regex} -> libbuild2\objs{functions-regex}
c++ libbuild2\cxx{functions-string} -> libbuild2\objs{functions-string}
c++ libbuild2\cxx{functions-target-triplet} -> libbuild2\objs{functions-target-triplet}
c++ libbuild2\cxx{lexer} -> libbuild2\objs{lexer}
c++ libbuild2\cxx{make-parser} -> libbuild2\objs{make-parser}
c++ libbuild2\test\cxx{target} -> libbuild2\test\objs{target}
c++ libbuild2\cxx{module} -> libbuild2\objs{module}
c++ libbuild2\cxx{name} -> libbuild2\objs{name}
c++ libbuild2\cxx{operation} -> libbuild2\objs{operation}
c++ libbuild2\cxx{parser} -> libbuild2\objs{parser}
c++ libbuild2\cxx{prerequisite} -> libbuild2\objs{prerequisite}
c++ libbuild2\cxx{recipe} -> libbuild2\objs{recipe}
c++ libbuild2\cxx{rule} -> libbuild2\objs{rule}
c++ libbuild2\cxx{scheduler} -> libbuild2\objs{scheduler}
c++ libbuild2\cxx{scope} -> libbuild2\objs{scope}
c++ libbuild2\cxx{search} -> libbuild2\objs{search}
c++ libbuild2\cxx{target} -> libbuild2\objs{target}
c++ libbuild2\cxx{token} -> libbuild2\objs{token}
c++ libbuild2\cxx{types-parsers} -> libbuild2\objs{types-parsers}
c++ libbuild2\cxx{utility} -> libbuild2\objs{utility}
c++ libbuild2\cxx{variable} -> libbuild2\objs{variable}
c++ libbuild2\cxx{common-options} -> libbuild2\objs{common-options}
c++ libbuild2\test\script\cxx{token} -> libbuild2\test\script\objs{token}
c++ libbuild2\cxx{b-options} -> libbuild2\objs{b-options}
c++ libbuild2\script\cxx{lexer} -> libbuild2\script\objs{lexer}
c++ libbuild2\script\cxx{parser} -> libbuild2\script\objs{parser}
c++ libbuild2\script\cxx{regex} -> libbuild2\script\objs{regex}
c++ libbuild2\script\cxx{run} -> libbuild2\script\objs{run}
c++ libbuild2\script\cxx{script} -> libbuild2\script\objs{script}
c++ libbuild2\script\cxx{timeout} -> libbuild2\script\objs{timeout}
c++ libbuild2\script\cxx{token} -> libbuild2\script\objs{token}
c++ libbuild2\script\cxx{builtin-options} -> libbuild2\script\objs{builtin-options}
c++ libbuild2\build\script\cxx{lexer} -> libbuild2\build\script\objs{lexer}
c++ libbuild2\test\script\cxx{script} -> libbuild2\test\script\objs{script}
c++ libbuild2\build\script\cxx{parser} -> libbuild2\build\script\objs{parser}
c++ libbuild2\build\script\cxx{runner} -> libbuild2\build\script\objs{runner}
c++ libbuild2\build\script\cxx{script} -> libbuild2\build\script\objs{script}
c++ libbuild2\build\script\cxx{token} -> libbuild2\build\script\objs{token}
c++ libbuild2\build\script\cxx{builtin-options} -> libbuild2\build\script\objs{builtin-options}
c++ libbuild2\config\cxx{functions} -> libbuild2\config\objs{functions}
c++ libbuild2\config\cxx{init} -> libbuild2\config\objs{init}
c++ libbuild2\config\cxx{module} -> libbuild2\config\objs{module}
c++ libbuild2\config\cxx{operation} -> libbuild2\config\objs{operation}
c++ libbuild2\dist\cxx{operation} -> libbuild2\dist\objs{operation}
c++ libbuild2\dist\cxx{rule} -> libbuild2\dist\objs{rule}
c++ libbuild2\install\cxx{functions} -> libbuild2\install\objs{functions}
c++ libbuild2\install\cxx{init} -> libbuild2\install\objs{init}
c++ libbuild2\install\cxx{operation} -> libbuild2\install\objs{operation}
c++ libbuild2\install\cxx{rule} -> libbuild2\install\objs{rule}
c++ libbuild2\install\cxx{utility} -> libbuild2\install\objs{utility}
c++ libbuild2\test\cxx{common} -> libbuild2\test\objs{common}
c++ libbuild2\test\cxx{init} -> libbuild2\test\objs{init}
c++ libbuild2\test\cxx{module} -> libbuild2\test\objs{module}
c++ libbuild2\test\script\cxx{parser} -> libbuild2\test\script\objs{parser}
c++ libbuild2\test\cxx{operation} -> libbuild2\test\objs{operation}
c++ libbuild2\test\cxx{rule} -> libbuild2\test\objs{rule}
c++ libbuild2\test\script\cxx{lexer} -> libbuild2\test\script\objs{lexer}
c++ libbuild2\cc\cxx{lexer.test} -> libbuild2\cc\obje{lexer.test}
ar libbuild2\libus{build2}
ld libbuild2\script\exe{regex.test}
ld libbuild2\script\exe{lexer.test}
ld libbuild2\test\script\exe{lexer.test}
ld libbuild2\build\script\exe{parser.test}
ld libbuild2\test\script\exe{parser.test}
ld libbuild2\build\script\exe{lexer.test}
ld libbuild2\exe{scheduler.test}
ld libbuild2\exe{function.test}
ld libbuild2\exe{lexer.test}
ld libbuild2\exe{name.test}
ld libbuild2\exe{make-parser.test}
ld libbuild2\libs{build2}
ar libbuild2\bin\libus{build2-bin}
ar libbuild2\in\libus{build2-in}
ld libbuild2\in\libs{build2-in}
ld libbuild2\bin\libs{build2-bin}
ar libbuild2\version\libus{build2-version}
ar libbuild2\bash\libus{build2-bash}
ld libbuild2\bash\libs{build2-bash}
ld libbuild2\version\libs{build2-version}
ar libbuild2\cc\libus{build2-cc}
ld libbuild2\cc\exe{parser.test}
ld libbuild2\cc\exe{lexer.test}
ld libbuild2\cc\libs{build2-cc}
ar libbuild2\c\libus{build2-c}
ar libbuild2\cxx\libus{build2-cxx}
ld libbuild2\c\libs{build2-c}
ld libbuild2\cxx\libs{build2-cxx}
ld build2\exe{b}
ld tests\libbuild2\exe{driver}

Attempting to import libgtksourceview fails with:

unable to execute C:\Program Files\Microsoft Visual Studio\2022\Preview\VC\Tools\MSVC\14.35.32124\bin\Hostx64\x64\cl: the parameter is incorrect

libs =
import libs += libadwaita-1%lib{adwaita-1}
import libs += libgtksourceview-5%lib{gtksourceview-5}

# NOTE: libecho is not a package.
#
include ../libecho/
libs += ../libecho/lib{echo}

# Resource files are written in XML and contain a list of resources and their 
# corresponding properties. The glib-compile-resources utility reads these 
# resource files and converts them into a binary representation that can be 
# used by Echo at runtime.
#
./: c{gresource}: xml{*}
{{
  diag xml ($<[0])
  glib-compile-resources --generate-source $path($<[0]) --sourcedir $src_root/echo
}}

./: exe{echo}: {c hxx ixx txx cxx}{**} $libs $gresource testscript

switch $cxx.target.class, $cxx.id
{
  case 'windows', 'msvc'
  {
    cxx.coptions = /MDd /Zi
    cxx.loptions = /DEBUG /LIBPATH:C:/gnome/lib
  }
}

cxx.poptions =+ "-I$out_root" "-I$src_root"

Logs:

logs.txt

Build:

meson setup builddir -Dprefix=C:/gnome
meson install -C builddir

Configure glob patterns for excluding files and folders with Visual Studio Code and Visual Studio 2022. For example, the File Explorer decides which files and folders to show or hide based on this setting.

Consider an executable and a plugin (shared library). While an executable does not link the plugin, it would normally still list it as an ad hoc prerequisite to make sure it is up-to-date. It would also be helpful to enable our automatic rpath support for such an ad hoc prerequisite so that the plugin could be found when loaded in the development builds.

BTW, if someone wouldn't want this rpath functionality, they could instead use a post hoc prerequisite.