Mail Archives: cygwin/2005/10/26/05:57:06
On Oct 26 11:40, J?rg Schaible wrote:
> My solution was to build ssh as Windows console app:
> [...]
> +sshw$(EXEEXT): $(LIBCOMPAT) libssh.a $(SSHOBJS)
> + $(LD) -mwindows -o $@ $(SSHOBJS) $(LDFLAGS) -lssh -lopenbsd-compat $(LIBS)
> +
> [...]
> Two questions:
>
> 1/ Corinna, could you provide this version with next OpenSSH releases, too? Setting the appropriate property in the Subversion config to this sshw.exe, makes the SVN Clients in the Windows worlds happy. Neither Subclipse nor RapidSVN show these steadily popping up console windows anymore, nor does the command line version of Subversion behave differently.
Sorry, no. It's nothing I'm willing to support.
> 2/ If linking a normal console app as Windows console app does not behave differently, why is it not the default? What's the real difference for Cygwin? It is still a Cygwin app and is normally listed in the Cygwin processes. I cannot say too much about the pipe and forking stuff, but something like "tar cf - *.sh | sshw spk1 tar xf -" works just normal.
Just open a console window and call "ssh". What you see is the help
text. Now try the same with "sshw". What do you see? The difference
is that the sshw process doesn't connect to the console. That's nothing
I'd want in the Cygwin distro.
It seems easy enough to build ssh this way if that's what you need.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -