StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9123302
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-03T03:29:52.820
FavoriteCount
0
LastActivityDate
2012-02-03T03:40:49.040
LastEditDate
2012-02-03T03:40:49.040
LastEditorUserId
14860
OwnerUserId
14860
ParentId
9123269
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
If your executable depends on its source code and another object, you need to link in the object as well. You can change your first (real) rule to something like (you may also need <code>HeatingUnit</code> stuff in both the dependency list and the <code>g++</code> command): <pre><code>TempControlTest: TempControlTest.cpp BangBangControl.o g++ -o TempControlTest TempControlTest.cpp BangBangControl.o </code></pre> You should also keep in mind that you may need dependencies on header files as well. Without that, a change to <code>BangBangControl.h</code> would not rebuild <code>BangBangControl.o</code> or <code>TempControlTest</code>. And, this is personal preference, I always make every rul depend on the <code>makefile</code> file as well so that, if I change the makefile, everything gets rebuilt automatically. Based on all your file contents, I would have something like: <pre><code># Non-file rules (all is default). all: TempControlTest clean: rm -rf *.o TempControlTest # Build executable from all objects. TempControlTest: makefile TempControlTest.o BangBangControl.o HeatingControl.o g++ -o TempControlTest TempControlTest.o BangBangControl.o HeatingControl.o # Build objects from source (C and headers). TempControlTest.o: makefile TempControlTest.cpp BangBangControl.h g++ -c TempControlTest.cpp BangBangControl.o: makefile BangBangControl.cpp BangBangControl.h HeatingUnit.h g++ -c BangBangControl.cpp HeatingUnit.o: makefile HeatingUnit.cpp HeatingUnit.h g++ -c HeatingUnit.cpp </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMy makefile isn't working
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpaxdiablo
UserOwnerUserId
1. USpaxdiablo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. 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.