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

Cannot use with SwiftTreeSitter #294

Open
nutsmuggler opened this issue May 1, 2023 · 0 comments
Open

Cannot use with SwiftTreeSitter #294

nutsmuggler opened this issue May 1, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@nutsmuggler
Copy link

What happened?

I am developing a tree-sitter grammar for the ABC music notation.
I was initially focusing on providing syntax highlighting with Runestone, but now that I am familiar with tree-sitter I realized I can use its tree to generate an abstract representation of musical scores (which I can then convert into midi or other format).
Now I have two test projects: my proper ABC parser based on SwiftTreeSitter, and my highlighter based on Runestone.
As soon as I try to add the Runestone to my SwiftTreeSitter-based project I get an error:

196 duplicate symbols for architecture arm64

I believe this is because both packages import the tree-sitter C classes.
Am I missing something banal here or are the two packages incompatible?

I've read the other thread about the reasons for not exposing the tree-sitter tree from Runestone; I am just wondering if there is a practical way of using Runestone and the tree-sitter tree; well, apart from forking of course :)
Of course I realize 2 tree-sitter routines are kind of a duplicate, but I'd use them in different parts of my app, so I don't expect lags or anything.

BTW thanks for the great job Simon!

What are the steps to reproduce?

  • Create a project based on Runestone, like the one described in the tutorial
  • Add the SwiftTreeSitter package
  • Build

=> Error: 196 duplicate symbols for architecture arm64

What is the expected behavior?

I'd expect the project to build and allow me to use both packages independently.

@nutsmuggler nutsmuggler added the bug Something isn't working label May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants