Yeah the install script does a check for root user: https://github.com/apache/cordova-cli/blob/master/bootstrap.js#L61
Interesting that that is not working out.. On 5/28/13 10:35 AM, "Don Coleman" <[email protected]> wrote: >I re-did the NPM install but didn't see the message. I'll retry on a fresh >machine today. > > >On Tue, May 28, 2013 at 10:25 AM, Braden Shepherdson ><[email protected]>wrote: > >> I note also the "macosx" in some paths there. >> >> And isn't there are message during the npm install that warns about >> chmodding that directory? I agree that this sucks and it would be great >>to >> fix it. >> >> Braden >> >> >> On Tue, May 28, 2013 at 8:46 AM, Andrew Grieve <[email protected]> >> wrote: >> >> > One hope here is that the problem will go away once we lazily fetch >>the >> > platform repos. >> > >> > >> > On Tue, May 28, 2013 at 12:28 AM, Don Coleman <[email protected]> >> > wrote: >> > >> > > "cordova platform add android" was failing on linux with an error >> > > about the android-sdk-macosx >> > > >> > > don@localhost:~/tmp/foo$ cordova platform add android >> > > [Error: An error occured during creation of android sub-project. >> > > BUILD FAILED >> > > >> > > >> > >> >>/usr/local/lib/node_modules/cordova/lib/cordova-android/framework/build.x >>ml:133: >> > > Cannot find /Applications/android-sdk-macosx/tools/ant/build.xml >> > > imported from >> > > >> > >> >>/usr/local/lib/node_modules/cordova/lib/cordova-android/framework/build.x >>ml >> > > >> > > cordova 2.7.4 node 0.10.8 npm 1.2.23 Ubuntu 12.04.2 LTS | crouton | >> > > ChromeOS >> > > >> > > == >> > > >> > > The problem was cordova was installed with sudo. >> > > >> > > The eventual solution was to chown -R the cordova npm directory. At >> > > first I tried editing sdk.dir in >> > > >> > > >> > >> >>/usr/local/lib/node_modules/cordova/lib/cordova-android/framework/local.p >>roperties >> > > which seemed like a bad idea. >> > > >> > > CB-2604 says there should have been a warning about a root install >>but >> > > I never got one. >> > > >> > > >> > >> >>https://issues.apache.org/jira/browse/CB-2604?focusedCommentId=13637291&p >>age=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comm >>ent-13637291 >> > > >> > > Thoughts on the best way to handle this? >> > > >> > >>
