Heh - copy and paste --> garbage. That first sentence should be "... on the computer where you have cloned the ripple repository ..." :)
-----Original Message----- From: Tim Barham [mailto:[email protected]] Sent: Thursday, January 29, 2015 1:47 PM To: [email protected] Subject: RE: Build error Kiran - on the computer where you have you have clones the ripple repository and built Ripple, you can do one of the following: 1. From within the root Ripple folder (which contains package.json), enter "npm link". The 'ripple' command should now be available from the command line, and it will use the files in your repository (so you can make changes, build, and see the changes reflected next time you launch ripple). 2. In a console window, enter ' npm install -g [path to root Ripple folder]'. This will *copy* the ripple files to the npm node_modules folder. You will be able to use "ripple" from the command line, but it will use the copy and not the original source (so you won't be able to see changes you make in ripple without re-installing). Then, from the root folder of a Cordova project, enter "ripple emulate". (Note you can also copy the required ripple files to another computer and install from the folder. To know which files you should copy, look under "files" in package.json). Tim -----Original Message----- From: Venkata Kiran [mailto:[email protected]] Sent: Thursday, January 29, 2015 5:17 AM To: [email protected] Subject: RE: Build error Hi, How can I ripple emulate the cordova app using the ripple build I created ? Thanks & Regards, --Kiran -----Original Message----- From: Brent Lintner [mailto:[email protected]] Sent: Friday, January 23, 2015 10:50 PM To: [email protected] Subject: Re: Build error Hey Kiran, I hear you coming from a Windows standpoint. I had worked a bit on it in the past, but, primarily (when Ripple was initially created and worked on) it was always *nix environments, mainly Linux. Any help on the Windows end is always appreciated and uber helpful! Hope to hear from you in the future. Happy to help; all the best! On Fri Jan 23 2015 at 11:21:25 Venkata Kiran <[email protected]> wrote: > Hi Brent, > > Thanks, I am finally able to complete the build. It seemed a > long process and coupled with unclear documentation(may be the > documentation was more linux flavoured), things were little more > difficult. With so many things I have tried to make this work, I will > do this again on another system and try to create a clear > instructions. I hope they will help someone down the line. I will get back to > you in case I need any help. > > Thanks a lot for helping me out. > > Thanks & Regards, > --Kiran > > > -----Original Message----- > From: Brent Lintner [mailto:[email protected]] > Sent: Friday, January 23, 2015 8:58 PM > To: [email protected] > Subject: Re: Build error > > Hey Kiran, > > Ah! Glad you were able to get around things. > > >> Error: Error: Command failed: 'cp' is not recognized as an internal > >> or > external > command, > > Hmm. I wish I noticed earlier you seem to be on Windows. > > I know some members have created some instructions in the README > (which I presume you have already checked out): > https://github.com/apache/incubator-ripple#build-requirements > > However, I am not sure as to the status of it in Windows (CMD prompt). > `cp` is technically a command there... In the README, msysgit is > mentioned, which is what I use for building, etc. Perhaps that will > ultimately solve things? > > http://msysgit.github.io > > All the best, > > Brent > > On Fri Jan 23 2015 at 09:30:16 Venkata Kiran <[email protected]> wrote: > > > Thanks Brent. > > > > I was able to resolve the earlier issue but I kept on > > running into new issues and was resolving them as they are > > encountered. As of now, I am stuck with the below issue. I was just > > wondering if I was doing anything wrong or if the process itself is > > too long with too many > dependencies. > > > > C:\Work\gwtphonegap\incubator-ripple>jake -t jake aborted. > > Error: Error: Command failed: 'cp' is not recognized as an internal > > or external command, operable program or batch file. > > > > at C:\Work\gwtphonegap\incubator-ripple\build\targets\hosted. > js:35:28 > > at ChildProcess.exithandler (child_process.js:652:7) > > at ChildProcess.emit (events.js:98:17) > > at maybeClose (child_process.js:756:16) > > at Process.ChildProcess._handle.onexit (child_process.js:823:5) > > > > C:\Work\gwtphonegap\incubator-ripple> > > > > Thanks & Regards, > > --Kiran > > > > > > -----Original Message----- > > From: Brent Lintner [mailto:[email protected]] > > Sent: Thursday, January 22, 2015 10:08 PM > > To: [email protected] > > Subject: Re: Build error > > > > Hey Kiran, > > > > If you: > > > > ./node_modules/.bin/bower install > > > > Doe that solve it? I know Jasmine used to be installed via git > > submodules, but now is part of bower. *should* be working, heh, > > unless I messed something up (in > > https://github.com/apache/incubator-ripple/commit/ > > fb77af84a6b43bf7772e8b4fe5c3ccbcfc752032 > > ). > > > > All the best, > > > > Brent > > > > On Thu Jan 22 2015 at 09:56:44 Venkata Kiran <[email protected]> wrote: > > > > > Hi, > > > > > > > > > > > > I checked out the Ripple code and when I am trying > > > to make a build, I am getting the below error. Any help on how to > > > get around it ? > > > > > > > > > > > > C:\Work\gwtphonegap\incubator-ripple>jake -t > > > > > > jake aborted. > > > > > > Error: Cannot find module > > > 'C:\Work\gwtphonegap\incubator-ripple\build/../thirdpa > > > > > > rty/jasmine/lib/jasmine-core/jasmine' > > > > > > at Function.Module._resolveFilename (module.js:338:15) > > > > > > at Function.Module._load (module.js:280:25) > > > > > > at Module.require (module.js:364:17) > > > > > > at require (module.js:380:17) > > > > > > at Object.<anonymous> > > > (C:\Work\gwtphonegap\incubator-ripple\build\test\jasmi > > > > > > ne-node.js:23:15) > > > > > > at Module._compile (module.js:456:26) > > > > > > at Object.Module._extensions..js (module.js:474:10) > > > > > > at Module.load (module.js:356:32) > > > > > > at Function.Module._load (module.js:312:12) > > > > > > at Module.require (module.js:364:17) > > > > > > at require (module.js:380:17) > > > > > > > > > > > > Thanks, > > > > > > --Kiran > > > > > > > > > > > >
