Hi Chris, Yes. It would be better to your plugin under plugins directory. I think, this is how the openhpi is organized.
Regards, PG >-----Original Message----- >From: Chris Friesen [mailto:[email protected]] >Sent: Friday, August 28, 2009 4:32 AM >To: [email protected] >Subject: [Openhpi-devel] question on developing new plugins > >Hi all, > >Just a quick question, please cc me since I'm not subscribed. > >When developing new plugins it seems like some of the header files >needed (oh_handler.h, oh_domain.h, oh_error.h) are not exported by >Makefile.am. > >Is the expectation that new plugins are developed directly in the >plugins directory of openhpi itself so that these header files are >available? > >Thanks, > >Chris > >--------------------------------------------------------------- >--------------- >Let Crystal Reports handle the reporting - Free Crystal >Reports 2008 30-Day >trial. Simplify your report design, integration and deployment >- and focus on >what you do best, core application coding. Discover what's new with >Crystal Reports now. http://p.sf.net/sfu/bobj-july >_______________________________________________ >Openhpi-devel mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/openhpi-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
