-
7 Oct 2012 2:59 PM #1
Command not found mac OSX mountain lion
Command not found mac OSX mountain lion
I ran the mac installer for sencha cmd. but when I type sencha into a terminal window all I get is this:
-bash: sencha: command not found
The directory was created and the files exist after running the installer. What else do I have to do?
-
7 Oct 2012 8:14 PM #2
What version of Sencha Cmd did you install? Also, did you start a new terminal instance? The PATH environment variable is updated by a shell script that should run on terminal start.
Don Griffin
Ext JS Development Team Lead
Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue
"Use the source, Luke!"
-
7 Oct 2012 10:42 PM #3
.bash_profile
.bash_profile
On Lion 10.7.4, you have to add PATH and VAR in the .bash_profile file at the root of your user folder !
Code:export SENCHA_CMD_3_0_0="/Users/you/Path/To/Sencha/Cmd/3.0.0.XXX" export PATH=/Users/you/Path/To/Sencha/Cmd/3.0.0.188:$PATH
-
7 Oct 2012 10:56 PM #4
That should be done by the installer. Maybe not to that exact shell script, I'll have to check, but you should not need to add anything manually.
Don Griffin
Ext JS Development Team Lead
Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue
"Use the source, Luke!"
-
7 Oct 2012 11:44 PM #5
Hi Don,
With the new Cmd v3 (since 144), i've to manually insert the VAR and PATH into my .bash_profile file.
The VAR and PATH are well added to the .profile file, but the "sencha" command in Terminal gives nothing. This works after having added to the .bash_profile...
-
10 Oct 2012 12:06 PM #6
-
10 Oct 2012 12:25 PM #7
I have opened a bug in our bug tracker so we can look at this. Thanks!
-
10 Oct 2012 10:28 PM #8
-
11 Oct 2012 12:35 PM #9
Don Griffin
Ext JS Development Team Lead
Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue
"Use the source, Luke!"
-
11 Oct 2012 1:38 PM #10
Thanks, yeah - tried to delete in time once I realized mine was different. I've resolve my issue. Thanks for the tip. I really appreciate it.
You found a bug! We've classified it as
SDKTOOLS-202
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote

