Slick Edit build "shell" vs Window command "shell"

[ronw]

I am using Slick Edit 15.0.1.3

In my Project Properties, I have configured the following as my Build command:

C:\Freescale\CodeWarrior_for_S12X_V5_0\Prog\maker.exe "%rn.mak" all

When I run the build of my project from inside SE, SE runs the following:

"C:\Program Files\SlickEditV15.0.1\win\vsbuild" -signal 1093 -command C:\Freescale\CodeWarrior_for_S12X_V5_0\Prog\maker.exe "Pod.mak" all

which then runs:

C:\Freescale\CodeWarrior_for_S12X_V5_0\Prog\maker.exe "Pod.mak" all

and the build runs to successful completion.

However, in the Windows Cmd window, when I run:

C:\Freescale\CodeWarrior_for_S12X_V5_0\Prog\maker.exe "Pod.mak" all

nothing happens, not even an error message. I even tried:

C:\Freescale\CodeWarrior_for_S12X_V5_0\Prog\maker.exe Pod.mak all

Still, nothing happens. I just get another command prompt.

Why would maker.exe run the make file correctly when run inside SE, but do nothing from the Windows cmd prompt?

[Graeme]

Maybe the current directory is different for the two cases or maybe maker.exe outputs to stderr instead of stdout.

Have you tried maker.exe /?

[ronw]

I re-verified that the current directory is the same.  "maker /?" also did nothing. "maker /help" popped up a notification box saying "error parsing options 'elp'", so I tried "maker /h", which did nothing.