如何修复extjs4.1中的构建错误com.sencha.exceptions.ExProcess

Question

我在构建 extjs4.1 项目时遇到以下异常。谁能告诉我如何避免它？我使用的是sencha命令版本3.0。使用命令

sencha app build


[ERR]           D:\TestProduction\.sencha\app\build-impl.xml:213: com.sencha.exc
eptions.ExProcess: phantomjs process exited with code 100 :

谢谢

Answer 1

我在运行 sencha 应用程序构建时遇到了同样的问题：

[...]
[INF] loading page .../static/sass/example/theme.html
failed to render widgets within 30 sec.

[ERR]
[ERR] BUILD FAILED
[ERR] com.sencha.exceptions.ExProcess: phantomjs process exited with code 1
[ERR]
[ERR] Total time: 49 seconds
[ERR] The following error occurred while executing this line:
.../static/.sencha/app/build-impl.xml:469: com.sencha.exceptions.ExProcess: phantomjs process exited with code 1

我的项目目录好像缺少

sass

文件夹。

所以我创建了一个新应用程序并从那里复制了 sass 文件夹：

$ cd /tmp
$ sencha -s ~/develop/js/Sencha/ext-4.2.1.883 generate app MyApp myapp
$ tree myapp/sass
myapp/sass
├── config.rb
├── etc
├── example
│   ├── bootstrap.css
│   ├── custom.js
│   ├── render.js
│   └── theme.html
├── src
└── var
$ cp -r myapp/sass <dest>

我还尝试将 sass 文件夹直接从我的应用程序中的

ext

文件夹中复制出来：

$ cp -r ext/packages/ext-theme-classic/sass .

但是好像有些路径没有设置。所以我必须手动编辑文件

theme.html

:

$ vim sass/example/theme.html

[...]
<!--
These links need to match the ext sdk from the current project
-->
<link rel="stylesheet" type="text/css" href="example.css" />
<script type="text/javascript" src="../../ext/ext-dev.js"></script>
<script type="text/javascript" src="bootstrap.js"></script>

此后，我又可以做

sencha app build

：

$ sencha app build
[...]

[INF] loading page .../static/sass/example/theme.html
Capturing screenshot
Saving slicer widget manifest
Capture complete

[INF] Capture complete
[INF]      [echo] Slicing theme images to .../static/build/CreateProduct/production/resources
[INF] Including theme package ext-theme-classic for app.theme=ext-theme-classic build
[INF] Slicing images...
[INF] Slicing complete - generated 0 images
[INF]
[INF] -after-slice:
[INF]
[INF] -build:
[INF]
[INF] -after-build:
[INF]
[INF] build:
[INF]
[INF] app-build:

Answer 2

我遇到了同样的问题，它似乎与客户端路径有关，路径名中包含“#”，即 c:\project