This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
TkMan with Win32 TCL stuff
- To: gnu-win32 at cygnus dot com
- Subject: TkMan with Win32 TCL stuff
- From: Chad Loder <cloder at ccs dot neu dot edu>
- Date: Sun, 2 Nov 1997 19:51:59 -0500 (EST)
- Reply-To: cloder at acm dot org
Does anyone know if it's possible (without major headaches) to get TkMan to
run under Win32?
Also, while I'm on the subject...I am familiar with UNIX tools, etc., and
the setup of GNU-Win32 has been fairly easy. My problem is that I'm having
trouble deciding on the best directory structure for my Windows NT system.
Right now, I have something like this:
E:\ (mount point corresponds to /)
utils
rktools
gnu-win32
mkstools
(various other programs)
rman
DevStudio
apps
gstools
Program Files
WinZip
WinRAR
CRT (a great telnet/rlogin program!)
(various other programs)
Now, I want to use .exe's from all of these directories, but I don't want to
add all of these directories to my path. I decided to make a /bin directory
and put symbolic links to my commonly used .exe's, but some of these require
DLLs and whatnot...how should I organize all this stuff? Most UNIX systems
I've used have been pretty huge and messy, with various packages and things
floating around in /bin, /usr/bin, /usr/local/bin, and all of their
subdirectories, so it was pretty hairy.
I would rather not mess up my existing structure too badly...I'm of the
opinion that any program or script which absolutely requires a program to be
in a certain hard-coded directory is a piece of crap (e.g., requiring /bin/sh
to exist).
Does anyone have suggestions on how to organize my directories so I can
access my tools from the bash command line and still keep the tools separate?
-chad
----------------------------------------------------
| Chad Loder - Somerville, MA, USA |
| EMail: cloder@acm.org |
| Home Page: http://www.ccs.neu.edu/home/cloder |
----------------------------------------------------
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".