Closed Sh4rK closed 5 years ago
Can you try with: pip3 install -U lbuild==1.11.1
?
Same.
Is this the standard modm-io/modm/develop
branch?
Cos the warnings should be fixed now.
[WARNING] lbuild.repository: Namespacing repository filter 'chr' to 'modm.chr'!
Oh no. I know what's happening here. WINDOWS. NOooooooo.
I use :
as hierarchy separator for lbuild modules, and the d:\
fucks this up.
Sorry, I'm fixing this with 1.11.3.
The warnings do seem to be fixed now, I don't remember what configuration of modm and lbuild I used in the first post.
Ok, I now first check if the config file exists and if it does not check if it contains :
and if that's not the case, raise such a "not found" exception. Try v1.11.3.
Awesome, it works! Thanks!
I just upgraded my lbuild and pulled the latest develop changes, and this is what I get: