Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 24 Feb 2003 17:38:19 -0500 From: Charles Krug To: cygwin AT cygwin DOT com Subject: Minimum Install for Executable Distrubution Message-ID: <20030224223818.GO14960@pentek.com> Mail-Followup-To: cygwin AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Cygwinners: We've built the gcc/as/ld toolset as a cross compiler to the Altavec PowerPC. We've been using it internally for a couple of weeks. Those of us with full developer Cygwin installations can run the program with no problems. We'd like to be able to distribute a minimal package to everyone here who needs the cross compile capability. Our first attempts seem to get confused about the correct paths to the executables. This is our first venture into distributing executables to people who haven't downloaded the entire package. What do we need to do to give people in the package? My thought based on the symptoms I've seen is that the gcc tools, being UNIX-centric will require at least a minimal official Cygwin setup, otherwise it won't grok the mount points. A coworker believes, "There MUST be a way to build it so that that's not necessary," To which I reply, "Perhaps, but would it be worth the trouble?" I BELIEVE the correct course of action would be to do a default Cygwin install and then distribute our cross development toolset. Would there be any problems doing it that way? Most important (to me), is there a Cygwin tool for assembling the correct packages? Thanks. Charles -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/