Hi David The issue you describe arises because the CDL library, on which the eCos host tools are based, uses Tcl to read/write files. Tcl uses its own line-ending translation layer and ignores the Cygwin filesystem mount mode (text or binary). This is one of the reasons why I always recommend the use of a filesystem mounted in text mode for eCos development on Microsoft Windows.
While it would certainly be possible to hack the eCos tools to workaround this issue, the correct location for a fix would be in the Tcl library. John Dallaway eCosCentric Limited -------- Original Message -------- Subject: Re: Re: eCos Configuration Tool experimental build for Vista Date: Thu, 4 Sep 2008 06:08:11 -0700 From: David Brennan <[EMAIL PROTECTED]> To: John Dallaway <[EMAIL PROTECTED]> CC: [email protected] Newsgroups: gmane.os.ecos.general References: <[EMAIL PROTECTED]> John, I don't know if this is the right time to bring this up. But it is a minor "windows" issue that we came across. We use subversion for our VCS system. When we configured it to use native line-endings (I don't remember the correct term for that in svn lingo), we found the ecosconfig spits out files with Windows line endings under windows/cygwin, even if cygwin is configured for unix line-endings. This caused cygwin's svn to think that our ecosconfig file changed every time we ran 'ecosconfig anything'. Our solution was to use a windows native svn client. One developer used TortiseSVN. I downloaded the windows command line version from tigris.org. Both of these used windows line endings for everything, so it matched ecosconfig. But it would be nice if ecosconfig would honor the cygwin setting, or maybe have a command line option for one or the other. Or if there is an existing file, keep the line endings the same. David -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
