[ci] Change soname of _experimental.so

[JSUYA]

Force changing SONAME because experimental so can not loaded in C++ host application.
#110 (comment)

[swift-kim]

Can we dynamically load libvulkan at runtime (e.g. volk)? I believe you have already considered this approach but wanted to ask anyway. Please ignore if it's too hard to explain.

[JSUYA]

Oh, I hadn't thought about dynamically loading libvulkan. Since the vulkan support PR has already been merged, i think, there's no need to apply this right now, but it seems like it could be improved using this method. Thanks for your information.

[JSUYA]

+)
We'll review this comment here. If you have any suggestions, please leave them.
#128

[xiaowei-guan]

@JSUYA Hello, I have a query, :
how to load _experimental.so if we run command 'flutter-tizen run --dart-define=USE_FLUTTER_TIZEN_EXPERIMENTAL'?
I originally thought it would link _experimental.so when the USE_FLUTTER_TIZEN_EXPERIMENTAL parameter was added.

[JSUYA]

how to load _experimental.so if we run command 'flutter-tizen run --dart-define=USE_FLUTTER_TIZEN_EXPERIMENTAL'?
I originally thought it would link _experimental.so when the USE_FLUTTER_TIZEN_EXPERIMENTAL parameter was added.

Hi @xiaowei-guan
The work of downloading experimental so and including it with app compile and packaging it together should be done in flutter-tizen. flutter-tizen/flutter-tizen#684

[xiaowei-guan]

how to load _experimental.so if we run command 'flutter-tizen run --dart-define=USE_FLUTTER_TIZEN_EXPERIMENTAL'?
I originally thought it would link _experimental.so when the USE_FLUTTER_TIZEN_EXPERIMENTAL parameter was added.

Hi @xiaowei-guan The work of downloading experimental so and including it with app compile and packaging it together should be done in flutter-tizen. flutter-tizen/flutter-tizen#684

Hi,@JSUYA
Yes, flutter-tizen will downloading common so and experimental so.
And I think if we execute 'flutter-tizen run', we will link libflutter_tizen_common.so. If we execute ‘flutter-tizen run --dart-define=USE_FLUTTER_TIZEN_EXPERIMENTAL’, we will link libflutter_tizen_common_experimental.so. I'm not sure if my understanding matches what you're thinking.If the ideas are consistent, I don't think it's necessary to modify the library name using the patchelf command.

And Previously, we encountered errors when running C++ host because using simple file renaming commands (such as mv) only changed the file name in the file system, but the internal SONAME of the library file remained the old name. The application would then fail because it couldn't find a library with the correct name. Therefore, we used patchelf to modify the SONAME.

[JSUYA]

Yes, that's correct. As per your review, patchelf doesn't seem to be needed. I've created a flutter-tizen PR that uses experimental.so. Please review it. flutter-tizen/flutter-tizen#686