About lxqt-panel, I'd like to make building plugins outside the lxqt-panel source tree possible.Other libs already received the treatment and the result was generally good.I did not touch libqtxdg since it's more complicated.This not only make the file size smaller, it also speed up runtime dynamic linking and symbol name resolution and make loading faster.Take liblxqt for example, after using the gcc visibility trick, number of the exported symbols decreased by 50% (about 1000).With this, we can avoid exporting unnecessary dynamic symbols.Hello,I recently did some gcc visibility-related stuff to most of the libraries we have.
--Cheers!I haven't start doing this since áÌÅËÓÁÎÄÒ óÏËÏÌÏ× knows this much better than me, and also your comments and suggestions are needed.After these are done, we can develop plugins outside the lxqt-panel source tree. So other third parties can develop lxqt panel plugins as well. We can also develop some distro-specific panel plugins, such as libindicator plugin for ubuntu.2. BuildPlugin.cmake should be reworked and create LxQtPanel-config.cmake, which is installable.These requires several changes.1. lxqt-panel should be split into lxqt-panel and liblxqt-panel. All classes/functions used by the plugins should be in liblxqt-panel.
3. Install plugin API headers
About #1, making core plugin API its own library liblxqt-panel is needed. Though without this back-linking from the plugins to the executable still works, it's not portable.
You received this message because you are subscribed to the Google
Groups "Razor-qt" group.
For more options, visit this group at
You received this message because you are subscribed to the Google Groups "Razor-qt" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.