[build2] Potential improvement: "bdep new ... --package" should automatically configure?

Klaim - Joël Lamotte mjklaim at gmail.com
Thu Jun 7 17:01:36 UTC 2018

On 7 June 2018 at 00:44, Klaim - Joël Lamotte <mjklaim at gmail.com> wrote:
> On 6 June 2018 at 14:08, Boris Kolpackov <boris at codesynthesis.com> wrote:
>> BTW, currently, instead of deinit & init, you should be able to init just
>> that package, for example:
>> bdep init -d new-package
>> Or just run bdep init: it will skip the already-initialized ones.
> I can confirm that this works with v0.7.0.

However I observe an error (last line) with v0.8.0, when trying to do the same:

PS G:\perso\experiments> bdep --version
bdep 0.8.0-a.0.a992a95ef3f7
libbpkg 0.8.0-a.0.8a300f420c27
libbutl 0.8.0-a.0.99be6932124a
Copyright (c) 2014-2018 Code Synthesis Ltd
This is free software released under the MIT license.
PS G:\perso\experiments> bdep new lolilol -t lib
warning: library name does not start with 'lib'
  info: this package may not be acceptable to some repositories
created new library project lolilol in G:\perso\experiments\lolilol\
PS G:\perso\experiments> cd .\lolilol\
PS G:\perso\experiments\lolilol> bdep init -C ../build-msvc cc config.cxx=cl
initializing in project G:\perso\experiments\lolilol\
created configuration G:\perso\experiments\build-msvc\ 1
  new lolilol/0.1.0-a.0.19700101000000
PS G:\perso\experiments\lolilol> bdep new kikoo -t exe --package
created new executable package kikoo in G:\perso\experiments\lolilol\kikoo\
PS G:\perso\experiments\lolilol> bdep init
error: package directory  is not listed in G:\perso\experiments\lolilol\

Note that there is an additional empty space between "directory" and
"is" in the error log.
Looks like the error log is wrong and it should still work and not
trigger an error.


More information about the users mailing list