To speed up the compilation process by running it on multiple cores, you may optionally use jom instead of mingw-make. Start texstudio.exe (Strg+R in Qt Creator).Change in texstudio.pro "LIBS += -lzlib \" to "LIBS += C:\yourPath\libzlib1.dll \" if "libzlib.dll" is not found by the linker (in the build step), try to set an aboslute reference.Optionally change the target (debug/release).This is done in Build Settings -> Make -> Make arguments (see image to the right). To build a release version, make needs a relase command line argument. In that case you would have to select the python-based version in the options yourself (in my case that was C:\QtSDK\pythongdb\python_2.7based\gdb-i686-pc-mingw32.exe). It may be that the automatic detection selects the native mingw gdb, which won't work with Qt Creator. For the mingw toolchain, this would be the gdb (python-based version supplied with Qt SDK. This is what I did: If you do not only run the application but run it through a debugger, you will need to additionally setup a debugger. Please confirm if you tried it).įormerly one needed to setup the debugger manually. Recent QtCreator documentation suggests that debugging now works out of the box (I have not tested this so far. For a distributable version you should build a relase version. However this is not suited for distribution, because the application will depend on the debug versions of the Qt dlls. No further settings are required to build and run the application. This creates a debug and a relase target. When you open texstudio.pro for the first time in QtCreator, it will ask you for the targets. If the dlls are not in the correct directory, the build will fail with a message on missing dlls. It depends on your setting in QtCreator.) You may skip this step and perfrom it later after setting up the build in QtCreator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |