当我在编译qt-extended-4.4.3时,总是提示这个错误我表示很不解,能保忙回答一下吗???谢谢 很急,现在,高手指点

闪电侠风行 2011-10-07 09:23:53
Project () ERROR: An error occured while evaluating a QBuild script extension.
File: /witech/qt-extended-4.4.3/qbuild.pro@87
Error: SyntaxError: Parse error
<anonymous>()@:6732

用的是ubuntu10.04 ,编译器是arm-linux-gcc 4.4.1.



这是源码:
qbuild.pro的源码:




UNIFIED_NCT_LUPDATE=1
TEMPLATE=subdirs
SUBDIRS=src etc/themes examples

# qbuild cleanimage
cleanimage [
TYPE=RULE
commands=\
"#(eh)echo $$shellQuote(Removing $$QTOPIA_IMAGE)"\
"#(e)rm -rf $$shellQuote($$QTOPIA_IMAGE)"
]

# qbuild clearDBlocks
clearDBlocks [
TYPE=RULE
commands=\
"#(e)$$path(QtopiaSdk:/bin/content_installer,generated) -clearlocks $$QTOPIA_IMAGE/qtopia_db.sqlite"\
"#(e)for qtopia in /tmp/qtopia-*; do \
if [ -f $$shellQuote($qtopia/$$QTOPIA_IMAGE/qtopia_db.sqlite) ]; then \
$$path(QtopiaSdk:/bin/content_installer,generated) -clearlocks $$shellQuote($qtopia/$$QTOPIA_IMAGE/qtopia_db.sqlite); \
fi; \
done"
prerequisiteActions=\
"#(oh)/src/tools/content_installer/check_enabled"\
"#(oh)/src/tools/content_installer/target"
]

# Before qbuild image, remove the image and clear the DB locks
PREIMAGE_RULES=cleanimage clearDBlocks sub_prep_db

# QBuild append_image skips the removing part. Not so useful now but will be once the install
# rules set inputFiles and outputFiles correctly (ie. only update what isn't already up-to-date).
append_image [
TYPE=RULE
prerequisiteActions=clearDBlocks sub_prep_db sub_image makeimagedone
serial=true
]

# print a message when qbuild is done
makedone [
TYPE=RULE
commands=\
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(Qt Extended has been built.)"\
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(You must now install Qt Extended by running 'bin/qbuild image'.)"\
"#(eh)echo $$shellQuote(This will put the files required to run Qt Extended into the image:)"\
"#(eh)echo $$shellQuote("$$QTOPIA_IMAGE")"\
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(Before you can use the SDK you must finalize it by running 'bin/qbuild sdk'.)"\
"#(eh)echo $$shellQuote(This will put the required files into the SDK:)"\
"#(eh)echo $$shellQuote("$$SDKROOT")"\
"#(eh)echo $$shellQuote()"
]
POSTRUN_RULES=makedone

# print a message when qbuild image is done
makeimagedone.TYPE=RULE 58行
makeimagedone.commands=\ 59行
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(Qt Extended has been installed.)"\
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(The files required to run Qt Extended are in the image:)"\
"#(eh)echo $$shellQuote($$QTOPIA_IMAGE)"\
"#(eh)echo $$shellQuote()"
equals(QTOPIA_IMAGE,$$QTOPIA_PREFIX):makeimagedone.commands+=\
"#(eh)echo $$shellQuote(Please note that Qt Extended cannot be moved. It must be run from the image.)"
else:makeimagedone.commands+=\
"#(eh)echo $$shellQuote(Please note that Qt Extended cannot be run from the image.)"\
"#(eh)echo $$shellQuote(You must move Qt Extended to the prefix first. The prefix is:)"\
"#(eh)echo $$shellQuote($$QTOPIA_PREFIX)"
!enable_rpath:makeimagedone.commands+=\
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(Note that you will need to set)"\
"#(eh)echo $$shellQuote(LD_LIBRARY_PATH=$$QTOPIA_PREFIX/lib)"\
"#(eh)echo $$shellQuote(unless you are using bin/runqtopia or Qt Extended will not start.)"
makeimagedone.commands+=\
"#(eh)echo $$shellQuote()"
POSTIMAGE_RULES=makeimagedone

# Setup some default targets
installs_getImage()

