This is the mail archive of the
mailing list for the Cygwin project.
RE: Added setup.exe to User's Guide
- From: "Hannu E K Nevalainen (garbage mail)" <garbage_collector at telia dot com>
- To: <lhall at rfk dot com>, <cygwin at cygwin dot com>
- Date: Mon, 24 Mar 2003 23:35:36 +0100
- Subject: RE: Added setup.exe to User's Guide
> From: cygwin-owner at cygwin dot com [mailto:cygwin-owner at cygwin dot com]On Behalf
> Of lhall at pop dot ma dot ultranet dot com
> Your comments about installing Cygwin via setup using a local cache and/or
> burning a CD to install from do have merit. Can you suggest some wording
> that would describe a simple process that will work well? I think this
> would be the most hopeful and useful for inclusion.
As I understood from a posting of Igor Pechtchanski this isn't as hard as I
Well, now to the collection of words; something like this, maybe:
If you have a CD-burner, ZIP, Jazz, removable HD or some such at "home"
_and_ in a machine elsewhere, which also has fast internet access; you can
1. Use the fast internet access machine, create a temporary "Local Package
Directory" (the package cache) where there is enough space.
2. Download and use setup.exe to fill the above cache with whatever
contents you wish (Download from Internet in setup.exe).
3. *Move* the ENTIRE cache directory onto a CDR (or whatever) - do NOT
change anything within the cache.
4. Carry the CDR (or whatever) "home", where you will be able to use it
directly as "Local Package Directory" for setup's "Install from local
NOTE1: The prerequisite here is that you do put THE DIRECTORY CONTAINING
THE CACHE onto your CDR. Do something else and you will have trouble using
it at "home".
NOTE2: If there is more packages than can be fitted on your "CDR" (e.g.
you're using ZIP-disks) then you need to select NO MORE packages AT A TIME
than can fit on your disk.
Comments or Corrections anyone?
(Don't say I got it right on the first try, I wouldn't believe you! ;-)
/Hannu E K Nevalainen, Mariefred, Sweden
I had the impression that setup.exe saved paths within it's *ini-file or
some such; thus forcing one to have *exactly* the same path at cache-disk
creation AND use time. (This can be accomplished by intelligent use of the
"subst" DOS-command. I don't know if "subst" is available for more than just
This "path saving" is one of the worst nightmares you can be caught of as
computer user. Windows has it, all over the place - I know people who have
been hit by Windows changing D:\WINDOWS -> C:\WINDOWS and thus destroying
everything! i.e. D: contains the Windows installation, all paths get reset
Xilinx Modelsim has it.
Borland's old C++ V5.02 has it.
OrCad PSpice has it.
These are the ones I remember right now... I KNOW there is more.
Create a BC5.02 project on one machine - make it work.
Copy the *.ide file and the sources to another machine.
If the compiler on the new machine was NOT installed under the same
path - you will end up with gery hairs pretty quick.
UNLESS you know to look into
Options->Project->Source Directories:Include & Library
If THESE do not point at the right place -> trouble.
THIS is a SIMPLE ONE to change.
Have a go at doing the same for PSpice projects or Modelsim...
AN APPLICATION-GLOBAL PATH THAT DEPENDS ON INSTALLATION POSITION (i.e.
PATH) DOES NOT BELONG IN A _*PROJECT FILE*_ THAT GETS CREATED BY THAT
Project files MUST be relocatable.
--END OF MESSAGE--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html