I have followed the installation guide to install and am getting stuck on the errors I see in the command line.
If I navigate to the SDK and just type sencha I get -
[WARN] The current working directory (/Applications/MAMP/htdocs/sencha-touch-2.1.0-gpl/sdk) is not a recognized Sencha SDK or application folder. Running in backwards compatible mode.
Sencha Command v2.0.0 Beta 3
Copyright (c) 2012 Sencha Inc.
usage: sencha COMMAND [ARGS]
The available commands are:
build build a JSB project
create bootstrapdata generate boostrap data
create jsb generate a minimal JSB project for an app
create locale generate a template locale file from source
create manifest generate classes manifest
package package your Touch web app into a native bundle
slice theme slice a custom theme's images for IE
I saw on a thread that if you add a hidden file called .senchasdk into the sdk then that will help.
But than I get this error -
throw e; // process.nextTick error, or 'error' event on first tick
Error: Cannot find module '/Applications/MAMP/htdocs/sencha-touch-2.1.0-gpl/sdk/command/sencha.js'
at Function._resolveFilename (module.js:332:11)
at Function._load (module.js:279:25)
at Array.0 (module.js:479:10)
at EventEmitter._tickCallback (node.js:19
This has me confused! There is no path sdk/command but there is sdk/cmd
If I try sencha generate app that has the same error
I have no idea how to progress. I have sencha cmd 3.0 installed but any sencha commands I do throws error.
Do I have to change the SDK path in /etc/paths/ ??
FYI all, I tried to install the latest Sencha Cmd 220.127.116.11 version, and found that the Mac OSX installer on OSX 10.7.5 did not correctly update the $PATH. When I dug a little further, I found that my ~/.bash_profile and ~/.profile had the correct PATH 'Export' statements, but it wasn't until I also put the newer Sencha Cmd path into my ~/.bashrc file, and reloaded the bash terminal that using Sencha Cmd became possible.
In researching this on StackOverflow, I reference this great post on the in's & out's of Mac OSX 10.7.x $PATH parsing which helped clarify the issue...
I think Sencha need to re-test and clean up their Mac OSX installers in general, especially if you are paying for Sencha Complete, and make its a seamless one-click install that detects dependencies and corrects these kinds of issues.