Can module be loaded through static library?

[x850044053wwt]

RT

[JackLau1222]

There is an important feature of BMF is dynamic module loading, which is convenient for some scenarios like elastic deployment. However, you can still try to use static library loading. You may encounter some problems. You can try to change some SDK codes. I recommend you to take a look at the relevant code of module_manager.cpp

[x850044053wwt]

There is an important feature of BMF is dynamic module loading, which is convenient for some scenarios like elastic deployment. However, you can still try to use static library loading. You may encounter some problems. You can try to change some SDK codes. I recommend you to take a look at the relevant code of module_manager.cpp

Modifying the compilation option BUILD_SHARED_LIBS=OFF does not completely generate a static library，only libfmt.a libbenchmark.a and some static lib

[x850044053wwt]

maybe Only support static build for IOS platform

[JackLau1222]

BMF doesn’t officially support static library build. You need to modify the CMake script. Sent from my iPhone

…

------------------ Original ------------------ From: x850044053wwt ***@***.***> Date: Tue, Nov 26, 2024 7:55 PM To: BabitMF/bmf ***@***.***> Cc: Jack Lau ***@***.***>, Comment ***@***.***> Subject: Re: [BabitMF/bmf] Can module be loaded through static library? (Issue#153) There is an important feature of BMF is dynamic module loading, which is convenient for some scenarios like elastic deployment. However, you can still try to use static library loading. You may encounter some problems. You can try to change some SDK codes. I recommend you to take a look at the relevant code of module_manager.cpp Modifying the compilation option BUILD_SHARED_LIBS=OFF does not completely generate a static library，only libfmt.a libbenchmark.a and some static lib — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[ruiqurm]

There is an important feature of BMF is dynamic module loading, which is convenient for some scenarios like elastic deployment. However, you can still try to use static library loading. You may encounter some problems. You can try to change some SDK codes. I recommend you to take a look at the relevant code of module_manager.cpp

Modifying the compilation option BUILD_SHARED_LIBS=OFF does not completely generate a static library，only libfmt.a libbenchmark.a and some static lib

I tried to build the bmf staticly for the wasm construction, FYI PR 130. It does not support staticlly linking python and some gpu related feature and still used some dynamic linking due to symbol duplication at runtime when fully static linking.
And as Jack mentioned, one of the feature of bmf is it allows user to load module dynamically. You might not want a real fully static linking bmf. So can you share the reason why you need static linking?