Trying to use FamixPythonImporter I got a Tree sitter error

[FedeLoch]

This happens to me using any Pharo/Moose version

Steps to reproduce it:

1- Load MoosePy

Metacello new
  githubUser: 'moosetechnology' project: 'MoosePy' commitish: 'master' path: 'src';
  baseline: 'MoosePy';
  load.

2- I run FamixPythonImporter

FamixPythonImporter import: path asFileReference

3- I got

SymbolNotFoundError: Could not find symbol named: #ts_parser_new searching in module: '/Users/fede/Documents/Pharo/vms/120-x64/Pharo.app/Contents/MacOS/Plugins/libtree-sitter.dylib'

[alesshosry]

@FedeLoch
Hello, is this still an issue? I tried to reproduce the same on mac but it worked; And I checked the newer version of tree_sitter, it is always supporting ts_parser_new. Can you please elaborate more:

• what machine are you using ?
• did you check that the libraries are correctly added in the vms ?
• Can you use Pharo-tree-sitter in playground?

parser := TSParser new. 
language := TSLanguage python.
parser language: language.
string := 'some python code here'.
tree := parser parseString: string.
rootNode := tree rootNode. "do you get something when you inspect it? " 

• Perhaps the library was not generated correctly. what I recommend is to delete it and execute the tests again. The project is meant to clone the repos in your Documents and generate the libraries then to move them to the convienient vm folder (according to the version of Moose you're using).
• if it is still throwing the same issue, perhaps you can give it a try by generating the libraries manually (follow the documentation on the readme).

[alesshosry]

I think I’ve found a solution to the problem with the libraries generated on your machine.
In fact, I thin it is related to a difference in CPU architecture.

So, to check whether this is indeed the cause of the problem, here’s the procedure to follow :

• Close Pharo.
• In the terminal, type
  open /Users/yourusername/Documents/Pharo/vms/120-x64/Pharo.app/Contents/MacOS/Plugins
  to open Pharo’s VM plugins folder.
• Rename the old Tree-sitter XML library.
• Go to the folder Documents/tree-sitter-libraries/tree-sitter-xml.
• Open a terminal from the XML folder (right-click on the XML folder → open terminal in this folder).
• Run: make clean (this will remove the library already generated in that folder).
• Then run:
  make CFLAGS="-arch arm64 -O2 -fPIC" LDFLAGS="-arch arm64"
  (this should generate a library compatible with your machine, hopefully 😛).
• Copy the newly generated .dylib into Pharo’s VM plugins folder.
• Reopen Pharo and try again to see if it works.

Please try and if the problem is solved please let me know so I can then change the configuration in the Pharo-Tree-Sitter repository to make it generic and fix it.

[FedeLoch]

Oh sorry, I have not seen this message before! 🫠 .

Thanks! :) I will try, and I will let you know if that worked! :) .

[alesshosry]

Oh sorry, I have not seen this message before! 🫠 .

Thanks! :) I will try, and I will let you know if that worked! :) .

@FedeLoch did you try the solution?