In a world where build automation is a mystical art, one brave warrior dares to conquer the realm of “RULES.mk” config files with Visual Studio Code and IBM i. Join us on this thrilling adventure!

Step 1: Prepare for Battle (Install the Necessary Extensions)

Gather your trusty steed (Visual Studio Code) and equip it with the following extensions:

• Code for IBM i – Powerful VSCode Extension (because who doesn’t love a good acronym?)
• IBM i Source Orbit – Source Management System (It’s not flat you know – it’s orbitting)
• Git – Distributed Version Control System (dirty git)
• BOB – Better Object Builder for IBM i (You know this is the little yellow animated Bob)
• Project Explorer – Navigating Files and Folders (Come sail the seven seas of software development)

Step 2: Unleash the Power of “RULES.mk” (Create a New File)

Create a new file named “RULES.mk” (yes, it’s case-sensitive, so don’t even think about trying “rules.mk” – the build gods will not be pleased). This file will hold the secrets of your build automation.

Step 3: Conjure the Magic (Configure Your “RULES.mk” File)

Using the ancient wisdom from my Visual Studio Code for IBM i Course (https://www.nicklitten.com/course/autogenerate-rules-mk/), configure your “RULES.mk” file.

Step 4: Vanquish the Build (Run Your Makefile)

With your “RULES.mk” file and Visual Studio Code settings in place, run your Makefile using the “Make: Build” command (or press Ctrl+Shift+B for the keyboard warriors).

Watch in awe as your IBM i code is compiled, linked, and assembled into a majestic executable.

Epilogue: The Hero’s Reward

Congratulations, brave warrior!

You have conquered the realm of “RULES.mk” config files with Visual Studio Code and IBM i.

Your build automation skills are now legendary, and your code is compiled, linked, and assembled with ease.

Go forth and build greatness!