I'm trying to install Anaconda on my Windows 7 machine. I often use cygwin to for my command-line work, and I would like to manage Anaconda from there. I've worked through the graphic installer without any issues, and checked necessary boxes to reset my default path to this install of python. I go ahead to check where python is and initially I get this...
Regarding your path issue, see Installing anaconda to use with windows on how to fix that. Alternatively, you can just run /cygdrive/c/Anaconda/python.exe to start the Anaconda/windows python and leave the standard python pointing to the cygwin version.
Note that few of the suggestions given on the internet also include the necessary change to PYTHONPATH: if you use the anaconda/windows python, you also want the anaconda python libraries. Binary modules like numpy will surely crash or misbehave if you mix things up. The easiest way to check this is to install a module in cygwin that you do not need in Conda and test whether you can import that from anaconda python. If you can, your path is wrong.
However, this is also a terminal issue: Anaconda (Windows) python expects a windows shell and a modern cygwin shell is like an xterm, so very different. Diagnose this by running python --help, if that works but plain python hangs, the interactive prompt is the problem. This means you can run python programs, you just cannot interact with them.
A way around this is to use the cygwin bash shell instead of the cygwin terminal (both are under Cygwin group in the Start menu). They look very similar, but the font in the bash shell is less pretty and you cannot make the window wider than 80 chars (like all other CMD windows, never understood that 'feature'). This is cygwin bash running inside a CMD window, and your anaconda python will be interactive. The cygwin terminal gives you a bash shell running in a putty derivative, which mimics an xterm and cannot be used by anaconda python.
Old question, but for others that google and got here: Official setup has command line arguments which allowed me to prepare simple *.bat script - just put following line in e.g. "install-pkg.bat" and put that file into your root directory (e.g. C:\cygwin):
There is a chicken egg problem with the accepted answer. If you didn't get wget or lynx during the initial install, you cannot use apt-cyg. Here is how I installed wget so that I could use apt-cyg. (It uses the CLI features of the cygwin setup exe.)
Other answers are missing the dependencies you need before you can run the lynx installer within Cygwin. Run this from a privileged powershell or equivalent (your setup executable should be somewhere like Downloads\ or C:\tools\cygwin):
For at least packages that do not require post-install configuration, I have simply untarred them from the cygwin root '/'. I required an older version of subversion (1.7.14) which had passed beyond the two versions handled by setup.
An additional advantage is the package becomes outside the cygwin package management world and thus in a kind of adhoc blacklist is not automatically updated with the newest package if defaults are kept.
Basically we call cygwin_create_path from cygwin1.dll to perform the path conversion. That function allocates a memory buffer (using malloc) containing the converted path. So then we need to use free from cygwin1.dll to release the buffer it allocated.
Cygwin/X is licensed under a MIT/X11 style license. Cygwin is licensed under a modified GNU General Public License that specifically allows libcygwin.a to be linked to programs that are licensed under an Open Source Definition compliant license without such linking requiring that those Open Source programs be licensed under the GNU General Public License (see the Cygwin licensing page for more information). Source code and binaries for both projects are freely available.
For all Cygwin/X related questions and observations, please check the resources available at this site, such as the FAQ, the User's Guide and the mailing list archives. If you've exhausted these resources then please read the Cygwin problem reporting guidelines before sending an email to the cygwin mailing list.
I'm trying cygwin with emacs.My environment is Windows 7 x64, emacs-24.0.93.1, cygwin 2.769, system encoding is gbk, cygwin's coding system is default to utf-8, and emacs's coding system is default to gbk
During the cygwin setup process, make sure to choose the emacs packages - I picked "regular" emacs, emacs-x11, and emacs-w32 (native compiled for windows). The emacs-w32 looks/feels just like the regular Windows emacs binary as far as I can tell.
In order for an application to be able to use ANSI escape sequences when launched from cmd.exe (TERM=cygwin), either the application itself needs to be linked with cygwin1.dll, or its output needs to be filtered through another one which is (e. g.: mc or ssh subshells).
An alternative solution is using ConEmu as the external output filter (bash.exe running as a direct child of ConEmu.exe). This approach doesn't require linking with cygwin1.dll, as output filtering is performed by ConEmu itself. The downside is that ConEmu's support for escape sequences is limited (particularly, it doesn't understand the VT100 alternate character set used for line drawing).
I am running cygwin on Windows7 to execute my unix shell commands and I need to automate the process by writing a Java app. I already know how to use the windows shell through Java using the 'Process class' and Runtime.getRuntime().exec("cmd /c dir"). I need to be able to do the same with unix commands: i.e.: ls -la and so forth. What should I look into?
You do not need cygwin here. There are several pure Java libraries implementing SSH protocol. Use them. BTW they will solve your second problem. You will open session and execute command withing the same session, so the shell state will be preserved automatically.
I am running Windows 10 on my Surface Pro 3. I installed Cygwin and also added some useful packages (gvim, nedit, emacs, vim, g++). However, when I run gvim, I get "Can't open display". The same thing happens with nedit. When I did echo $DISPLAY, I showed nothing so I set the DISPLAY to :0.0. I still get "can't open display." I tried removing cygwin and re-installing but I get the same problem.
I know for my class, I had to install cygwin to get my Netbeans IDE running, but I see options during setup for both g++ and gcc and I am not sure if they are the same thing or not, and where does wingw? is it another compiler, and if so why choose on over the other?
So if you put cygwin1.dll in c:\ocaml-stuff, then /tmp corresponds to c:\ocaml-stuff\..\tmp, i.e., c:\tmp. An easy way to understand this is: in Cygwin, cygwin1.dll expects to live in /bin, so /tmp corresponds to a sibling subdirectory. So one option is to create this tmp directory: your OCaml executable will happily use that.
I am attempting to install root on my windows 10 laptop. Unfortunately the laptop does not support virtual machines so I will have to use cygwin. I found this guide on how to install root with cygwin.
Could y'all update the wiki to include a Windows 10 instead of Windows XP graphic? I've got cygwin installed and have placed the cdo.exe file in my windows/system32 folder and still can't get CDO to install per the instructions.
When I try ldd ./cdo.exe I get the output as shown in the attached. What I notice is that the linked cygwin paths are all in /usr/bin/, but in my cygwin install there is no such directory. Instead my cygwin installation has all the linked dlls in /bin. Could this be an issue?
I will check thw binary again on my windows box. could be that thw cygwin installation on the huilding machine needs an update. in general it dosnt matter where the dll are, but not getting any output is weird.
At the heart of the Cygwin collection of tools is the cygwin1.dll dynamic link library (DLL). The DLL serves as an emulation layer that provides Portable OS Interface, or POSIX, system call functionality. The Cygwin distribution also has a large collection of free tools, including most GNU and many Berkeley Software Distribution tools, along with an X server and a full set of X applications.
For those who want to start syncthing as a service under windows (7) using the cygwin environment here is a bash script that expects the syncthing exe under for personal directory/binStart it using the cygwin bash shell and it stays silently in the background and logs in files.
Cygwin is essentially a utility that offers a Linux-like environment on a Microsoft Windows host. Technically, it is a DLL (cygwin1.dll) that acts as a Linux API layer providing substantial Linux API functionality. Once you install Cygwin, you can configure the SSH Daemon on the host. The Add Host Targets Wizard is certified and supported with Cygwin 2.4.1 or higher.
why not use the windows ones (.exe)? .rpm is the redhat installer extension (kinda like .msi for windows) you will need to install something into cygwin that can read it. have you installed the latest python?
I have many scripts written for linux envirionment. To make them work smoothly on my laptop, cygwin is a good choice. The windows version of BLAST does not work well with cygwin, because it cannot interpret the linux-style path. I have installed python 2.6.7. Not the latest for python, but the latest under Cygwin. If the rpm version can work under cygwin after installing something necessary, that is a good news. I am trying to build a local platform similar to linux, taking the advantage of both linux and windows.
In the course of writing automation scripts for use under DSS, I had the need to execute a bash shell script from within my javascript code. I went nuts trying to find something on the web that would do this, but only found a few examples that were not completely what I wanted. The following javascript function is intended to run under the rhino javascript interpreter that is used with DSS. It is expecting to be invoked from a Windows environment that is running cygwin. It takes a single character string that is a command to be executed as though it were typed into a bash shell command prompt. It returns as the function's value a character string that contains the text written to the shell's stdout stream. The shell's exit code is made available in the global variable bash_exit_code. So here is the function:
760c119bf3