Shane:
Thank you for the tip. Actually I am using Visual Source Safe as the
Source Management tool.
I was considering the use of CVS, but decided against at the last
moment because most of the fellow developers including me, had been
using VSS for a considerable amount of time, and felt that
Hi all,
I am writing a automated build script for my project that will be run
under cygwin. I will copy my updated source files to the build directory and if
there are updated files, the executables will be built. To copy the source
files, I had to use XCOPY since the directory structure
On Sun, 6 Aug 2006, Shane wrote:
Hi all,
Hi. http://cygwin.com/acronyms/#PCYMTWLL. Reading the one-line below
was extremely painful in the web archives. See for yourself:
http://cygwin.com/ml/cygwin/2006-08/msg00169.html.
I am writing a automated build script for my project that
On 8/6/06, Shane wrote:
Can you please provide me a way of checking the XCOPY exit code: reference
[http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/xcopy.mspx?mfr=true]
within Bash?
result codes are stored in $? in bash
success = 0 usually, and xcopy seems to
Igor Peshansky wrote:
Nope, you didn't have to. Something like
(cd $2/.. find $2 -name *.$1 | tar cfT - -) | tar xfC - $3
would do the job of XCOPY /S using POSIX means.
If you go POSIX, you can use the --keep-newer-files tar option.
Of course it didn't. Please read a good bash
Shane wrote:
I am writing a automated build script for my project that will be run
under cygwin. I will copy my updated source files to the build
directory and if there are updated files, the executables will be
built. To copy the source files, I had to use XCOPY since the
directory structure
David Christensen wrote:
There are standard software development tools that solve the problems
you are facing -- CVS and Make:
http://ximbiot.com/cvs/wiki/index.php?title=Main_Page
http://ximbiot.com/cvs/wiki/index.php?title=Main_Page
Both are included in Cygwin. In the long run,
On Mon, 7 Aug 2006, Shane wrote:
What I am trying to do is, checkout the source to the build directory
and if there are any local changes in my working directory copy them to
the build directory, build and do a test run from there. This is so that
I can test my code before I do the actual
On Sun, Aug 06, 2006 at 07:46:07AM -0800, Shane wrote:
I am writing a automated build script for my project that will be run
under cygwin. I will copy my updated source files to the build
directory and if there are updated files, the executables will be
built. To copy the source files, I had to
Igor Peshansky wrote:
As David said, cvs has an easy way of doing this (using cvs diff and
patch), which will also deal with local and checked in changes to the
same file (while your method won't).
Point taken. I will certainly look into it.
Did you happen to notice the mention of the
Christopher Faylor wrote:
Is there some reason why you are not using cp to accomplish your task?
cp --help should provide you with all sorts of options for copying files.
You should be able to press cp into service for this.
Using DOS utilities and DOS paths for this type of thing is putting
On Mon, Aug 07, 2006 at 06:52:40AM +0900, Shane wrote:
Christopher Faylor wrote:
Is there some reason why you are not using cp to accomplish your
task? cp --help should provide you with all sorts of options for
copying files. You should be able to press cp into service for this.
Using DOS
://lists.samba.org/archive/samba/1999-December/016328.html
and it's follow-ups.
Thanks and Regards
Shane
-Original Message-
From: [EMAIL PROTECTED]
Sent: Sun, 6 Aug 2006 21:04:27 -0400
To: cygwin@cygwin.com
Subject: Re: Checking XCOPY Exit Value in Cygwin Bash
On Mon, Aug 07, 2006
On Sun, Aug 06, 2006 at 08:26:11PM -0800, Shane wrote:
What's wrong with cp -a or cp -r?
It only copied files that were directly under the source directory. It
didn't traverse the directories inside source recursively. I did some
searching and, I came up with a similar thread. Finally the tar
14 matches
Mail list logo
