Hello, could you provide a guide on how to organize the project structure for third-party plugin development? I've noticed that current compilation requires the already built bind9's config.h file, but this file doesn't exist in a brand new project. Does this mean it doesn't allow external compilation of the source code?
Looking forward to your reply. * Colin Vidal <[email protected]> [2025-11-21 :14:06]: > On Fri, 2025-11-21 at 23:29 +0800, Chunhui Ouyang wrote: > > Could you tell me what the entry point of the plugin is? > > > > As explained in the reference for plugin development I sent you > earlier: > > "At various locations within the named source code, there are "hook > points" at which a plugin may register itself. When a hook point is > reached while named is running, it is checked to see whether any > plugins have registered themselves there; if so, the associated "hook > action" - a function within the plugin library - is called." > > So there is no really a single "entry" point, but rather multiples ones > depending where the plugin is hooked. (Plus the four `plugin_*` API to > implement for registering, etc.) > > Side note: please answer emails with the mailing list in CC, so > everyone can see, benefit and contribute to this thread. > > Thanks > > Colin Vidal >
signature.asc
Description: PGP signature
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.
