This PR allows for buildings the depends packages on WSL
Tested on Windows 11 WSL 2.x
This PR allows for buildings the depends packages on WSL
Tested on Windows 11 WSL 2.x
This PR allows for buildings the depends packages on WSL
Tested on Windows 11 WSL 2.x
What is the current issue exactly?
Current issue is that Windows Subsystem for Linux adds some PATH values that have () and spaces, which cause these 3 lines of code to get a syntax error, simply adding the quotes fixes the issue.
Actually to be clear the issue also happens on any linux distro that has PATH values with those characters.
I think this change fixes those issue mentioned, I'm able to build depends correctly with path values with spaces with this fix.
With fix:

Without:

$PATH value:

Concept and code review ACK 663cda823a3a4348a57f9edb6c77aa8d35209d09
I'm kind of happy to see building in paths with spaces is almost supported. It's almost like it's 2022 not 1984. Once that works it'd make sense to do it in one of the CI runs.
Concept and code review ACK 663cda8
I'm kind of happy to see building in paths with spaces is almost supported. It's almost like it's 2022 not 1984. Once that works it'd make sense to do it in one of the CI runs.
I usually avoid path values with spaces, but sometimes it just can't be helped 😄
I usually avoid path values with spaces, but sometimes it just can't be helped smile
Sure, if that's your preference. But there should be no technical reason to :smile: Space has been a valid character in paths since, i dunno, moving away from FAT16? To be sure, some of the UNIX tooling is just very clumsy in that regard, it's not specific to this project. But things are improving slowly.
I usually avoid path values with spaces, but sometimes it just can't be helped smile
Sure, if that's your preference. But there should be no technical reason to 😄 Space has been a valid character in paths since, i dunno, moving away from FAT16? To be sure, some of the UNIX tooling is just very clumsy in that regard, it's not specific to this project. But things are improving slowly.
For sure!
@mxaddict can you confirm that everything works with this change. Not just building depends, but also building bitcoind, running make install, even performing a cross-compile etc.
You'll also need to get rid of the merge commit out of the PR, and, while you're at it, can you update the commit message for the change to be more descriptive than Updated funcs.mk to work...
I can confirm that I can cross compile for mingw and osx as well, have not tried any other builds though
I assume it also does not break any builds as the CI runs have passed.
Sure, I can update the commit message and remove the merge commit
Closing, no one seems to be interested in this PR