You may also need to install Xcode’s command line tools with the following command:
Note: Due to multiple upstream bugs, Xcode may fail to build certain dependencies if you use the CocoaPods with versions lower than 0.39. Please upgrade CocoaPods, or use Bundler to execute a local version (as suggested above) instead.
An appropriate SDK should be bundled with Xcode 5 or later versions.
After cloning the repository, run the following commands inside the repository root (directory containing this README.mdfile):
and open MacDown.xcworkspace in Xcode. The first command initialises the dependency submodule(s) used in MacDown; the second one installs dependencies managed by CocoaPods.
Refer to the official guides of Git and CocoaPods if you need more instructions. If you run into build issues later on, try running the following commands to update dependencies:
git submodule update
bundle exec pod install
Join our Gitter channel if you have any problems with MacDown. Any suggestions are welcomed, too!
You can also file an issue directly on GitHub if you prefer so. But please, search first to make sure no-one has reported the same issue already before opening one yourself. MacDown does not update in your computer
immediately when we make changes, so something you experienced might be known, or even fixed in the development version.
MacDown depends a lot on other open source projects, such as Hoedown for Markdown-to-HTML rendering, Prism for syntax highlighting (in code blocks), and PEG Markdown Highlight for editor highlighting. If you find problems when using those particular features, you can also consider reporting them directly to upstream projects as well as to MacDown’s issue tracker. I will do what I can if you report it here, but sometimes it can be more beneficial to interact with them directly.