Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So short answer: You can't. Those settings are the reason why it is a .user file: They reference settings that are specific to one Qt Creator instance.</p> <p>Long answer: We are moving to support this use case better, 2.6 was a huge step in that direction. With 2.6 you <em>might</em> be able to share build/deploy/run settings, <em>but</em> you need to make sure everybody using that .user file has compatible kits with exactly the same ids. You also need to make sure that everybody is using the same paths to sources, builds, operating system, etc. which limits its use quite a bit.</p> <p>This might work e.g. with the Qt 5 kit installed by the official Qt 5 packages or with kits created specially for your setup. This will fail in any setup where you do not have tight control over all the development setups! On the other hand: If somebody is using a non-default setup of creator (kits, paths, etc.) then creator will just throw away some or all kit defined in the .user file of the project and will then continue, asking for kits to use. That is exactly what you will get without a .shared/.user file available at all.</p> <p>Please be aware that as far as I know nobody ever tested such a setup. So you will most likely run into bugs and misbehavior... if you do: Please file bug reports at <a href="https://bugreports.qt.io/" rel="nofollow noreferrer">https://bugreports.qt.io/</a> ;-)</p> <p>If you have only one environment you are targeting with your development, then you can get pretty far by having that environment set up (e.g. you only have one compiler/Qt version/kit defined that is exactly what you want everybody to use). Creator will then just default to that one, even if you have no .user file at all.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to specify build, deployment, and run configuration in a Qt Creator `.pro.shared` file?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMBach
    1. USTobias Hunger
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to specify build, deployment, and run configuration in a Qt Creator `.pro.shared` file?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAh, that makes sense. Thanks. We're working on fairly disparate build environments, so that won't work. My main concern is that we have a large Qmake SUBDIRS project, which has a lot of test targets, and I'd like for these test targets not to show up in Qt Creator when a user sets up a new development environment, since they're rarely useful to run independently — I'd prefer to have developers just run `make check` on the command line to run all the tests at once. Is there any way to just control whether a subproject shows up as a target in Qt Creator?
      singulars
      1. PO
      1. USsmokris
    2. CONot yet, but you might want to add that as a feature request to https://bugtracker.qt-project.org/ :-)
      singulars
      1. PO
      1. USTobias Hunger
    3. COAdded: https://bugreports.qt-project.org/browse/QTCREATORBUG-8482
      singulars
      1. PO
      1. USsmokris
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload