Custom Build Tool Not Found - Unexpectedly found nil while unwrapping an Optional value

[shahzadmajeed]

Hi,

Very nice tool. It can find builtin tools at default $PATH but not custom tools. I have a command line tool installed at /usr/local/bin/ and I have added that to $PATH but the program doesn't seem to locate the tool. It seems like $PATH doesn't even have that value appended to it. Not sure if there is an easy way to configure the tool to look at custom paths at initialization rather than just looking at $PATH so that it can fallback to say CUSTOM_TOOLS_LOOKUP or something which could just be a simple hashmap initialized by the dependent program?

Do you have any suggestion on fixing my current issue? Thank you!

[shahzadmajeed]

Actually I think I can initialize Command object with executable path directly and it works.. but another problem (which is same with ShellOut as well) due to which I was trying to move from ShellOut to SwiftCommand is basically I want to print logs as sub-commands are being executed just as it happens on terminal. But it seems like we are logging output once the invoked command is done executing. Is there a way to log each entry as soon as it is generated from the tool/command being executed?

[Zollerboy1]

Hey @shahzadmajeed can you provide a bit more context? What are you trying to achieve? Can you maybe give me an example that doesn't work as expected for you?