![]() ![]() limits the components to be build from sources to those interacting with the AUT directly.The quickest route to such a customized installation: ![]() Any of these may differ from the versions and configurations used for the pre-built binary packages. The main influencing factors are the Qt libraries, compiler, and hardware. The most often found use case for such a minimal build is to create a custom build of those components that will have to match the environment of the tested application. If you need non-standard compiler options or a non-standard Qt configuration, you have to compile Squish from sources using the very same compiler and Qt library that is being used for the appliction. You can build Squish from sources for testing Qt applications built with a native compiler by using a prebuilt binary package. If your setup does not meet the Quick Install requirements, you can still build Squish from source, but you will need to follow one of the non-standard build processes that are documented after the Quick Install section. In many common cases, the build process can be done in just a few simple steps, as described in Quick Install. Once the tools have been built, you can install the Squish IDE. Once Squish is built, it can be distributed to different computers running the same operating system, as instructed in Distributing and Sharing an Installation.įor source builds, Squish is supplied as two separate packages: the Squish tools source package that must be built and the Squish IDE package that just needs to be installed. However, you can build it from source if no suitable binary package is available or if you need to use features that require a source build, for example. In most situations, Squish can be quickly and easily installed from a binary package. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |