Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"bii build" runs "bii configure" even if nothing changed #22

Open
smessmer opened this issue Apr 27, 2015 · 2 comments · May be fixed by #25
Open

"bii build" runs "bii configure" even if nothing changed #22

smessmer opened this issue Apr 27, 2015 · 2 comments · May be fixed by #25
Assignees

Comments

@smessmer
Copy link

OS: Ubuntu 14.10
Biicode: 3.0

Steps to reproduce:

$ git clone git@github.com:smessmer/cryfs.git
$ cd cryfs
$ bii init -l
$ bii build -- -j5

Then, without changing any files, directly call

$ bii build -- -j5

It runs the whole configure step again before it notices that actually nothing changed. For projects with some dependencies, this happening with each compiler call is a lot of lost time.

Especially in a project with multiple open blocks (old project layout), this configure step takes quite a while, because configuring an open block takes longer than configuring a closed block.

@drodri
Copy link
Contributor

drodri commented Apr 29, 2015

Last refactors, released in version 3.1.1 would greatly alleviate the problem of speed in configuring large projects. In any case, I suggest the following solution: #25

Could it be enough? Just typing 2 chars "-q" more :)

@smessmer
Copy link
Author

I didn't see a big difference in configuring speed in 3.1.1 unfortunately.

To your point of not breaking developer expectations, maybe "bii build" could configure the project if it isn't configured yet, but not reconfigure it after the first call.

An alternative approach would be that "bii build" is intelligent on whether a reconfigure is necessary (check whether config files changed) and only reconfigure in that case.

I think these solutions would be better, but I can also live with "-q".
If you decide not to implement the suggestions, you can close this issue.

@drodri drodri self-assigned this May 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants