Cygwin: Difference between revisions

From wikinotes
No edit summary
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
Cygwin is a fully separate (and native) unix system that can run within windows.  
Cygwin provides a unix-like environment to run processes under windows by translating unix syscalls.<br>
Cygwin emulates tools that are exclusive to linux (fork, mmap, ioctl, ...) by passing
It has no CLI package manager, but the installer can be scripted to install packages.
those calls to the cygwin.dll library.  


It's beautiful, you can even run an Xserver and have it integrate with your windows' windows.
= Notes =
You can also run a full linux desktop within your Xwindow (although it is much faster to just use a terminal).
 
Cygwin comes without a CLI package manager, but packages can still be installed automatically using the cygwin installer's commandline arguments.
 
= Install =
<blockquote>
<blockquote>
'''chocolatey installs cygwin to C:\programdata\chocolatey\cygwin\tools\cygwin'''
{|
 
| [[cygwin install]]
Cygwin is built to be able to be run in a portable way. You install, update, and get new packages by
re-running the cygwin installer.
 
Always install the 32 bit version of cygwin, unless you absolutely need it to be 64bit. It is much
more supported. Cygwin doesn't seem to require any registry keys to be set, the only things that
affect it's portability are some environment variables.
 
'''NOTE''' If you are using my package-setup script, always run it with a normal
cygwin http-repo as a source, reboot, then run with the private key for a cygports repo.
If you fail to do this, and run the cygports repo first, you may end up with corrupted packages.
</blockquote><!-- Install -->
 
= Package Management =
<blockquote>
{| class="wikitable"
!colspan=3| Best Sources
|-
|-
| http://lug.mtu.edu || || standard cygwin packages
| [[cygwin package management]]
|-
|-
| http://mirrors.kernel.org/sources.redhat.com/cygwinports/  || || precompiled cygports (https://sourceware.org/cygwinports/)
| [[cygwin configuration]]
|}
 
<syntaxhighlight lang="bash">
## Start Cygwin with GPG key for cygports
/path/to/setup-x86.exe -K http://cygwinports.org/ports.gpg
</syntaxhighlight>
 
 
''' CYGPORTS CONTAINS DWM, MPD, NCMPC, PYSIDE '''<br>
Cygwin doesn't have a traditional package manager. There are a few terminal programs you
can use to emulate apt-get, but since on Windows files cannot be deleted or overwritten while they
are running it is best to quit cygwin, and install programs using the installer.
 
Because of cygwin's limited options in the default repo, I find myself compiling packages myself
quite a lot. I created a git repo for compiled (and attempts at compiling) programs for quick (manual)
installations on new machines.
 
There is also a system loosely based on Gentoo's portage to assist in compilation. It is called cygports,
and can be installed from the main package manager.
 
<br>
<br>
 
</blockquote><!-- Package Management -->
 
= Common Problems =
<blockquote>
== rebase ==
<blockquote>
Almost all issues related to cygwin can be resolved by rebasing. You can do it
the quick/dirty way:
 
<syntaxhighlight lang="bash">
C:/cygwin/bin/dash.exe
/bin/rebaseall
 
</syntaxhighlight>
 
Or the full proper way:
<syntaxhighlight lang="bash">
 
- Open Task Manager and close any processes that look to be Cygwin related.
- Open C:\Cygwin\bin in Windows Explorer
  - Verify that dash.exe, ash.exe, rebase.exe, and rebaseall exist in this folder
      - If any of them are missing, re-run Cygwin setup and select the dash, ash, and rebase packages
 
    - right-click your C:\Cygwin folder, uncheck Read-only (if its checked), and press OK.
      - When an error about not being able to switch some files comes up, select "Ignore All". Wait for this process to complete.
 
    - Browse to C:\Cygwin\bin in Windows Explorer
    - Right click dash.exe and click "Run as Administrator". A command Prompt should appear with nothing but a $
    - Type /usr/bin/rebaseall -v, hit enter, and wait for the process to complete.
        - If you get errors about Cygwin processes running, try Step 1 again. If that still doesn't work, Restart your computer into safe mode and try these steps again.
        - A commenter noted that, depending on your settings, you may have to type cd /usr/bin && ./rebaseall -v instead.
    - Try opening Cygwin again.
</syntaxhighlight>
 
{| class="wikinotes"
|-
|-
| http://stackoverflow.com/questions/9300722/cygwin-error-bash-fork-retry-resource-temporarily-unavailable
| [[cygwin programs]]
|-
|-
| http://cygwin.wikia.com/wiki/Rebaseall
| [[cygwin troubleshooting]]
|}
 
 
</blockquote><!-- rebaseall -->
 
</blockquote><!-- Common Problems -->
 
= Programs =
<blockquote>
Cygwin does not by default include a CLI package manager. Instead, you run cygwin.exe with the flag
'config', which updates your existing cygwin (labeled as installation, but only checks for missing/out
of date files). I have included the option of running 'CygwinPers.bat --config'. There are package
managers available for cygwin, such as apt-cyg, but they're pretty awful. It is much better to just
use the default installer.
 
Base Packages:
<syntaxhighlight lang="bash">
## Cygwin Packages
bc
offlineimap
msmtp
mutt
w3m
ncurses
abook
xclip
git, git-completion, gitk, tig
openssh
gcc
automake
python2
python3
 
xorg
rxvt-unicode
nc
nc6
tmux
zsh
irssi
rsync
 
 
## External Packages:
  urlview (win32) -- http://www.oocities.org/win32mutt/win32.html
  mutt with sidebar -- http://www.alexbr.com/wblog/?p=183
 
</syntaxhighlight>
 
== Terminal Programs ==
<blockquote>
{| class="wikitable"
|-
| [[mintty]]
|-
| [[openssh]]
|-
| [[mutt]]
|-
|-
|}
|}
 
</blockquote><!-- Notes -->
 
=== vim ===
------
<blockquote>
Vim works perfectly, but some of the plugins have quirks that will need to be rewritten.
These cygwin-specific issues will be  tracked under [[vim]].
 
''' NOTE '''<br>
If you install a plugin, and get errors about ^M line endings in it's source files,
You can fix in a very simple way. Simply open the sourcefile and execute:
<syntaxhighlight lang="vim">
:set ff=unix
:wq
</syntaxhighlight>
 
 
 
</blockquote><!-- vimya -->
</blockquote><!-- vim -->
 
=== utimer ===
------
<blockquote>
A little script for setting alarms from the commandline. I have it all integrated with tmux
though, and especially at work it would be useful to force myself to checkup on people every
now and then, or stretch.
 
https://launchpad.net/utimer
 
<syntaxhighlight lang="bash">
cygwin --config  --> pkgconfig, intltool
 
./configure
make
make install
 
## make install does install the manpage, but
## utimer doesn't seem to be in the correct place
## copy it to /usr/bin
cp src/utimer.exe /usr/bin/
 
</syntaxhighlight>
</blockquote><!-- utimer -->
 
=== unrar ===
------
<blockquote>
 
<syntaxhighlight lang="bash">
curl -#O http://www.rarlab.com/rar/unrarsrc-5.2.4.tar.gz
tar -xvf unrar*
cd unrar*
make -f makefile.cygmin (#doesn't exist)
(I don't have this working yet...)
</syntaxhighlight>
 
</blockquote>
 
=== vifm ===
------
<blockquote>
vifm is a super awesome, and speedy terminal filemanager. I like it a lot.
 
 
<syntaxhighlight lang="bash">
curl -#O http://sourceforge.net/projects/vifm/files/vifm/vifm-0.7.8.tar.bz2/download
tar -xvf vifm*
cd vifm*
./configure
make
cp vifm.exe /usr/bin/
 
</syntaxhighlight>
</blockquote><!-- vifm -->
 
=== ranger ===
------
<blockquote>
Ranger is a vim-style, tabbed, terminal filemanager that lets you browse
through your filesystem and preview files REALLY REALLY QUICKLY. Perfect
for jumping through the script directory.
 
<syntaxhighlight lang="bash">
## Make sure python2.6+ is installed
cd ~
curl -#O http://nongnu.org/ranger/ranger-stable.tar.gz
tar -xvf ranger-stable.tar.gz
cd ranger-X.XX
python setup.py install --optimize=1 --record=install_log.txt
cd ..
rm -rf ranger*
</syntaxhighlight>
</blockquote><!-- ranger -->
 
 
=== sshfs/fuse ===
------
<blockquote>
cygwin doesn't have sshfs per-se, however there are a couple of windows
ports of fuse/sshfs that work marvelously (although require a GUI unfortunately...).
Of the two, dokan is portable, so it will be my preference.
 
Dokan does not accept command-line flags, but a forum user showed his autohotkey
script that he used as a wrapper for it:
 
<syntaxhighlight lang="autohotkey">
Run "C:\Program Files (x86)\Dokan\DokanSSHFS\DokanSSHFS.exe"
sleep 1000
Send {tab}{tab}{tab}{tab}{tab}{tab}{tab}{tab}{tab}{tab}password{tab}{tab}{tab}{tab}{tab}{tab}{enter}
sleep 4000
Send {enter}
</syntaxhighlight>
 
 
{|
| http://dokan-dev.net/en/download/#sshfs
|-
| https://code.google.com/p/win-sshfs/downloads/detail?name=win-sshfs-0.0.1.5-setup.exe&can=2&q=
|}
 
</blockquote><!-- sshfs -->
 
=== ipython ===
------
<blockquote>
<syntaxhighlight lang="bash">
pip2 install ipython
 
 
</syntaxhighlight>
</blockquote><!-- ipython -->
 
 
=== PySide ===
------
<blockquote>
<syntaxhighlight lang="bash">
## Cygwin Install: qt4 (check many packages)
 
cp /usr/bin/qmake-qt4
 
 
git clone https://github.com/PySide/pyside-setup.git pyside-setup
pip2 install wheel
python2 setup.py bdist_wheel --qmake=/usr/bin/qmake-qt4 ## haven't had this work just yet
 
</syntaxhighlight>
</blockquote><!-- PySide -->
 
 
=== (python) schedule ===
-----
<blockquote>
This looks very promising as an alternative to cron that does not require the windows'
task scheduler.
 
{|
https://github.com/dbader/schedule
|}
</blockquote><!-- Schedule -->
 
=== disused ===
<blockquote>
==== statnot ====
------
<blockquote>
statnot is another minimal notifications system. It has less dependencies still than dunst.
 
STATNOT REQUIRES X TO BE RUNNING, WHICH I DON'T WANT TO BOTHER WITH. INSTEAD I'M JUST
USING MY PERSONAL TMUX NOTIFICATION SCRIPT RATHER THAN PASSING IT THROUGH NOTIFY-SEND.
NOTIFY-SEND IS ONLY REALLY USEFUL IN LINUX ANYWAYS IF I'M LOOKING AT A WEB BROWSER. I
CAN REWRITE MY ACTUAL NOTIFICATION SCRIPT TO CALL NOTIFY-SEND OR WINDOWS NOTIFICATIONS
DEPENDING ON THE OSTYPE.
 
<syntaxhighlight lang="bash">
cygwin --config --> python2, python-dbus, python-gtk
 
</syntaxhighlight>
</blockquote><!-- statnot -->
 
==== dunst ====
------
<blockquote>
Dunst is a notification system. I use it to pass messages to all my tmux sessions
so that I don't miss messages or important alarms. It can run headless (sweet).
 
DUE TO THE UNAVAILABILITY OF LIBXDG-BASEDIR IN CYGWN (ALTHOUGH BEING PORTED), I CANNOT USE
DUNST.
 
<syntaxhighlight lang="bash">
cygwin --config --> dbus, libxinerama, libxft, libxss, libnotify
 
# you'll also need to compile some other dependencies:
libxdg-basedir
 
</syntaxhighlight>
</blockquote><!-- dunst -->
</blockquote><!--disused Terminal Programs -->
 
== X Programs ==
<blockquote>
=== Xserver ===
<blockquote>
==== CygwinX ====
{| class="wikitable"
| <pre>%terminal%/cygwin/app/cygwin/cygwinXpers.bat</pre> || || [http://{{SERVERNAME}}/progs/config/cygwin/cygwinXpers.bat cygwinXpers.bat] || personal launcher script
|-
| <pre>~/.xstartwinrc</pre> || || [http://{{SERVERNAME}}/progs/config/cygwin/.startxwinrc .startxwinrc] || customize startup of xwin
|}
 
''' IMPORTANT NOTE'''
IF YOU ARE RUNNING WINDOWS AS A DIFFERENT USER THAN 'will' (ex: willp). My workaround for both
<code>.xinitrc</code>, and <code>.config/openbox</code>. was to use symbolic links to their locations
in will.
<syntaxhighlight lang="bash">
ln -s /home/will /home/willp
</syntaxhighlight>
 
 
<syntaxhighlight lang="bash">
# xorg-xerver
# win-xorg-clipboard
 
# There are options to customize startx and startxwin,
# I prefer to leave startxwin blank because when left alone,
# it can run ANY program as an argument, and it will create a
# windows' window for it.
#### ~/.startxwin ## Any instructions to be run every time startxwin is run
#### ~/.xinitrc ## Any instructions to be run every time startx is run
#### man xwin ## commandline flags for startxwin/startx
 
 
startx (programs to run) -- (xwin flags)
-rootless (no window decorations on xserver)
-keyhook (cygwin sees keypresses before windows) (allows windows key to be used)
 
ex:
startx /usr/bin/openbox  -- -rootless -keyhoook ## start openbox in same windowspace as windows
 
</syntaxhighlight>
<br>
<br>
 
==== WINAPI ====
I'm not entirely sure what this is, or how it works but this is how DWM is able to run
natively in windows, and manage win32 windows ( but not cygwin windows unless launched with
startxwin /usr/bin/<progrm> )
 
 
</blockquote><!-- Xserver -->
<br>
<br>
 
=== Fonts ===
<blockquote>
{|
| <pre>/usr/share/fonts/font.ttf</pre> || font dir
|-
| <pre>fc-list</pre> || list all fonts
|}
There is not a lot of options for fonts in the cygwin package repo, Here
are the fonts that I use most frequently:
 
<syntaxhighlight lang="bash">
## Droid-Sans-Mono (preference)
http://www.fontsquirrel.com/fonts/droid-sans-mono
 
## DejaVu
http://sourceforge.net/projects/dejavu/
 
## copy fonts to /usr/share/fonts/
fc-list ##List all currently available fonts
Urxvt.font: xft:Droid Sans Mono-10 ##Setting font for urxvt in ~/.Xdefaults
 
</syntaxhighlight>
</blockquote><!-- Fonts -->
 
=== feh ===
<blockquote>
feh is an awesome image viewer. requires imlib2
 
<syntaxhighlight lang="bash">
## CYGWIN DEPENDENCIES:
# imlib2, libcurl, libcurl-devel, libpng, libX11, libXinerama, libXt-devel
# make sure to install all imlib, imlib2, libiml, and devel packages from setup.exe
#
# note that when hunting down a package because of a compile error, you can use
# cygcheck for more info ex: cygcheck -p x11/Intrinsic.h
 
curl -#O http://feh.finalrewind.org/feh-2.12.tar.bz2
make
make install
cp feh.exe /usr/bin/
</syntaxhighlight>
 
</blockquote><!-- feh -->
</blockquote><!-- X Programs -->
</blockquote><!-- Programs -->

Latest revision as of 04:03, 2 July 2022

Cygwin provides a unix-like environment to run processes under windows by translating unix syscalls.
It has no CLI package manager, but the installer can be scripted to install packages.

Notes

cygwin install
cygwin package management
cygwin configuration
cygwin programs
cygwin troubleshooting