makefile parse target to define dependencies












1















I have source files in several directories and I want to compile them in a one unique temporary directory, currently I use this target to create my object files :



$(BUILD_DIR)/%.o : 
@echo "Compiling $@"
$(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')


It is working well but when I modify a source file, the object one is not recompiled. So I have to add the source file to the dependencies.



But this target doesn't work :



$(BUILD_DIR)/%.o : $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')
@echo "Compiling $@"
$(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $^


Is there any way to use target name in dependencies ?










share|improve this question



























    1















    I have source files in several directories and I want to compile them in a one unique temporary directory, currently I use this target to create my object files :



    $(BUILD_DIR)/%.o : 
    @echo "Compiling $@"
    $(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')


    It is working well but when I modify a source file, the object one is not recompiled. So I have to add the source file to the dependencies.



    But this target doesn't work :



    $(BUILD_DIR)/%.o : $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')
    @echo "Compiling $@"
    $(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $^


    Is there any way to use target name in dependencies ?










    share|improve this question

























      1












      1








      1


      0






      I have source files in several directories and I want to compile them in a one unique temporary directory, currently I use this target to create my object files :



      $(BUILD_DIR)/%.o : 
      @echo "Compiling $@"
      $(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')


      It is working well but when I modify a source file, the object one is not recompiled. So I have to add the source file to the dependencies.



      But this target doesn't work :



      $(BUILD_DIR)/%.o : $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')
      @echo "Compiling $@"
      $(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $^


      Is there any way to use target name in dependencies ?










      share|improve this question














      I have source files in several directories and I want to compile them in a one unique temporary directory, currently I use this target to create my object files :



      $(BUILD_DIR)/%.o : 
      @echo "Compiling $@"
      $(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')


      It is working well but when I modify a source file, the object one is not recompiled. So I have to add the source file to the dependencies.



      But this target doesn't work :



      $(BUILD_DIR)/%.o : $(shell echo "$(SOURCES)" | sed 's/ /n/g' | sed -nr '//$(*F).c/p')
      @echo "Compiling $@"
      $(VERBOSE) $(CC) $(CFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $^


      Is there any way to use target name in dependencies ?







      makefile






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 '18 at 15:07









      GautithoGautitho

      465




      465
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Assuming you are using GNU Make...



          Use a pattern rule like:



          obj/%.o: %.c
          $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


          to tell make that an object file obj/<name>.o is to be compiled from a source file
          <name>.c



          In conjunction with this, use the VPATH special variable
          to inform make of directories in which it should look for any <name>.c, if it is not
          in the current directory.



          Also, add an order-only prerequisite
          to the pattern rule to ensure that the directory (obj) to which your object files are compiled
          exists when needed:



          obj/%.o: %.c | obj
          $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


          So for example, with project structure:



          ./
          -- Makefile
          -- aa/
          -- main.c
          -- bb/
          -- foo.c
          -- obj/ #<-- Compile object files in here
          -- prog #<- program to be built


          And:



          Makefile



          VPATH := aa:bb
          SRCS := foo.c main.c
          OBJS := $(addprefix obj/, $(SRCS:.c=.o))

          .PHONY: all clean

          all: prog

          prog: $(OBJS)
          $(CC) $(LDFLAGS) -o $@ $^ $(LDLIBS)

          obj/%.o: %.c | obj
          $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<

          obj:
          mkdir $@

          clean:
          $(RM) $(OBJS) prog


          the build runs like:



          $ make
          cc -c -o obj/foo.o bb/foo.c
          cc -c -o obj/main.o aa/main.c
          cc -o prog obj/foo.o obj/main.o





          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53483986%2fmakefile-parse-target-to-define-dependencies%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Assuming you are using GNU Make...



            Use a pattern rule like:



            obj/%.o: %.c
            $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


            to tell make that an object file obj/<name>.o is to be compiled from a source file
            <name>.c



            In conjunction with this, use the VPATH special variable
            to inform make of directories in which it should look for any <name>.c, if it is not
            in the current directory.



            Also, add an order-only prerequisite
            to the pattern rule to ensure that the directory (obj) to which your object files are compiled
            exists when needed:



            obj/%.o: %.c | obj
            $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


            So for example, with project structure:



            ./
            -- Makefile
            -- aa/
            -- main.c
            -- bb/
            -- foo.c
            -- obj/ #<-- Compile object files in here
            -- prog #<- program to be built


            And:



            Makefile



            VPATH := aa:bb
            SRCS := foo.c main.c
            OBJS := $(addprefix obj/, $(SRCS:.c=.o))

            .PHONY: all clean

            all: prog

            prog: $(OBJS)
            $(CC) $(LDFLAGS) -o $@ $^ $(LDLIBS)

            obj/%.o: %.c | obj
            $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<

            obj:
            mkdir $@

            clean:
            $(RM) $(OBJS) prog


            the build runs like:



            $ make
            cc -c -o obj/foo.o bb/foo.c
            cc -c -o obj/main.o aa/main.c
            cc -o prog obj/foo.o obj/main.o





            share|improve this answer




























              1














              Assuming you are using GNU Make...



              Use a pattern rule like:



              obj/%.o: %.c
              $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


              to tell make that an object file obj/<name>.o is to be compiled from a source file
              <name>.c



              In conjunction with this, use the VPATH special variable
              to inform make of directories in which it should look for any <name>.c, if it is not
              in the current directory.



              Also, add an order-only prerequisite
              to the pattern rule to ensure that the directory (obj) to which your object files are compiled
              exists when needed:



              obj/%.o: %.c | obj
              $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


              So for example, with project structure:



              ./
              -- Makefile
              -- aa/
              -- main.c
              -- bb/
              -- foo.c
              -- obj/ #<-- Compile object files in here
              -- prog #<- program to be built


              And:



              Makefile



              VPATH := aa:bb
              SRCS := foo.c main.c
              OBJS := $(addprefix obj/, $(SRCS:.c=.o))

              .PHONY: all clean

              all: prog

              prog: $(OBJS)
              $(CC) $(LDFLAGS) -o $@ $^ $(LDLIBS)

              obj/%.o: %.c | obj
              $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<

              obj:
              mkdir $@

              clean:
              $(RM) $(OBJS) prog


              the build runs like:



              $ make
              cc -c -o obj/foo.o bb/foo.c
              cc -c -o obj/main.o aa/main.c
              cc -o prog obj/foo.o obj/main.o





              share|improve this answer


























                1












                1








                1







                Assuming you are using GNU Make...



                Use a pattern rule like:



                obj/%.o: %.c
                $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


                to tell make that an object file obj/<name>.o is to be compiled from a source file
                <name>.c



                In conjunction with this, use the VPATH special variable
                to inform make of directories in which it should look for any <name>.c, if it is not
                in the current directory.



                Also, add an order-only prerequisite
                to the pattern rule to ensure that the directory (obj) to which your object files are compiled
                exists when needed:



                obj/%.o: %.c | obj
                $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


                So for example, with project structure:



                ./
                -- Makefile
                -- aa/
                -- main.c
                -- bb/
                -- foo.c
                -- obj/ #<-- Compile object files in here
                -- prog #<- program to be built


                And:



                Makefile



                VPATH := aa:bb
                SRCS := foo.c main.c
                OBJS := $(addprefix obj/, $(SRCS:.c=.o))

                .PHONY: all clean

                all: prog

                prog: $(OBJS)
                $(CC) $(LDFLAGS) -o $@ $^ $(LDLIBS)

                obj/%.o: %.c | obj
                $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<

                obj:
                mkdir $@

                clean:
                $(RM) $(OBJS) prog


                the build runs like:



                $ make
                cc -c -o obj/foo.o bb/foo.c
                cc -c -o obj/main.o aa/main.c
                cc -o prog obj/foo.o obj/main.o





                share|improve this answer













                Assuming you are using GNU Make...



                Use a pattern rule like:



                obj/%.o: %.c
                $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


                to tell make that an object file obj/<name>.o is to be compiled from a source file
                <name>.c



                In conjunction with this, use the VPATH special variable
                to inform make of directories in which it should look for any <name>.c, if it is not
                in the current directory.



                Also, add an order-only prerequisite
                to the pattern rule to ensure that the directory (obj) to which your object files are compiled
                exists when needed:



                obj/%.o: %.c | obj
                $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<


                So for example, with project structure:



                ./
                -- Makefile
                -- aa/
                -- main.c
                -- bb/
                -- foo.c
                -- obj/ #<-- Compile object files in here
                -- prog #<- program to be built


                And:



                Makefile



                VPATH := aa:bb
                SRCS := foo.c main.c
                OBJS := $(addprefix obj/, $(SRCS:.c=.o))

                .PHONY: all clean

                all: prog

                prog: $(OBJS)
                $(CC) $(LDFLAGS) -o $@ $^ $(LDLIBS)

                obj/%.o: %.c | obj
                $(CC) $(CPPFLAGS) $(CFLAGS) -c -o $@ $<

                obj:
                mkdir $@

                clean:
                $(RM) $(OBJS) prog


                the build runs like:



                $ make
                cc -c -o obj/foo.o bb/foo.c
                cc -c -o obj/main.o aa/main.c
                cc -o prog obj/foo.o obj/main.o






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 26 '18 at 15:52









                Mike KinghanMike Kinghan

                31.1k766115




                31.1k766115
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53483986%2fmakefile-parse-target-to-define-dependencies%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

                    Calculate evaluation metrics using cross_val_predict sklearn

                    Insert data from modal to MySQL (multiple modal on website)