Build error under Linux about nativeshell

[dureuill]

Removing the symlink did the trick.

Not sure what to do with this issue then :-). Maybe the code should try to follow symlinks to resolve the path to flutter?

[knopp]

I think this should do the trick. I'll just need to test it on all platforms before publishing updated crate.

[knopp]

Hi,

this part seems suspicious:

Flutter artifact location path at "/bin/cache/artifacts/engine/linux-x64" does not exist! Try running 'flutter precache'

The path should not start with /bin. It should start with wherever "flutter" executable is. But if "flutter" is not in PATH, the error message you got should have been completely different (Please make sure that flutter is in PATH).

What does your PATH look like? I'm curous why flutter location in your case resolved in empty string.

[dureuill]

flutter is in PATH.

examples on  main [?] is 📦 v0.1.0 via 🎯 v2.14.0-188.0.dev via 🦀 v1.50.0
🔋🔽29% ❯ which flutter                                                                                                                 [22:37:21]
/bin/flutter

examples on  main [?] is 📦 v0.1.0 via 🎯 v2.14.0-188.0.dev via 🦀 v1.50.0
🔋🔽29% ❯ whereis flutter                                                                                                               [22:38:00]
flutter: /usr/bin/flutter /opt/flutter/bin/flutter /opt/flutter/bin/flutter.bat
examples on  main [?] is 📦 v0.1.0 via 🎯 v2.14.0-188.0.dev via 🦀 v1.50.0
🔋🔽29% ❯ ls /usr/bin/flutter -hl                                                                                                       [22:38:04]
lrwxrwxrwx 1 root root 24  7 juin  22:00 /usr/bin/flutter -> /opt/flutter/bin/flutter

It looks like flutter lives in /opt/flutter but has a symlink to /usr/bin/flutter.
I installed flutter from the AUR, it probably created that symlink.

The symlink doesn't look necessary because /opt/flutter/bin is in my PATH. I can try removing it, but I don't like removing files installed by packages.

Thanks for the quick answer.

[knopp]

I see where the problem is. I really didn't expect that there'd be symlink to wherever flutter is installed. Normally the way to install flutter is to add [flutter_root]/bin to PATH. Apparently that's not always the case.

I think the best way to fix this should be resolve flutter if it is symlink when searching for artifacts.

[dureuill]

Aha, I was looking at the code and just arrived at the same conclusion: adding canonicalize should do the trick.

I will test your fix and test and report if it works for me.

[dureuill]

After reinstating the symlink and checking that it still fails on the previous version, I can report that commit 10ea0de indeed fixes the problem :-).

Feel free to close this issue now or when the updated crate is published.

[knopp]

Thank you for confirming this. I published updated crate so I'm closing this issue.