On 2018-04-20 11:50, oliver wrote: > > your first answer pointed to the right direction. > i found the solution after digging a bit more in the archives: > > for non-native executables (FFPLAY in my case) you need to provide > absolute paths in the shell scripts.
i figure this just a PATH issue (PATH missing "/usr/local/bin") for interactive shells (which is what you get by opening Terminal.app), this seems to be automatically handled by ~/.bashrc. at least mine (on an OSX machine) looks like: ~~~ # only run in interactive mode: [ -z "$PS1" ] && return export CVS_RSH=ssh export PATH=${PATH}:/usr/local/bin if [ "x${EDITOR}" = "x" ] then export EDITOR=/usr/bin/vi fi ~~~ which makes it clear that non-interactive shells (and non-bash) shells do not get the merits of /usr/local/bin/... you could: - call programs by absolute paths (which is what you already do; it's somewhat ugly as it breaks everything if the paths ever change) - add something like "PATH=/usr/local/bin:${PATH}" at the beginning of your script (after the hashbang) and don't worry any more. - add /usr/local/bin to your global search paths. e.g. [1]. fgmasdrt IOhannes [1] https://docs.brew.sh/FAQ#my-mac-apps-dont-find-usrlocalbin-utilities
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list