From: Jack U. <jd...@gm...> - 2007-11-13 05:36:34
|
On Nov 12, 2007 9:45 PM, Elliott Slaughter <ell...@gm...> wrote: > On Nov 12, 2007 8:13 PM, Jack Unrue <jd...@gm...> wrote: > > I'd like some feedback on the src/makemake.in patch below, > > which adds a new target called 'nsis' to invoke the Windows > > installer script. > > Thanks for your work on the patch. > > If I want to test the build, how do I go about doing it? Just > download the newest cvs, patch makemake.in and compile using > mingw and msys? After you apply my patch to src/makemake.in, you need to make an additional edit where makensis is invoked, such that you include the full path to that executable. This issue is what I was referring to when I mentioned needing to create a patch against configure to allow users to specify where NSIS lives. Here is the configure command-line that I'm using: CFLAGS="-O2" ./configure --with-mingw --build build --with-libsigsegv-prefix=/usr/local --with-module=bindings/win32 --with-module=dirkey --with-module=rawsock --with-module=wildcard --with-module=libsvm > Also, I want to upload some changes to the install scripts > ("%NAME%" and "%VERSION%" tags that need to be > replaced by the correct strings by make, and a script for > converting the COPYRIGHT file to rtf before building > install.nsi). I'm completely new to cvs, and I haven't had > much time to read up on its documentation, so I'm not > sure how to do that... (I have cvs on Ubuntu as well as > tortoise cvs on Windows. But I am not completely sure > what commands I need to use to upload the > files, and what to do about the change log.) I use CVS from the command-line, so with that in mind and assuming you already did a checkout using the developer CVSROOT (see http://sourceforge.net/cvs/?group_id=1355 for more info), then use the 'cvs commit' command. You'll also find the 'cvs diff' command useful. And 'cvs update' to get the latest from the repository; also 'cvs -nq update' to find out what files have local changes or conflicts. A CVS manual is available here: http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs.html BTW, it's a good practice to explicitly list the files that you want to check in, to avoid accidentally committing in-progress or experimental work. -- Jack Unrue |