Paul McCullagh wrote: > Sorry, it had to be something stupid of course! :) > > plug.ini ==> plugin.ini
I'm mostly out today moving apartments ... but I'm going to try to think in the back of my head how to deal with your dir layout. Normally, you'd list the plugin source files in plugin.ini, and then if there's something more complex you need to add (like a libpbxt.la) you'd put that in plugin.am, which is included at the top level, so is written from that perspective. So the system will need some though in how to address your source layout... Monty > On May 15, 2009, at 4:04 PM, Paul McCullagh wrote: > >> I am just moving PBXT over to the new plugin directory and have a >> little problem. >> >> I do the following: >> >> rm -r autom4te.cache >> config/autorun.sh >> ./configure --help >> >> But PBXT is not listed as a plugin in the output. Expected would be >> something like this: >> >> --with-pbxt-plugin >> Build PBXT Storage Engine >> >> Neither are any Makefile.in's generated. >> >> My directory structure looks like this: >> >> plugin/pbxt >> plugin/pbxt/plug.ini > > > > -- > Paul McCullagh > PrimeBase Technologies > www.primebase.org > www.blobstreaming.org > pbxt.blogspot.com > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
