Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make swift fails because of old swift tools version #170

Open
nickasd opened this issue Jul 29, 2019 · 9 comments
Open

make swift fails because of old swift tools version #170

nickasd opened this issue Jul 29, 2019 · 9 comments

Comments

@nickasd
Copy link
Contributor

nickasd commented Jul 29, 2019

Running make swift causes this error:

package at 'MultiMarkdown-6' is using Swift tools version 3.1.0 which is no longer supported; use 4.0.0 or newer instead

I couldn't find where this version number would have to be replaced.

@fletcher
Copy link
Owner

No idea. I don't use Swift -- that was done a couple of years ago to demonstrate that MMD could be used with Swift (it can), but I haven't used it since.

@nickasd
Copy link
Contributor Author

nickasd commented Jul 29, 2019

It looks like the Package.swift file is outdated, so I'm trying to bring it up to date. There is a libMultiMarkdown dependency: do you recall where that dependency was supposed to be or how it should be built?

@fletcher
Copy link
Owner

mmd-swift is basically an empty wrapper around libMultiMarkdown, with the main.swift demo file thrown in.

@nickasd
Copy link
Contributor Author

nickasd commented Jul 29, 2019

Ok, but it seems that the libMultiMarkdown should already be built before running the command make swift, because it complains that the dependency cannot be found. That’s why I asked where the dependency is supposed to be built, so that I could update the path if necessary. Or do you think that it should be handled by make swift as well?

@fletcher
Copy link
Owner

swift build, or the package manager, or whatever is supposed to take care of that as part of the build process. But like I said, that was a few years ago.

@nickasd
Copy link
Contributor Author

nickasd commented Jul 29, 2019

Do you know if the only difference between the Objective-C and the Swift versions is the Xcode project? Because I'm thinking that since C can be embedded in Objective-C code but not in Swift unless you use a bridging header, probably it wouldn't be worth it trying to make the build work for Swift. Maybe it would just be enough to set up the right bridging header?

@fletcher
Copy link
Owner

That's what this did -- MMD-6 has always been written in C (and presumably always will be until something better comes along). The make swift functionality built libMMD and packaged it to be compatible with swift projects. It worked (as demonstrated by the trivial test project), but based on your comments, it would seem that Apple has broken backwards compatibility with build workflows....

@nickasd
Copy link
Contributor Author

nickasd commented Aug 5, 2019

It worked (as demonstrated by the trivial test project)

This sounds as if there was a working (compiled) sample project to confirm this hypothesis, but I think that's not what you mean, right?

@fletcher
Copy link
Owner

fletcher commented Aug 6, 2019

make swift created a command line utility that would convert a simplistic MMD text string into HTML. It did not have logic to handle command line options or to read files, but there was no reason to reinvent that. It was proof that libMultiMarkdown worked properly in a swift program to handle processing of text into HTML (or LaTeX or whatever)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants