后使用快捷导航没有帐号？
只需一步，快速开始
查看: 1775|回复: 8
最后登录贡献度34 金元1417 银行存款0 注册时间阅读权限50帖子主题精华0积分278UID2755693
高级玩家, 积分 278, 距离下一级还需 222 积分
贡献度34 金元1417 注册时间积分278精华0帖子
本帖最后由 kaine1419 于
02:07 编辑
游戏下载的版本是
《无主之地2》3DM简体中文汉化硬盘版v2.0
WIN7 64开不出游戏为什么？VC++都装了还是不行
出现几个问题。
没装VC++2010 86时候报出丢失msvcp100.dll装好后。游戏双点不报错但是打不开我用力管理员权限打开也不行。兼容XP也不行。steam平台都安装好了也没用郁闷了
02:01 上传
02:05 上传
这些全装了打开游戏还是没反应。
最后登录贡献度1 金元897 银行存款0 注册时间阅读权限30帖子主题精华0积分94UID3377286
中级玩家, 积分 94, 距离下一级还需 106 积分
贡献度1 金元897 注册时间积分94精华0帖子
应该是游戏破解的问题。去找一款适合你的破解…
最后登录贡献度8 金元2678 银行存款0 注册时间阅读权限50帖子主题精华0积分300UID4295257
高级玩家, 积分 300, 距离下一级还需 200 积分
贡献度8 金元2678 注册时间积分300精华0帖子
大概自三号升级挡这个问题我就没弄好过。总是说什么要免steam免steam的，我不但早已装了steam，免steam注册表也导入了，还尝试过用steam运行，都不行。放弃这个游戏吧。不然去买。
最后登录贡献度117 金元9659 银行存款0 注册时间阅读权限90帖子主题精华0积分1434UID1688763
游戏狂人, 积分 1434, 距离下一级还需 66 积分
贡献度117 金元9659 注册时间积分1434精华0帖子
下整合版的吧。。。。。
最后登录贡献度24 金元5414 银行存款0 注册时间阅读权限70帖子主题精华0积分637UID4329700
超级玩家, 积分 637, 距离下一级还需 163 积分
贡献度24 金元5414 注册时间积分637精华0帖子
楼主装游戏前没看说明？这个游戏运行之前，要先脱机运行一次。然后以后就没关系了
最后登录贡献度1 金元487 银行存款0 注册时间阅读权限30帖子主题精华0积分53UID4370604
中级玩家, 积分 53, 距离下一级还需 147 积分
贡献度1 金元487 注册时间积分53精华0帖子
我啥也不装都能运行，只能说楼主太白了
最后登录贡献度30 金元4035 银行存款0 注册时间阅读权限70帖子主题精华0积分524UID2174121
超级玩家, 积分 524, 距离下一级还需 276 积分
贡献度30 金元4035 注册时间积分524精华0帖子
本帖最后由 gprs1986 于
15:44 编辑
每次都有类似问题，尽量少用XXXX这类软件优化系统 一键清理或者注册表垃圾清理。系统优化过头麻烦问题多的是！
最后登录贡献度35 金元4384 银行存款0 注册时间阅读权限70帖子主题精华0积分578UID2556534
超级玩家, 积分 578, 距离下一级还需 222 积分
贡献度35 金元4384 注册时间积分578精华0帖子
我下载的也是这个版本，WIN7X64下就装了个DX，直接进啊。
六楼也是直接进的。
Powered byQt for Windows - Deployment | Qt 5.4
Qt for Windows - Deployment
Qt for Windows - Deployment
This documentation describes deployment issues for . We demonstrate the procedures in terms of deploying the
application that is provided in Qt's examples directory.
Static Linking
To build static applications, build Qt statically by configuring Qt with -static:
cd C:\path\to\
configure -static &any other options you need&
If you later need to reconfigure and rebuild Qt from the same location, ensure that all traces of the previous configuration are removed by entering the build directory and running nmake distclean or mingw32-make distclean before running configure again.
Linking the Application to the Static Version of Qt
As an example, this section will build the
example statically.
Once Qt finishes building, build the
application. First we must go into the directory that contains the application:
cd examples\tools\plugandpaint
Run qmake to create a new makefile for the application, and perform a clean build to create the statically linked executable:
nmake clean
qmake -config release
You probably want to link against the release libraries, and you can specify this when invoking qmake. Now, provided that everything compiled and linked without any errors, we should have a plugandpaint.exe file that is ready for deployment. To check that the application has the required libraries, copy the executable to a machine that does not have Qt or any Qt applications installed, and run it on that machine.
Remember that if your application depends on compiler specific libraries, these must still be redistributed along with your application. You can check which libraries your application is linking against by using the depends tool. For more information, read the
Since we cannot deploy plugins using the static linking approach, the application we have prepared is incomplete. It will run, but the functionality will be disabled due to the missing plugins. To deploy plugin-based applications we should use the shared library approach.
Shared Libraries
We have two challenges when deploying the
application using the shared libraries approach: The Qt runtime has to be correctly redistributed along with the application executable, and the plugins have to be installed in the correct location on the target system so that the application can find them.
Building Qt as a Shared Library
For this example, we assume that Qt is installed as a shared library, which is the default when installing Qt, in the C:\path\to\Qt directory.
Linking the Application to Qt as a Shared Library
After ensuring that Qt is built as a shared library, we can build the
application. First, we must go into the directory that contains the application:
cd examples\tools\plugandpaint
Now run qmake to create a new makefile for the application, and do a clean build to create the dynamically linked executable:
nmake clean
qmake -config release
This builds the core application, the following will build the plugins:
cd ..\plugandpaintplugins
nmake clean
qmake -config release
If everything compiled and linked without any errors, we will get a plugandpaint.exe executable and the pnp_basictools.dll and pnp_extrafilters.dll plugin files.
Creating the Application Package
To deploy the application, we must make sure that we copy the relevant Qt DLLs (corresponding to the Qt modules used in the application) and the Windows platform plugin, qwindows.dll, as well as the executable to the same directory tree in the release subdirectory.
In contrast to user plugins, Qt plugins have to be put into subdirectories matching the plugin type. The correct location for the platform plugin is a subdirectory named platforms.
section has additional information about plugins and how Qt searches for them.
Qt relies on the
library for unicode support. Therefore, you must include the ICU DLLs that are located in the bin directory of your Qt installation if Qt was configured to use ICU. The Qt version bundled in the Qt5 package uses ICU, so deployment is needed there. The ICU DLLs are version dependent and have to match the ones your Qt version was linked against.
If you are using
(the default) then you additionally need to include both libEGL.dll and libGLESv2.dll from Qt's 'lib' directory as well as the HLSL compiler from DirectX. The HLSL compiler library is called d3dcompiler_XX.dll where XX is the version number that ANGLE (libGLESv2) was linked against.
Remember that if your application depends on compiler specific libraries, these must be redistributed along with your application. You can check which libraries your application is linking against by using the depends tool. For more information, see the
We'll cover the plugins shortly, but first we'll check that the application will work in a deployed environment: Either copy the executable and the Qt DLLs to a machine that doesn't have Qt or any Qt applications installed, or if you want to test on the build machine, ensure that the machine doesn't have Qt in its environment.
If the application starts without any problems, then we have successfully made a dynamically linked version of the
application. But the application's functionality will still be missing since we have not yet deployed the associated plugins.
Plugins work differently to normal DLLs, so we can't just copy them into the same directory as our application's executable as we did with the Qt DLLs. When looking for plugins, the application searches in a plugins subdirectory inside the directory of the application executable.
So to make the plugins available to our application, we have to create the plugins subdirectory and copy over the relevant DLLs:
plugins\pnp_basictools.dll
plugins\pnp_extrafilters.dll
An archive distributing all the Qt DLLs and application specific plugins required to run the
application, would have to include the following files:
ComponentFile Name
The executableplugandpaint.exe
The Basic Tools pluginplugins\pnp_basictools.dll
The ExtraFilters pluginplugins\pnp_extrafilters.dll
The Qt Windows platform pluginplatforms\qwindows.dll
The Qt Core moduleQt5Core.dll
The Qt GUI moduleQt5Gui.dll
The Qt Widgets moduleQt5Widgets.dll
In addition, the archive must contain the following compiler specific libraries depending on your version of Visual Studio:
VC++ 8.0 (2005)VC++ 9.0 (2008)VC++ 10.0 (2010)
The C run-timemsvcr80.dllmsvcr90.dllmsvcr100.dll
The C++ run-timemsvcp80.dllmsvcp90.dllmsvcp100.dll
If ICU was used, the archive must contain:
icudtXX.dllicuinXX.dllicuucXX.dll
Finally, if ANGLE was used, then the archive must additionally contain:
libEGL.dlllibGLESv2.dlld3dcompiler_XX.dll
To verify that the application now can be successfully deployed, you can extract this archive on a machine without Qt and without any compiler installed, and try to run it.
An alternative to putting the plugins in the plugins subdirectory is to add a custom search path when you start your application using () or ().
qApp-&addLibraryPath(&C:\some\other\path&);
One benefit of using plugins is that they can easily be made available to a whole family of applications.
It's often most convenient to add the path in the application's main() function, right after the
object is created. Once the path is added, the application will search it for plugins, in addition to looking in the plugins subdirectory in the application's own directory. Any number of additional paths can be added.
Manifest files
When deploying an application compiled with Visual Studio 2005 onwards, there are some additional steps to be taken.
First, we need to copy the manifest file created when linking the application. This manifest file contains information about the application's dependencies on side-by-side assemblies, such as the runtime libraries.
The manifest file needs to be copied into the same folder as the application executable. You do not need to copy the manifest files for shared libraries (DLLs), since they are not used.
If the shared library has dependencies that are different from the application using it, the manifest file needs to be embedded into the DLL binary. Since Qt 4.1.3, the following CONFIG options are available for embedding manifests:
embed_manifest_dll
embed_manifest_exe
To use the options, add
CONFIG += embed_manifest_exe
to your .pro file. The embed_manifest_dll option is enabled by default. The embed_manifest_exe option is NOT enabled by default.
You can find more information about manifest files and side-by-side assemblies at the .
The correct way to include the runtime libraries with your application is to ensure that they are installed on the end-user's system.
To install the runtime libraries on the end-user's system, you need to include the appropriate Visual C++ Redistributable Package (VCRedist) executable with your application and ensure that it is executed when the user installs your application.
For example, on an 32-bit x86-based system, you would include the
executable. The
executables provide the appropriate libraries for the IA64 and 64-bit x86 architectures, respectively.
Note: The application you ship must be compiled with exactly the same compiler version against the same C runtime version. This prevents deploying errors caused by different versions of the C runtime libraries.
Manual installations with Visual Studio 2008 and 2010
As well as the above details for VS 2005 and onwards, Visual Studio
applications may have problems when deploying manually, say to a USB stick.
The recommended procedure is to configure Qt with the -plugin-manifests option using the 'configure' tool. Then follow the
for manually deploying private assemblies.
In brief the steps are
create a folder structure on the development computer that will match the target USB stick directory structure, for example '\app' and for your dlls, '\app\lib'.
on the development computer, from the appropriate 'redist' folder copy over Microsoft.VC80.CRT and Microsoft.VC80.MFC to the directories '\app' and '\app\lib' on the development PC.
xcopy the \app folder to the target USB stick.
Your application should now run. Also be aware that even with a service pack installed the Windows DLLs that are linked to will be the defaults. See the information on .
Application Dependencies
Additional Libraries
Depending on configuration, compiler specific libraries must be redistributed along with your application.
For example, if Qt is built using , its shared libraries and the required shared libraries of the
need to be shipped as well.
You can check which libraries your application is linking against by using the
tool. All you need to do is to run it like this:
depends &application executable&
This will provide a list of the libraries that your application depends on and other information.
When looking at the release build of the Plug & Paint executable (plugandpaint.exe) with the depends tool, the tool lists the following immediate dependencies to non-system libraries:
QtVC++ 10.0 (2010)VC++ 11.0 (2012)VC++ 12.0 (2013)
QT5CORE.DLL - The
QT5GUI.DLL - The
QT5WIDGETS.DLL - The
MSVCR100.DLL - The C runtime
MSVCP100.DLL - The C++ runtime
MSVCR110.DLL - The C runtime
MSVCP110.DLL - The C++ runtime
MSVCR120.DLL - The C runtime
MSVCP120.DLL - The C++ runtime
LIBWINPTHREAD-1.DLL
LIBGCC_S_DW2-1.DLL
LIBSTDC++-6.DLL
When looking at the plugin DLLs the exact same dependencies are listed.
Qt Plugins
All Qt GUI applications require a plugin that implements the
(QPA) layer in Qt 5. For Windows, the name of the platform plugin is qwindows.dll. This file must be located within a specific subdirectory (by default, platforms) under your distribution directory. Alternatively, it is possible to adjust the search path Qt uses to find its plugins, as described below.
Your application may also depend on one or more Qt plugins, such as the print support plugin, the JPEG image format plugin or a SQL driver plugin. Be sure to distribute any Qt plugins that you need with your application. Similar to the platform plugin, each type of plugin must be located within a specific subdirectory (such as printsupport, imageformats or sqldrivers) within your distribution directory.
Note: If you are deploying an application that uses Qt WebKit to display HTML pages from the World Wide Web, you should include all text codec plugins to support as many HTML encodings possible.The search path for Qt plugins is hard-coded into the
library. By default, the plugins subdirectory of the Qt installation is the first plugin search path. However, pre-determined paths like the default one have certain disadvantages. For example, they may not exist on the target machine. For that reason, you need to examine various alternatives to make sure that the Qt plugins are found:
. This approach is the recommended if you have executables in different places sharing the same plugins.
Using () or (). This approach is recommended if you only have one executable that will use the plugin.
Using a third party installation utility to change the hard-coded paths in the
If you add a custom path using
it could look like this:
qApp-&addLibraryPath(&C:/customPath/plugins&);
Then -&libraryPaths() would return something like this:
C:/customPath/plugins
C:/Qt/%VERSION%/plugins
E:/myApplication/directory
The executable will look for the plugins in these directories and the same order as the
returned by -&libraryPaths(). The newly added path is prepended to the -&libraryPaths() which means that it will be searched through first. However, if you use -&setLibraryPaths(), you will be able to determine which paths and in which order they will be searched.
document outlines the issues you need to pay attention to when building and deploying plugins for Qt applications.
The Windows Deployment Tool
The Windows deployment tool can be found in QTDIR/bin/windeployqt. It is designed to automate the process of creating a deployable folder that contains all libraries, QML imports, plugins, translations that are required to run the application from that folder. This is used to create the sandbox for
or an installation tree for Windows desktop applications that can be easily bundled by an installer.
Usage: windeployqt [options] [files]
Qt Deploy Tool 5.4.0
The simplest way to use windeployqt is to add the bin directory of your Qt
installation (e.g. &QT_DIR\bin&) to the PATH variable and then run:
windeployqt &path-to-app-binary&
If ICU, ANGLE, etc. are not in the bin directory, they need to be in the PATH
variable. If your application uses Qt Quick, run:
windeployqt --qmldir &path-to-app-qml-files& &path-to-app-binary&
-?, -h, --help
Displays this help.
-v, --version
Displays version information.
--dir &directory&
Use directory instead of binary directory.
--libdir &path&
Copy libraries to path.
Assume debug binaries.
Assume release binaries.
--release-with-debug-info
Assume release binaries with debug information.
Force updating files.
Simulation mode. Behave normally, but do not
copy/update any files.
--no-plugins
Skip plugin deployment.
--no-libraries
Skip library deployment.
--qmldir &directory&
Scan for QML-imports starting from directory.
--no-quick-import
Skip deployment of Qt Quick imports.
--no-translations
Skip deployment of translations.
--no-system-d3d-compiler
Skip deployment of the system D3D compiler.
--compiler-runtime
Deploy compiler runtime (Desktop only).
--no-compiler-runtime
Do not deploy compiler runtime (Desktop only).
Deployment of WebKit2 (web process).
--no-webkit2
Skip deployment of WebKit2.
Print to stdout in JSON format.
Force deployment of ANGLE.
--no-angle
Disable deployment of ANGLE.
--list &option&
Print only the names of the files copied.
Available options:
absolute path of the source files
absolute path of the target files
relative: paths of the target files, relative
to the target directory
outputs the source and the relative
target, suitable for use within an
Appx mapping file
--verbose &level&
Verbose level.
Qt libraries can be added by passing their name (-xml) or removed by passing
the name prepended by --no- (--no-xml). Available libraries:
bluetooth clucene concurrent core declarative designer designercomponents
enginio gui qthelp multimedia multimediawidgets multimediaquick network nfc
opengl positioning printsupport qml qmltooling quick quickparticles quickwidgets
script scripttools sensors serialport sql svg test webkit webkitwidgets
websockets widgets winextras xml xmlpatterns webenginecore webengine
webenginewidgets
Arguments:
Binaries or directory containing the binary.
& 2015 The Qt Company Ltd.
Documentation contributions included herein are the copyrights of
their respective owners.
The documentation provided herein is licensed under the terms of the
as published by the Free Software Foundation.
Qt and respective logos are trademarks of The Qt Company Ltd.
in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners.1015人阅读
&&&&&& 运行haar分类进行训练样本的时候出现了，msvcp100.dll缺失的问题，开始了自己的纠结征程。
&&&&&& 主要解决过程，截图之类的就免了，已经解决掉了，写下大致过程来记录下的。
&&&&&& 首先是上网下载了msvcp100.dll放在了C:WINDOWS/system32目录下，然后“开始-运行-输入regsvr32 msvcp100.dll”，回车，好了新的错误出现了，具体忘了是什么错误了，反正是导致我去下载msvcr100.dll文件，同样复制到C:WINDOWS/system32目录下，然后“开始-运行-输入regsvr32 msvcr100.dll”，回车。错误依旧还是存在的，记得貌似是找不到程序入口点，好吧，那就只能网上找了，网上说得安装VC2010，我没办法就只能是下载了个VC2010运行库进行安装，安装完成后期望能够解决问题的。
&&&&&& 完成安装进行测试发现还是不行，缺少“tbb.dll”（之前缺少过tbb_debug，同样方法解决的），好吧，缺少那我就找了，我是在OpenCV2.3.1的安装包中搜索的这个文件，发现还真存在，路径是..\OpenCV2.3.1\opencv\build\common\tbb\ia32\vc9。将这个文件拷贝到我设置的环境变量PATH目录下：G:\OpenCV2.3.1\opencv\build\x86\vc9\bin，然后再次测试发现问题解决了。目前正在样本训练中。。。
参考的网站
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：43619次
排名：千里之外
原创：19篇
转载：58篇
(1)(8)(3)(6)(1)(11)(5)(9)(1)(6)(8)(2)(1)(3)(1)(11)