I'll take a look at moving some of that stuff into configure... The one thing I'm not sure about is the handling of CC, although I think I can fudge that for now, and worry about a cleaner way later.
Derek Atkins wrote: > > Derrick J Brashear <[EMAIL PROTECTED]> writes: > > > > But they're not tested for now, the information is hard-coded in to > > > MakefileProto. Seems to me it would be just as good, maybe better, to > > > hard-code it in configure.in. > > > > Probably, but I kept hoping someone would come up with a better way to > > solve the problem, and so never did the work. > > I think if all the information is in the configure script then we > would be one-step closer to auto-generating the information. I think > centralizing all the 'choices' into autoconf is step one. Then making > autoconf smarter is step two. ;) > > Changing something that is hard-coded in multiple places into > something that is hard-coded in one place is the first step. Then we > can work on fixing the hard-codings, one at a time. > > Even if I wanted to, I couldn't autogenerate the Makefile and param > file for Linux without doing it for all the other platforms, too. If > we centralize it first, then we can autogenerate on a per-platform > basis, piecemeal. :) > > > -D > > -derek > > -- > Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory > Member, MIT Student Information Processing Board (SIPB) > URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH > [EMAIL PROTECTED] PGP key available > _______________________________________________ > OpenAFS-devel mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel -- ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
