[platypus-dev] Re: Debugging bash script output in Platypus 4.4
- From: Advrk Aplmrkt <avkaplmkt@xxxxxxxxx>
- To: platypus-dev@xxxxxxxxxxxxx
- Date: Sun, 15 Jul 2012 18:27:42 -0400
I ended up compiling and statically linking a copy of gawk from
scratch, and including it in the application, which worked.
Then I tried to remove that gawk, and revert to calling awk on the
local machine. For some reason it worked this time! I am not really
sure what I did wrong the first time, but now my computer can find awk
just fine.
Thanks for your suggestions!
On 13 July 2012 20:11, Dan Pritts <danno@xxxxxxxxx> wrote:
> I am completely new to this, and please excuse my ignorance. :)
>
> I have an existing bash script that recursively goes through the
> directory it is run in, identifies all JPEG image files, and adds
>
> I can't imagine awk won't always be in /usr/bin/awk on a macos machine;
> hardcode the path and you'll see whether that fixes it. I doubt that's your
> problem though, /usr/bin should be in the default path.
>
> Try changing your app to use a text window instead of a droplet. that way
> you'll see the output of the script.
>
> Another approach would be to have a wrapper shell script that calls your
> primary script. Have the wrapper send the output to a file.
>
> #!/bin/sh
>
> /your/real/script/here 2>&1 >/tmp/output.$$
>
> hope this helps
Other related posts:
