Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<4.1.19990921011647.00a2ae50@uclink4.berkeley.edu>
X-Sender:	theyeh AT uclink4 DOT berkeley DOT edu
X-Mailer:	QUALCOMM Windows Eudora Pro Version 4.1
Date:	Tue, 21 Sep 1999 01:20:09 -0700
To:	cygwin AT sourceware DOT cygnus DOT com
From:	David Yeh <theyeh AT uclink DOT berkeley DOT edu>
Subject:	Distributing packages that use cygwin
Mime-Version:	1.0

Is it possible to use cygwin to compile an application from source and
distribute it as a binary without making the users install all of cygwin?
If so, what are some possible problems?  For example, what if the
application needed access to the file structure?  (namely, tmp)  Woule the
application have to be modified and recompiled with no filestrucutre
dependencies?

Also, is it a good idea to make future cygwin releases include the tmp as
implicit in the file structure (as dev and proc are) and just link it to
whatever the TEMP directory under windows is.


Thanks,
David
  o    _______________                            |\
 /\_  _| David       |    Class of 2002           | |
_\__`[_______Yeh_____|                           () |
] [ \, ][         ][  theyeh AT uclink4 DOT berkeley DOT edu  ()


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -