StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POmakefile simplifying
primarykey
Id
10130409
data
AcceptedAnswerId
10131678
AnswerCount
3
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2012-04-12T19:27:45.587
FavoriteCount
1
LastActivityDate
2012-04-13T06:52:54.063
LastEditDate
2012-04-13T06:52:54.063
LastEditorUserId
135448
OwnerUserId
1145239
ParentId
0
PostTypeId
1
Score
0
ViewCount
357
LastEditorDisplayName
text
Body
<p>Suppose we have client-server application, compiling by one makefile. Server uses libtask for parallel clients serving. Client uses ncurses for some graphic. directory tree looks like this:</p> <pre><code>./ --bin/ --obj/ --src/ ----client/*.c ----server/*.c --makefile </code></pre> <p>So, here is makefile. Can we simplify it? I read some related questions on stackoverflow and I think it almost ideal, except of linking binaries, when we can see repeated commands. Some suggestions for style/cross-platform working will be useful. Thank you!</p> <pre><code>.PHONY: all clean TASKLIB = -ltask CURSESLIB = -lncurses CFLAGS = -Wall -Werror -pedantic bin = server client obj_dir = obj bin_dir = bin ssource := src/server csource := src/client search_wildcard s := $(addsuffix /*.c, $(ssource)) search_wildcard c := $(addsuffix /*.c, $(csource)) sobjs = $(addprefix $(obj_dir)/, $(patsubst %.c, %.o, $(notdir $(wildcard $(search_wildcard s))))) cobjs = $(addprefix $(obj_dir)/, $(patsubst %.c, %.o, $(notdir $(wildcard $(search_wildcard c))))) all: $(bin) @echo "done!" server: CFLAGS+=$(TASKLIB) client: CFLAGS+=$(CURSESLIB) clean: rm $(sobjs) $(cobjs) $(obj_dir)/*.d $(bin_dir)/client $(bin_dir)/server VPATH := $(ssource) $(csource) server: $(sobjs) @test -d $(bin_dir) || mkdir $(bin_dir) @echo "Linking $(@F)..." @$(CC) $< $(CFLAGS) -o $(bin_dir)/$@ client: $(cobjs) @test -d $(bin_dir) || mkdir $(bin_dir) @echo "Linking $(@F)..." @$(CC) $< $(CFLAGS) -o $(bin_dir)/$@ $(obj_dir)/%.o: %.c @test -d $(obj_dir) || mkdir $(obj_dir) @echo "Compiling $(@F)..." @$(CC) $< $(CFLAGS) -c -MD -o $@ include $(wildcard $(obj_dir)/*.d) </code></pre>
Tags
<c><makefile>
Title
makefile simplifying
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAndreas Wong
UserOwnerUserId
1. USJIghtuse
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. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POmakefile simplifying
  UserUserId
  USSuperJames
  VoteTypeVoteTypeId
  VTFavorite
2. VO
  singulars
  PostPostId
  POmakefile simplifying
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTApproveEditSuggestion
CommentsPostId

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.