@SGaist @aha_1980 Yeah, I thought of "low level" plugins anyway, as I don't want to extend Qt ifself, but a user application with my widget library. @SGaist said in Qt Widget Library vs. Qt Plugin advice: That said, if your goal is to provide a set of widgets for other to use in their application (such as the widgets module), then there's no need for plugins. Ok, I'll try a plain shared library and see how it goes :) Thank you both of you.

Libraries that are shared between plugins and executable shall be shared and not static. Otherwise you will end up with multiple definition of the static meta object of your QObject based classes which is not good.

Hi, With help of our senior Engineer. I am able to solve this issue. He change the binary path of libSquidStateLibrary.1.dylib into libChargeDischarge1.dylib and .app file. Inside the bundle my library location at _Squidstate.app/squidstatelibrary/libSquidStateLibrary.1.dylib //change Binary path in Plugin install_name_tool -change libSquidStateLibrary.1.dylib @executable_path/squidstatelibrary/libSquidStateLibrary.1.dylib ./../../out/Release/_SquidStat/_SquidStat.app/Contents/MacOS/prebuilt/libChargeDischarge1.dylib // change binary path in app install_name_tool -change libSquidStateLibrary.1.dylib @executable_path/squidstatelibrary/libSquidStateLibrary.1.dylib ./../../out/Release/_SquidStat/_SquidStat.app/Contents/MacOS/_SquidStat solution may be helpful to novice programmer like me. Thank you.

Great! Thanks for sharing your solution!