!equals(SDKROOT,$$path(/,generated)) {
# make the SDK stand-alone
<script> 86行
var script = project.property("SDK_SCRIPT"); 87行
var file = qbuild.invoke("path", "/src/build/bin/sdkcache", "project");
script.setValue(file);
if ( script.strValue() == "" ) {
project.warning("Unable to locate sdkcache script.");
return;
}
</script>
sdk.TYPE=RULE
#sdk.prerequisiteActions=default
sdk.commands=\
"#(eh)echo $$shellQuote(Finalizing the SDK)"\
"#(E)$$SDK_SCRIPT $$SDKROOT"\
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(The SDK has been finalized.)"\
"#(eh)echo $$shellQuote(It can now be deployed to another computer.)"\
"#(eh)echo $$shellQuote()"\
"#(eh)echo $$shellQuote(Note that you should run configure before building again.)"\
"#(eh)echo $$shellQuote()"
}共105行。

现在在做qt的移植,但是就是没有移植过去,希望能够尽快解决,谢谢
...全文
168 5 打赏 收藏 转发到动态 举报
写回复
用AI写文章
5 条回复
切换为时间正序
请发表友善的回复…
发表回复
闪电侠风行 2011-10-08
  • 打赏
  • 举报
回复
[Quote=引用 3 楼 yong_f 的回复:]

配置不对吧
[/Quote]


你好,你能给我指点一下吗,具体是什么地方配置不对,请你尽可能详细的说一下,我好着手修改。
yong_f 2011-10-08
  • 打赏
  • 举报
回复
配置不对吧
闪电侠风行 2011-10-08
  • 打赏
  • 举报
回复
谢谢楼上的回复,我已经换过好几个编译器了,4.3.2,gcc4.4.3,gcc3.4.1,gcc4.2.2等等,我都用过的,都是报上面同样的错误,让我很头疼阿
闪电侠风行 2011-10-08
  • 打赏
  • 举报
回复
对于这个问题,我仍然不知道他的错误在哪里,但是我换了个版本(改为buntu9.10)试了以下,看着里面还有很多的错误,但是初期的那些报错还在,不过那些小错误,通过编译了。
念茜 2011-10-07
  • 打赏
  • 举报
回复
换编译器试试,4.3.2通过率比较高
源码下载地址: https://pan.quark.cn/s/a4b39357ea24 谷歌公司设计了一款无费用且具备开源特性的网络浏览器,名为Chrome,因其卓越的速度、稳定性和安全性而广受赞誉。该浏览器运用了前沿的Web渲染引擎Blink以及JavaScript引擎V8,旨在保障网页载入与脚本运行的卓越效能。为应对无网络环境下的Chrome安装需求,特别准备了离线安装包。此压缩文件内含32位与64位两种规格的Chrome浏览器离线安装方案,具体文件名分别为"chromedev_x64-v68.0.3423.2.exe"与"chromedev_x86-v68.0.3423.2.exe"。在文件命名中,"x64"标识64位版本,适用于64位操作系统平台,而"x86"则对应32位版本,适配32位操作系统。文件名中的"v68.0.3423.2"代表Chrome的一个特定版本号,各版本可能涵盖安全补丁、性能改进或新增功能。与32位Chrome相比,64位版本具备如下长处:能够处理更多内存容量,从而提升多任务作业能力;针对现代硬件的优化使其运行更为迅猛;64位版本更具备高级别的安全防护,能更周全地抵御恶意软件的侵袭。尽管如此,32位版本对于仍在使用32位操作系统的用户,或是在系统资源需求不高的场景下,依然适用。在部署Chrome浏览器,用户需依据其个人计算机的操作系统平台,挑选匹配的版本进行安装。通过双击相应的.exe文件,安装流程将自动启动,一般包含接受使用许可、确定安装路径及构建桌面快捷方式等环节。若在安装阶段遭遇难题,可参照提示信息或联系技术支援获取协助,同该压缩文件发布者亦表明欢迎用户以留言形式反映问题。Chrome浏览器的主要特质涵盖:直观的用户界面设计...

23,223

社区成员

发帖
与我相关
我的任务
社区描述
Linux/Unix社区 应用程序开发区
社区管理员
  • 应用程序开发区社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