How to Install Cygwin+GCC GCC - How to Install Cygwin+GCC Disclaimer The Instructor, the ECE Department, and Portland State University will not accept responsibility for any file or system damage that might be caused by installing or using Cygwin software on your computer. Take precautions, such as using virus and malware scanners and backing up your important files, before installing downloaded software.

Mar 13, 2014 Complete Walkthrough on How to Install Cygwin on Windows. Instructions: First step: Check the System type of your computer (32. Important: For programmers, you certainly need to open the 'Devel' (Development) category and select 'gcc', 'g++', 'gdb', 'make', and others, which are not part of the default selection. Browse thru all the categories. Complete the installation process. You can always re-run 'setup' to install additional packages later.

Getting CygwinWebsite: Download to a convenient directory on your local drive. Installing Cygwin & GCC • Run the setup-x86.exe file to begin installation. (Note: You may need local administrator rights.) • The initial Cygwin Setup window appears. • Click [Next >]. • The Choose Installation Type window appears. • Select the 'Install from Internet' option. • Click [Next >].

• The Choose Installation Type window appears. • In the Root Directory input box, type in the directory path where you want Cygwin installed. • In the Install For selection box, choose the desired type (All Users or Just me). • Click [Next >]. • The Select Local Package Directory window appears. • In the Local Package Directory input box, type in the directory path where you want to store the downloaded installation packages.

Note: This is not the same as the Cygwin root directory that you chose in the previous step. • Click [Next >]. • The Select Connection Type window appears. • In most cases, the default Direct Connection option is most appropriate. • Click [Next >].

• The Choose Download Site(s) window appears. • From the list of Available Download Sites:, select a site from which to download the Cygwin packages (try a U.S.

Or nearby location). • Click [Next >]. • After a minute or two, the Select Packages window appears. • From this window, choose the Cygwin applications to install. For our purposes, you will select certain GNU C/C++ packages. • Click the + sign next to the Devel category to expand it. • You will see a long list of possible packages that can be downloaded.

Scroll the list to see more packages. • Pick each of the following packages by clicking its corresponding 'Skip' marker. • gcc-core: C compiler subpackage • gcc-g++: C++ subpackage • libgcc1: C runtime library • gdb: The GNU Debugger • make: The GNU version of the 'make' utility • Note: If a package has not been previously installed, then clicking the 'Skip' marker selects the package and shows its version number.

• Click the – sign next to the Devel category to close it. • Click the + sign next to the Libs category to expand it. • Pick the following package by clicking its corresponding 'Skip' marker. • libmpfr4: A library for multiple-precision floating-point arithmetic with exact rounding (Note: On some systems this may already be selected. If so, you may ignore this step.) • Click the – sign next to the Libs category to close it. • In addition to the specific packages you picked, the setup program automatically selects other packages that are needed to build a working Cygwin environment.

• Click [Next >]. • If a 'Resolving Dependencies' window appears, just click [Next >]. • The download progress window appears. It will take a while for the downloads and installation to finish. • After package installation is done, the Installation Status and Create Icons window appears.

• Make your icon selections. • Click [Finish]. You have now completed installing Cygwin and GCC. Using Cygwin • If you prefer using the C compiler in the text-only command line mode, begin by double-clicking the Cygwin Terminal icon on the Windows desktop. • If you prefer using a graphical integrated development environment (IDE) instead, you will need to download and install NetBeans next.

A full Cygwin installation can range from 21 to 105 GiB, depending on how you define 'full.' Your 100 MB number tells me that you just clicked through the defaults presented by Cygwin's setup-*.exe program, selecting no optional packages, because that installs only the Base package set, which currently amounts to 100 MiB. Cygwin follows the modern net-connected software distribution model: it assumes you can just run setup-*.exe again and select new packages as you need them. It's normal to start with that 0.1 GiB base installation, then add packages as you need them.

The Cygwin maintainers try to keep the Base category's package set as small as practical.¹ A Cygwin Base install gives you something much like an old-style Unix installation, covering little more than. So How Do You Get a Full Installation? The Cygwin installer does not have an obvious way to get a 'full' installation, on purpose, because no one needs literally every package in the Cygwin repository.² There is, however, a sneaky way to install everything.

At the package selection screen.click the 'Default' text to the right of the 'All' group header. It will change to 'Install,' as will the corresponding text in all of the groups underneath it. This marks everything for installation. I include this tip for completeness only. You do not want to do this!

It will install gigs and gigs of stuff you will never use. Currently, there are 9951 in Cygwin,³ and installing every last one of them takes 83.4 GiB of disk space for the installation tree plus 21.3 GiB for the download tree.⁴ That gives the 105 GiB upper limit above. All that unused software carries several costs. Even if disk space, download time, installation time,, and local bandwidth use are of no consequence to you, consider the the generous wasted bandwidth. I've done the experiment, so now you don't have to. An Intelligent 'Complete' Installation I've come up with a simple set of package exclusion rules that results in a much smaller installation: • Skip all of the -debuginfo packages.

Few people need these, and they take up a lot of space. Savings: 53.4 GiB in the installation tree alone; more in the download tree. It's easy to apply this rule. After selecting all packages for installation with the sneaky trick above but before you move on to the next screen, click the 'Install' text next to the 'Debug' category header until it switches back to 'Default.' (Or if you've already installed them, click it until it says 'Uninstall' instead.) • Do not explicitly install any of the lib* packages. Let Cygwin's setup-*.exe automatically install libraries to satisfy package dependencies. Savings: about 5.1 GiB ⁵ To apply this rule, switch the 'Libs' category to 'Default' or 'Uninstall' as you did with the 'Debug' category.

The installer will figure out which libraries you actually need in a later step. • Skip the and associated packages.

Again, few people need these.⁶ Savings: 3.7 GiB There are basically two sets of cross-development tools in Cygwin: the set for creating Cygwin executables of the other (i.e. 64-bit tools and libraries for 32-bit Cygwin, or vice versa) and the set for building executables of the same word size as your Cygwin installation. To apply this rule for a 64-bit Cygwin installation, while still on the 'Select Packages' screen, type cygwin32- in the package name search box at the top of that screen, then click the Default text next to each top-level category until it cycles back to Default, thereby changing all the underlying matching packages' Install modes back to Default, which is not to install them if this is the first pass through setup-*.exe. Or, if you have already installed these packages, change these modes to Uninstall. Repeat that for mingw64. The idea is the same for 32-bit Cygwin, except that you search for and exclude packages with cygwin64- and mingw32- in their names instead.

By following this rule set, I was able to install nearly everything, taking only about 21 GiB. Paring That Down We can get the installation to be even smaller by excluding several other notorious disk hogs: •, the desktop environments, and the GUI apps together require about 10.8 GiB.⁷ • A Cygwin Base + Devel installation comes to 9.6 GiB. • A Cygwin Base + TeX category installation takes about 4.8 GiB. If you installe only your native language's support package, it comes to about 3.7 GiB instead.

• All of the -doc packages combined chew up about 4.5 GiB of disk space Someone who isn't a software developer, who doesn't use Cygwin for GUI stuff, who uses the Web for docs, and who doesn't use TeX for document creation could thus have a 'full' Cygwin installation in only about 1 GiB.⁸ If you use Cygwin the way it is intended to be used, installing the base and only the extra packages you need at the moment, you probably won't even get your installation size to even those levels. I use Cygwin this way, and my installations are typically well under 1 GiB, yet they are 'complete,' in that they meet my current needs. For Extra Disk-Filling Fun. All of this testing was done with the 64-bit version of Cygwin. You can roughly double the above space requirements by installing a parallel 32-bit Cygwin installation.⁹ This is not pointless.

It is a viable alternative to using cross-compilers, for one thing. For another, the of the two Cygwins means you may have need of both. Footnotes • There are occasional threads on the Cygwin mailing list where someone argues that some very common package should be included in the Base category, such as Perl, and the result is usually that the maintainers decide not to add it to Base. You also occasionally see the opposite: some package accidentally slips into Base, usually via an incorrect dependency. Stackridge Something For The Weekend Rarest. Shortly after the problem is brought to the attention of the Cygwin maintainers, the status quo ante is restored. () • Perhaps I am wrong. There could be a immigrant who completes on the side while not busy brushing up on his technical vocabulary by translating into his adopted.

I want to meet him. He sounds like an interesting guy. Plus, I think I can help him with his plan to create a GUI front end for.

Naturally, I will try to talk him into porting it from to /. I mean, Tcl/Tk, seriously?

Let's not be ridiculous. • curl -s grep -c x86_64/ • Cygwin's setup-*.exe doesn't delete the downloaded package files after installing them. This is useful at sites where you have multiple Cygwin installations, since you can put the download directory on a shared network drive. Each package then only has to be downloaded once at that site. My 105 GiB upper limit assumes you will download and install to the same drive, and that you will keep the download tree in case you need to reinstall it later. (All sizes in this answer are space-on-the-wire numbers, by the way, not space-on-disk numbers: will increase the size of the download and installation trees, the latter to a much greater degree, since the proportion of small files is much greater in the installation tree. Expect something like +1% in the download tree and +5% in the installation tree.) Not only does setup-*.exe not delete downloaded package files after installing them, it doesn't auto-purge old versions, so your download tree grows and grows over the years you use Cygwin.

(There are scripts floating about the net to solve this problem, such as.) • You may wonder why there are libraries in the Cygwin package repository that you don't need even though you've installed 'all' packages. There are several reasons: • some libraries are obsolete, but are still present on the mirrors • some libraries come in multiple alternative forms, so that people who know they need something other than the default can choose it • some libraries are there only for people writing their own programs, not to support any existing Cygwin package • Pretty much the only people who need the Cygwin cross-compilers are the people maintaining Cygwin packages, since maintainers are expected to build for both 32-bit and 64-bit Cygwin unless there is a good reason not to. There are probably more people with a good justification for MinGW cross-development tools, but there's also the option of using MinGW and MSYS instead of Cygwin. Also, I am guessing that the number of people who do dual-stack Cygwin + MinGW development is smaller than the set of people who use one or the other exclusively, or nearly so. • It is not easy to do this exclusion, because GUI packages are scattered throughout the Cygwin packaging system, and their top-level category often contains non-GUI software, so you can't simply exclude the whole category.

Math.) The first pass is to exclude the X11, GNOME, KDE, LXDE, MATE, Xfce, and Games categories using the same Categories view technique as above. Then, using the search box as we did for the cross-compiler exclusion above, remove packages matching gtk, gnome, qt, and kde, optionally excluding those in the Devel, Debug or Libs packages, if you need those. Finally, you'll have to switch to the Pending view and manually exclude a bunch of packages that weren't caught by either of those two broad exclusions:,,,,,,,,,,,,,,,,,,,,,,,,,,, and. If you don't exclude these, they'll drag back in much of what you excluded above as dependencies!

• You may notice that the size of all the excluded package sets adds up to more than the 21 GiB of the 'intelligent complete' installation. This is because of shared dependencies.

That is to say, these sizes overlap to some extent. • If you put both setup-*.exe programs in the same directory, they will share the download tree so that all of the noarch packages are downloaded only once for both Cygwins. Between that and the fact that 32-bit and 64-bit Intel compilers generate code that differs in size, installing both Cygwins doesn't quite double the disk space requirement. @SlySven: As for the Tcl/Tk comment, you do see that it's a joke, yes?

Well, mostly a joke: Tk should have been reskinned to something better than its current Motif-inspired default roughly 20 years ago. And yes, I'm aware that there are alternate Tk skins; I'm talking about defaults here. As for gitk as an example, that doesn't count as 'in 2017,' since the program was created in 2005.

Though given that the Motif look was quite dated even then, it's still a questionable tooling choice. – Jul 31 at 12:58. I would like to add to this thread.

Hannah Arendt Le Origini Del Totalitarismo Ebook Readers on this page. This approach gives you a leaner, meaner, bare-bones, minimal Cygwin install, with just the tools/items you need. No dependency bloat, no unwanted packages, files etc. I have been experimenting with Cygwin attempting to get a 'bare-bones', minimal install. I do find that installing utilities like grep, gawk, sed and similar tools has dependencies on cygwin, base-Cygwin and sometimes unwanted tools like bash, coreutils etc. I wanted to get only the tools and their required dlls installed and started examining the Cygwin package. I discovered that not using the setup.exe supplied by Cygwin is an alternative way to accomplish minimal Cygwin installs. And this is how I got it done: • Download only the packages you want from any of the Cygwin mirror sites using ftp or http.

Alternatively you can use the setup.exe supplied by Cygwin to download all the packages - download only and no install. • Once the download is successfully completed, individual packages like zlib, gawk, grep, libiconv are found under the x86/release or x86_64/release directory Each package is 'tar'red and compressed using tool 'xz' or bzip and stored in respective directories.