From: John Haugabook <johnhaugab...@gmail.com>

Running setup-x86_64.exe and performing an individual search for each package, 
is a pain in the neck. And the user running "setup-x86_64.exe -q -P packageName"
may have a typo and the package would not be installed.

So by copying and pasting these commands into the terminal setup-x86_64.exe 
runs 
a preliminary search, so when they reach the "Select Packages" window these 
packages
will be amongst the packages ready to be downloaded. Additionally sorting them 
makes it 
easier to go down the list, and make sure all packages are listed.

Putting separate commands allows the user to pick which packages to download in 
the 
case they want to run config, where those packages are not needed i.e. 
--without-cross-bootstrap.

Signed-off-by: John Haugabook <johnhaugab...@gmail.com>
---
 winsup/doc/faq-programming.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml
index 4daeb7079..b9269187c 100644
--- a/winsup/doc/faq-programming.xml
+++ b/winsup/doc/faq-programming.xml
@@ -710,6 +710,18 @@ packages. Building the documentation can be disabled with 
the
 <literal>--disable-doc</literal> option to <literal>configure</literal>.
 </para>
 
+<para>
+Below are ready-made commands to download the required 
+packages. When you reach the <emphasis>Select Packages</emphasis> screen, 
+these packages should be amongst the search results.
+</para>
+<screen>
+$ setup-x86_64.exe -P 
autoconf,automake,cocom,gcc-g++,git,libtool,make,patch,perl                     
      # download build tool packages
+$ setup-x86_64.exe -P 
gettext-devel,libiconv,libiconv-devel,libiconv2,libzstd-devel,zlib-devel        
      # download dumper packages
+$ setup-x86_64.exe -P mingw64-x86_64-gcc-g++,mingw64-x86_64-zlib               
                             # download utility packages
+$ setup-x86_64.exe -P 
dblatex,docbook-utils,docbook-xml45,docbook-xsl,docbook2X,perl-XML-SAX-Expat,xmlto
    # download documentation packages
+</screen>
+
 <para>Next, check out the Cygwin sources from the
 <ulink url="https://cygwin.com/git.html";>Cygwin GIT source repository</ulink>).
 This is the <emphasis>preferred method</emphasis> for acquiring the sources.
-- 
2.49.0.windows.1

Reply via email to