On Tue, Jul 28, 2009 at 11:13:09AM +0200, Bernd Machenschalk wrote:
> If we actually want to have a code segment, would it make sense to have
> some sort of plug-in concept (dlopen()) such that the projects don't
> have to hack the BOINC scheduler source code to get their app_plan()
> function into the scheduler?
Yep, I'm toying with that idea for some time now but I have no time
currently to implement it. This technique could also be used for the
validator and the assimilator as well.
The only blocker is the current state of shared library support. You
probably want to use libboinc & libsched functions from the plugin and
that can only be done sanely if those are compiled as shared libraries.
Currently there are a number of hacks in the code to force static
linking that should be removed. I've experimental Debian packages for
the BOINC server where the shared libraries work nicely, but the
packages did not receive much testing yet.
Also, having shared libraries means changes to the way a project is set
up; make_project can no longer just dump everything under the project
root and expect things to work. Instead, you need to do a "make install"
first that installs the shared libraries at a common location where the
run-time linker is configured to find them. And that can be taken even
further...
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
