Resolving the C Makefile Issue: Generating Multiple Output Files Made Easy

Описание: Learn how to modify your `C makefile` to produce multiple output files instead of just one. Simple fixes and explanations included for clarity!
---
This video is based on the question https://stackoverflow.com/q/65733697/ asked by the user 'Eli Zatlawy' ( https://stackoverflow.com/u/8978791/ ) and on the answer https://stackoverflow.com/a/65734071/ provided by the user 'ivan.ukr' ( https://stackoverflow.com/u/1540501/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: C makefile produce only 1 out file instead of 2

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Resolving the C Makefile Issue: Generating Multiple Output Files Made Easy

Introduction

If you've recently started using makefiles in your C projects, you've likely encountered some confusion about how they work. For example, you may have a scenario where you want to compile multiple source files but only end up with one output file. This can leave newcomers scratching their heads. In this guide, we will investigate a common issue faced by many: why only one output file is generated from a makefile and how to fix it.

The Problem: Only One Output File

Consider the following scenario: You have two source files, bar.c and foo.c, stored in the same directory along with a makefile that is supposed to compile them both. However, when you run the command make, the output is only the executable for foo, and bar does not get generated.

Here’s a look at the provided makefile:

[[See Video to Reveal this Text or Code Snippet]]

What’s Going Wrong?

The main issue lies in the way make processes the targets in the makefile. By default, make always starts from the first target it encounters unless instructed otherwise. In this case, the first target is foo, and thus only the foo target is completed, leaving the bar target untouched during a typical call to make.

The Solution: Organizing Your Makefile

The good news is that this behavior is easy to change. Here are two primary solutions to make your makefile produce both output files, foo and bar.

Solution 1: Move the all Target to the Top

To ensure that both foo and bar are compiled when you run make, you can simply move the all target to the top of your makefile. This way, you are explicitly stating which targets should be built by default.

Here’s how your modified makefile would look:

[[See Video to Reveal this Text or Code Snippet]]

Solution 2: Explicitly Specify the Target

If you prefer to keep the makefile as it is but want to still compile both files, you can directly specify the all target when you run the make command. Instead of just typing make, you would type:

[[See Video to Reveal this Text or Code Snippet]]

This command tells the make utility to execute the all target, which includes both foo and bar.

Conclusion

With just a few modifications, you can easily use your C makefile to produce multiple output files. Whether you decide to rearrange your targets or explicitly call the all target when you run make, you now have the knowledge to overcome this common issue. So, next time you face a similar situation, you can confidently adjust your makefile and compile all your necessary files without any hassle.

By following these practices, you'll not only simplify your own coding workflow but also enhance your understanding of how makefiles operate in the C programming environment. Happy coding!