Jim Hyslop wrote: > HAVE_GETCWD is used in lib\xgetcwd.c:
Are you looking in the most recent versions of the sources? I don't see it: [EMAIL PROTECTED] ~]$ cd work/ccvs-clean [EMAIL PROTECTED] ccvs-clean]$ cvs up [EMAIL PROTECTED] ccvs-clean]$ grep HAVE_GETCWD lib/*.[hc] [EMAIL PROTECTED] ccvs-clean]$ cat lib/CVS/Root [EMAIL PROTECTED]:/cvsroot/cvs [EMAIL PROTECTED] ccvs-clean]$ cd ../ccvs-1.11.x-clean [EMAIL PROTECTED] ccvs-1.11.x-clean]$ cvs up [EMAIL PROTECTED] ccvs-1.11.x-clean]$ grep HAVE_GETCWD lib/*.[hc] [EMAIL PROTECTED] ccvs-1.11.x-clean]$ cat lib/CVS/Root [EMAIL PROTECTED]:/cvsroot/cvs [EMAIL PROTECTED] ccvs-1.11.x-clean]$ >> Also, windows-NT/config.h.in and windows-NT/config.h are supposed to be >> autogenerated using the windows-NT/mkconfig.pl script, from ./config.h >> and windows-NT/config.h.in.in. I'm not sure if that still needs to be >> done on UNIX or if Conrad added MSVC targets in the build files for it. > > > I wasn't sure exactly how it got generated, so I made the changes > manually in all the files. I didn't see anything that built config.h. > > So, is the correct procedure to modify config.h.in.in and run > mkconfig.pl? I haven't seen any documentation that describes how to > regenerate windows-NT/config.h; I assumed it was manually maintained. I'm not sure we've really documented that outside the UNIX Makefiles, some emails, and comments at the start of the generated files but, yes, that is the correct procedure and, if you don't follow it, your changes can be overwritten without anyone noticing. There is one tricky bit, that you need the correct current working directory when the script is run so that the lines about "...this script was generated by mkconfig.pl..." don't end up making files look different despite no other differences, but with a little work this could probably be coded into the windows makefiles too. Regards, Derek -- Derek R. Price CVS Solutions Architect Ximbiot <http://ximbiot.com> v: +1 717.579.6168 f: +1 717.234.3125 <mailto:[EMAIL PROTECTED]> _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
