Qt Creator IDE的构建目录

Question

I am trying to populate a QTableview with some data. When developing under Qt Creator, data is read from build directory. Running the program each time, the QTableview keeps getting repopulated with previous data.

If I manually change the build directory each time before run, doesn't happen. But how do I solve the problem without manually changing the build directory every time I want a fresh run?

Answer 1

In your project directory there is a file name ProjectName.pro.user .

This file creating when you configure your project. it's XML file.

you can find this line on *.user files:

<value type="QString" key="ProjectExplorer.BuildConfiguration.BuildDirectory">C:/Users/probook/Documents/Qt/testProject/Build/Windows/Debug</value>

This line define build directory address for debug. there is a same line for Release and Profile in that file.

You can also use Qt creator to define(customize) relative directory build: goto Qt creator, Tools , Options... , Build & Run , General , Default build directory .

More info:

Qt Creator stores user-specific project settings in a .pro.user file. You can share these settings between several projects as a .pro.shared file. It has the same XML structure as a .pro.user file, but only contains the settings to share.

Answer 2

Based on comment, issue seems to be data which gets saved to build directory. And solution would be to remove it before running the application.

You can add Custom Process Step , either under Projects - Build Settings - Build Steps , or under Projects - Run Settings - Deployment , and just delete the desired data files. Exact command depends on operating system.

An alternative might be to add a command line switch, something like --development-erase-saved-data , to the application itself, and erase the files (or just not read them, or whatever). Then add that command line switch to Projects - Run Settings - Run Steps - Command Line Arguments for desired build configurations.

Adding support for this in the application itself is easier to maintain, and is almost automatically cross-platform. However, it might be a feature you don't want in the application, though in that case you might only enable it for Debug builds (with #ifdef ).

---

As a side note, saving data to executable directory is not a good idea these days. You might want to save it for example to location returned by

QStandardPaths::writableLocation(QStandardPaths::AppDataLocation)

(See here for more info.)