Hello, I realized that is not easy to ship the auto-generated files of autogen. That is if I ship them and the user has a different version of libopts installed then he'll get something like:: In file included from ocpasswd.c:31:0: ./ocpasswd-args.h:61:3: error: #error option template version mismatches autoopts/options.h header # error option template version mismatches autoopts/options.h header
If I include the libopts in the package and force the program to use that and not the system one, then I have issues with people who have autogen and regenerate them. Both cases are kind of ugly, and the only viable alternative seem to be to not ship them at all and require autogen in the target system. This is of course is ugly for systems like *bsd that typically do not have a lot of gnu tools (and autogen requires guile etc). Is there any other cleaner solution to that, that I'm missing? regards, Nikos ------------------------------------------------------------------------------ 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
