I have rebased the demo-plugin branch to the latest master Regards
Andreas On 02.10.2018 18:59, FORTMANN, TOM wrote: > Noel, > > Thank you for the quick response. This is exactly what I was looking for. > > Tom > > -----Original Message----- > From: Noel Kuntze <[email protected]> > Sent: Tuesday, October 2, 2018 11:38 AM > To: FORTMANN, TOM <[email protected]>; [email protected] > Subject: Re: [strongSwan-dev] Looking for direction on writing a custom > plugin. > > Hello Tom, > > Checkout the demo-plugin branch. It contains one additional commit, you can > see its contents here: > https://github.com/strongswan/strongswan/commit/648735c78ec7ca563b6ce52e65f54a44573973a7 > > For future migration, just keep a single diff or a set of diffs that you can > then apply on top of the checked out source code of the release you want to > build. > Regarding building just that plugin, you configure the source and then run > "make" in the plugin's directory. But you shouldn't do that because of > possible ABI changes between compiler versions, if you don't build it all in > one swoop. > > Kind regards > > Noel > > Am 02.10.18 um 18:26 schrieb FORTMANN, TOM: >> >> I’m looking for information on how to build a custom plugin. I can use the >> source from any of the provided plugins as a template, but I’m looking to >> guidance on how to integrate this in to the overall build process or >> building it outside of the strongswan build. Pros/cons. Also, tips on >> doing this in a way that simplifies migration to future strongswan updates >> would be very helpful. >> >> >> >> Thanks in advance for any and all help, >> >> Tom >> >> >> > -- ====================================================================== Andreas Steffen [email protected] strongSwan - the Open Source VPN Solution! www.strongswan.org Institute for Networked Solutions HSR University of Applied Sciences Rapperswil CH-8640 Rapperswil (Switzerland) ===========================================================[INS-HSR]==
