StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7135987
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-21T02:45:24.573
FavoriteCount
0
LastActivityDate
2011-08-21T02:56:13.587
LastEditDate
2011-08-21T02:56:13.587
LastEditorUserId
207321
OwnerUserId
207321
ParentId
7033610
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
As baysmith says, if your goal is to keep your source directory clean, the real solution is to use CMake's <a href="http://www.cmake.org/Wiki/CMake_FAQ#Out-of-source_build_trees" rel="nofollow">"out-of-source"</a> builds feature. If you're on Windows, set "Where to build the binaries" to a new directory, different from the "Where is the source code" directory. If you're on Unix, it goes something like this: <pre><code>cd <source directory> mkdir build cd build cmake .. make </code></pre> By running CMake on a different directory, all of the build files will go into that directory, and your sources will stay clean. (Note: the build directory doesn't have to be inside the source directory. See the <a href="http://www.cmake.org/Wiki/CMake_FAQ#Out-of-source_build_trees" rel="nofollow">CMake wiki</a> for more details.) If "out-of-source" doesn't work for you, I was able to find one other option. Based on what I can tell from the <code>Qt4Macros.cmake</code> file installed with my CMake 2.8, it isn't accessible as a config parameter. Here's the relevant line: <pre><code>SET(_moc ${CMAKE_CURRENT_BINARY_DIR}/${_current_MOC}) </code></pre> The workaround is to change all of your MOC include directives to specify the subfolder you'd like to build to. <pre><code>#include "moc/mainwindow.moc" </code></pre> After creating the <code>moc</code> directory inside my build directory, there were no problems building, and my MOC file was in the new directory.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCMake + Qt : define the moc/ui output directory
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDan Cecile
UserOwnerUserId
1. USDan Cecile
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCMake + Qt : define the moc/ui output directory
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.