Closed danielpunkass closed 9 years ago
I'm working on what will either be MMD 4.8 or MMD 5.0, and am migrating to cmake, which leads to a different way of building the xcode project.
I'm not sure of the proper way to do this in a cmake->Xcode workflow.
Hi Fletcher - if you're working on a new build mechanism maybe it's best to close this for now and after you've switched over if I'm inspired/motivated to submit similar request, I will do so then.
MMD-5 is now public:
https://github.com/fletcher/MultiMarkdown-5
Not sure if you're familiar with CMake or not, but I'm happy to help sort through what needs to change for MMD-5 to support what you want. Ideally, this would consist of upgrading the CMakeLists.txt
file, so that whenever an XCode project is generated, it includes the proper settings.
BTW -- I'm now in the process of upgrading MultiMarkdown Composer to use MMD-5 (which is a process, since I use a heavily customized version of v4). But I am sure I will learn a few things about incorporating CMake builds in XCode projects.
Thanks, good to know about MultiMarkdown-5 being released! I will let you know when I get around to switching to it whether I have similar contribution to make.
The MMD source in v5 is that of 4.7.1 plus a few improvements, memory fixes, etc. It tests well.
What needs more inspection is the build process, and for you especially the XCode project that CMake will create. I think this will require a bit of extra work now, but should make other changes easier in the future.... I hope!
Hi Fletcher - the gist of this request is to add support for easily importing MultiMarkdown's header from a project that depends upon MultiMarkdown. I don't know if you have another solution you already prefer, but this one seems pretty canonical and makes it easy for projects to add the resulting headers from the static library target as they see fit.