On 11/08/13 06:10, Nikos Mavrogiannopoulos wrote: > After having it implemented, it looks quite ugly (because files are > removed from the distributed tarball and cannot be easily revived). Is > there a reason why autogen generated files cannot run with an > arbitrary libopts? I mean does the API of libopts change that often? > If not it may be a good idea to require regeneration of the files only > libopts API is different from the API used by autogen. Currently the > #error condition is on every difference in major or minor release > between libopts and autogen, and this is what causes the > inconvenience.
Hmmm. OK. I'll pull your sources and if you'd send me your fiddlings (patch), I'll look into what makes sense. I'll try to do something reasonable with your code, but fix my own and re-release if necessary. Thanks for your help! Regards, Bruce ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Autogen-users mailing list Autogen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/autogen-users
