# Create the plug-in directory, if it doesn't exist. Necessary because some of the build setting paths are relative. # Change the directory to the project root. # Allows us to see any script errors by running 'cat /tmp/xcode_build.log'. 📣 Important: Make sure you set the INSTALL_PATH build setting in step 3. 🤔 Why: This step will copy our built plug-in to the MacDown's plug-in directory. Provide the build settings from the plug-in's target, and paste the following script: Now reveal the Build action's sub-menu, select Post-actions, click the + in the lower left corner of the right panel, and add a New Run Script Action. 🔥 This will allow us to debug the plug-in using Xcode's Debugger. Hold ⌥ option + click on the scheme, select the Run action, and set the executable to your local MacDown.app (in the Executable pop-up button's menu, select Other.

🤔 Why: The ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES property ensures the required Swift standard libraries are embedded in our Swift plug-in, and we'll use the INSTALL_PATH in a post-action build script. Setting the INSTALL_PATH to $(USER_LIBRARY_DIR)/Application Support/MacDown/PlugIns/, which is where the MacDown plug-ins are located.Setting the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES to Yes.Next step is to modify the build settings, so go ahead and find your way there. 📌 Note: Make sure the Bundle Extension is set to plugin.

Go ahead and fill out the project options to your liking. So you want to create your own Swift MacDown plug-in? Let's jump right in.Ĭreate a new Xcode Project using the Bundle macOS template. 🔥 Looking for Objective-C? Check out macdown-gistit.

Macdown change default fill in