Thom L wrote:
> My goal is gain the full functionality of my cygwin installation
> and use PODS at the same time.
>
> Has anyone had success getting PODS to work with a full version of cygwin?
Yes. I should have made better notes, but I'll try to recall how
I did it:
1. Install PODS, including Cygwin. You will get to name the
directory in which to install Cygwin during the installation.
Name it something like "PalmSourceCygwin" so that later you'll
know it is associated withe the PODS installation.
2. Download and install the full Cygwin package, but when installing,
DO NOT install it over the PODS installation. Manually install
it into yet another directory (e.g., "CygwinFull").
Now you have two Cygwin installations. One is set up to work with
PODS, and the other one has a complete set of goodies.
Now you need to do two things to link up the two installations
and get them to coexist peacefully:
3. There is a .dll file used by Cygwin, called cygwin1.dll. It
is located in the /bin directory of the Cygwin installation.
Problem is, if you have two installations, Cygwin will get
confused, load the wrong cygwin1.dll, and then get fatal conflicts.
Now I hope I am getting this part right: what you need to
do is delete or rename the cygwin1.dll in the non-PalmSource
Cygwin (full) installation. Try starting up a bash shell,
by double-clicking on the Cygwin green and black icon.
If it works, you deleted/renamed the right one. Otherwise,
you'll get an error message saying there was a conflict with
that file -- something like "I found two Cygwin installations,
and I am very confused. Bye.".
This part can be a little tricky, so don't actually delete
either of the .dll files until you're sure you got it right.
It is much safer to rename them, for example, as "cygwin1.dll.SAVE".
One more detail that may be important: the Cygwin.bat file that
I'm running is the one from the PalmSource Cygwin installation.
That might matter. You can set the Target in the shortcut's
Properties dialog. The "Start in" directory should be the
same directory that the cygwin.bat file is in, which is the
root directory of the PalmSource Cygwin installation. (Plus,
you can also change colors, window size, etc. for your bash
shell using that dialog. Just in case you didn't know...)
4. To be able to access the commands in the full installation,
start up a bash shell, and in your Cygwin home directory,
add this to your .bash_profile or .bashrc file, and then
restart your bash shell to make it take effect:
export
PATH=/bin:/usr/bin:/cygdrive/d/apps/Cygwin/bin:/cygdrive/d/apps/Cygwin/usr/bin:.
Er, well *almost* like that... My full Cygwin installation is
in D:\apps\Cygwin, which translates to /cygdrive/d/apps/Cygwin
in the Cygwin environment. So replace "/cygdrive/d/apps/Cygwin"
with the equivalent path spec for your full Cygwin installation.
(In both occurrances in the command, of course.)
Now your bash shell looks first in the PalmSource Cygwin, which
is absolutely essential to get gcc to compile code for Palm OS.
Anything that isn't in the PalmSource Cygwin installation will
be found in the full Cygwin installation. That is why /bin
is listed first in the PATH, prior to /cygdrive/d/apps/Cygwin/bin.
I *think* that is all it takes! My configuration is good enough to
allow me to use ssh to get to my Linux box, and I can edit my source
code with vi either on Windows or Linux. And I get all of the Unix
commands in the full Cygwin release, not just what PalmSource decided
to include. I have not tried getting an X server running, or really,
much of anything else. So I hope this method works to do what you
need.
Good luck.
Jay Ts
--
When we stop playing the game, there is no game.
- David Icke
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
