Closed chdiza closed 7 years ago
I should add that, if I do it the xcodebuild
way, I see similar messages, but they are only dubbed "warnings" and the build allegedly finishes
Thank you, please confirm the fix
It built, but then to my surprise it auto-launched some kind of test suite that turned off my bluetooth and thus left me with neither keyboard or mouse. Maybe that should be behind a make install
target. I was not expecting that, since xcodebuild
doesn't do that to me.
Thanks for the fix.
Sorry for the mess, I hope bluetooth was successfully restored to original state. I've updated the Makefile to only build by default and added other targets to test and install.
It was restored, fortunately. I can imagine something going wrong during the test, in such a way that bluetooth is never turned back on. Maybe a warning should be printed to the user on stdout if they ask for make test
.
(Maybe there is an easy way to turn bluetooth back on if one's keyboard and mouse have been disconnected, but short of having a wired mouse, or perhaps rebooting and hoping the OS attempts to find one's gear, I don't know what that is.)
BTW, blueutil
is a nice little tool. I like it, and I'm glad it's still maintained.
Good idea, quick search suggests that turning off bluetooth without wired input devices at hand will not be a nice experience, so I've added a warning + confirmation: fd6999bd4334b8c0ba58e3762500625d63e5d120. I am really glad that the tool is helpful :)
On Sierra 10.12.3, if I type
make
while in the unzipped source directory, I get this:I have Xcode 8.2.1 and the latest CommandLineTools installed.