Why load dynamic libraries instead of linking static libraries? #2403
Replies: 1 comment 19 replies
-
|
Looks reasonable! IIRC it is because (1) Flutter's default templates use dynamic loading (2) dynamic is more flexible (3) when using static linking you should be careful not to have conflicting symbols. But if you do not have these scenarios, then yes feel free to use static! |
Beta Was this translation helpful? Give feedback.
-
|
Can this be used in production? I tested it briefly and didn't seem to find any problems. |
Beta Was this translation helpful? Give feedback.
-
Did you test it on Windows? |
Beta Was this translation helpful? Give feedback.
-
|
Firstly make sure it is tested on a platform using static libraries. If it works in your thorough tests, then I guess it should be OK. But this is not officially supported (but feel free to PR to support it), so is not guaranteed to work forever. Instead, it would be great to combine your flutter packages that uses frb into a single one to avoid this. |
Beta Was this translation helpful? Give feedback.
-
Not before, I was on macos. But I tried today on windows, it failed to build. A temporary solution is to remove three lines in
No, I just use frb as a normal library. |
Beta Was this translation helpful? Give feedback.
-
??? I thought you had it static linking. |
Beta Was this translation helpful? Give feedback.
-
Linking static libraries can maximize the security of core logic in rust. When using a dynamic link library, others can deduce the logic of the call based on the parameters and order of the calling function.
In the output products on platforms windows and android, the figures of DLL and SO can be directly seen.
Is it because static linking is not possible on these platforms that dynamic linking is used?
Beta Was this translation helpful? Give feedback.
All reactions