Typos

parent 01c111be
......@@ -22,16 +22,16 @@ limitations under the License.
#### Qt Creator and Windows platform
The Qt Creator requires the paths to all libraries required, but they are not automatically added to the environment. Otherwise the program execution will immediately crash without any further useful information (the reason is: it can't locate runtime libraries).
The Qt Creator requires the paths to all dependent libraries, but they are not automatically added to the environment. Otherwise, the program execution will immediately crash without any further useful information (the reason is: it can't locate runtime libraries).
A workaround:
1. Copy the `platform` folder from the Qt binaries into the `bin` folder of the project, usually a crypting name like `build-Redstart-Desktop_Qt_5_6_0_MSVC2013_64bit-Release` or similar.
2. Deploy VA with Visual Studio, you will find a folder called something like `dist/win32-x64.vc12/bin`. Add this diectory as PATH entry in Qt Creator > Project in the Build Environment section.
1. Copy the `platform` folder from the Qt binaries into the `bin` folder of the project, usually a cryptic name like `build-Redstart-Desktop_Qt_5_6_0_MSVC2013_64bit-Release` or similar.
2. Deploy VA with Visual Studio using the INSTALL directive. It will assemble binaries of the Redstart application and you will find a folder called something like `dist/win32-x64.vc12/bin`. Add this directory as PATH entry in Qt Creator > Project in the Build Environment section.
Do not forget to Build & Install VA in Visual Studio in case you modify the core! Copying DLLs is always dangerous during development ...
Do not forget to Build & Install Redstart/VA in Visual Studio in case you modify the core! Copying DLLs is always dangerous during development ...
Now you can run the program from within Qt Creator. Repeat this for every kit you want to use.
#### Visual Studio and Windows platform
You can edit the UI with Qt Designer, but Visual Studio may fail to generate / modify the source code automatically, because modification detection is not perfect. In this case it is sometimes necessary to clean up the intermediate source files in the build folder. But generally, VS is able to run Qt specific compiler calls prior to compiling the application, cmake and qmake take care of this.
You can edit the UI with Qt Designer, but Visual Studio may fail to generate / modify the source code automatically, because modification detection is not always picking up changes. In this case it is sometimes necessary to clean up the intermediate source files in the build folder. But generally, VS is able to run Qt specific compiler calls prior to compiling the application, cmake and qmake take care of this.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment