Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <7dd7b97a05031512037bc6fb10@mail.gmail.com>
Date: Tue, 15 Mar 2005 15:03:34 -0500
From: John Westbrook <john.westbrook@gmail.com>
Reply-To: John Westbrook <john.westbrook@gmail.com>
To: cygwin@cygwin.com
Subject: Single Packaged Shell?
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I use cygwin for data analysis purposes for my employer. Up to this
point, I have produced reports as my unit of output. However, my
employer now wants to export my home-grown toolset to end users, which
makes me an application vendor, not a data analyst.

Aside from my anxiety over this sudden outbreak of scope creep (truly
a disease), I am struggling to find out how to distribute a
user-friendly version of my toolset to users who think that perl
scripts grow inside shell scripts in the ocean.

I have heard that you can compile perl code into c code, so I was
wondering if anything similar exists for shell scripts or even cygwin
itself. Ideally I would like to distribute an executable that uses a
shell script as its entry point, but does not require a cygwin
installation on the host.

If there is some way to package the few standard programs I need
(bash, perl, unzip, etc.) with my custom scripts, that would be
acceptable as well. It cannot by too hackish, but I could do a
reasonable amount of customization, as I am actually a programmer in
disguise.

Any help is greatly appreciated.

Thanks,

John Westbrook

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/