search

MobileChromeApps / chrome-app-developer-tool

Mirror of Apache Cordova app harness
Other
202 stars 33 forks source link

Updated list of preloaded plugins #27

Closed beaufortfrancois closed 9 years ago

beaufortfrancois commented 9 years ago

I wasn't able to compile it eventually ;(

Please can you make sure everything works as intended by pushing the ChromeSpec Mobile Chrome App?

BUG=#25

image

mmocny commented 9 years ago

Tested successfully; CADT builds and the manual tests work.

Not all auto tests pass, but I believe there is currently an issue with i18n tests, not related to this change causing the issue.

@beaufortfrancois I'd be happy to sit down some day and get you set up to build CADT yourself. You will need to set up a cordova development environment, using the coho command. Not sure if you have tried to do that yet.

rikelk commented 9 years ago

Hi @mmocny ,

it will be really nice if you could explain how to achieve that because i'm stuck since a week trying to manage it. At this point, when running step ./createproject.sh ChromeAppDevTool, i got this error:

Running: gulp build-dev [21:09:23] Using gulpfile ~\chrome-app-developer-tool\gulpfile.js [21:09:23] Starting 'lint:app'... [21:09:23] Starting 'lint:harness-push'... [21:09:23] Starting 'webpack:build-dev'... [21:09:23] Starting 'styles'... [21:09:23] [webpack:build-dev] Hash: 3de03120719048f2f578 Version: webpack 1.4.13 Time: 78ms Asset Size Chunks Chunk Names cca.bundle.js 1996 0 [emitted] cca cca.bundle.js.map 1999 0 [emitted] cca chunk {0} cca.bundle.js, cca.bundle.js.map (cca) 28 [rendered] [0] multi cca 28 {0} [built] [1 error]

ERROR in multi cca Module not found: Error: Cannot resolve 'file' or 'directory' ../../src/cca.js in C:\Users\leila\chrome-app-developer-tool/www/cdvah @ multi cca [21:09:23] Finished 'webpack:build-dev' after 88 ms [21:09:24] Finished 'styles' after 368 ms [21:09:24] Finished 'lint:harness-push' after 663 ms [21:09:25] Finished 'lint:app' after 1.4 s [21:09:25] Starting 'lint'... [21:09:25] Finished 'lint' after 8.15 μs [21:09:25] Starting 'build-dev'... [21:09:25] Finished 'build-dev' after 6.79 μs

fs.js:690 return binding.lstat(pathModule._makeLong(path)); ^ Error: ENOENT, no such file or directory 'C:\cygdrive' at Object.fs.lstatSync (fs.js:690:18) at Object.realpathSync (fs.js:1278:21) at [eval]:1:27 at Object. ([eval]-wrapper:6:22) at Module._compile (module.js:456:26) at evalScript (node.js:536:25) at startup (node.js:80:7) at node.js:906:3

module.js:340 throw err; ^ Error: Cannot find module 'C:\cygdrive\c\Users\leila\chrome-app-developer-tool\node_modules\cordova\bin\cordova' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Function.Module.runMain (module.js:497:10) at startup (node.js:119:16) at node.js:906:3

don't know what to do with that...

Thanks!

mmocny commented 9 years ago

It looks like @agrieve made a change referencing this issue. I'm not sure if your problem will be resolved, but one of our upcoming tasks is to better document the steps necessary to build CADT yourself.

Note, this project is usually meant to be consumed by installing our pre-built versions from the Releases page, and so the build instructions are historically for us and not entirely complete (but we hope to improve this, see above).

Valid reasons to build your own CADT include: to get an iOS version, to add plugins which we didn't add by default, or to set custom a packageId for use with cloud apis (like gcm/payments).