[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] re: cygwin
From: |
sjtan |
Subject: |
[Gnumed-devel] re: cygwin |
Date: |
Tue, 19 Oct 2004 23:08:54 +1000 |
User-agent: |
Mozilla Thunderbird 0.8 (Windows/20040913) |
I wonder if hacking on the Cygwin PG port isn't obsolete
since 8.0 ? There's a native Windows version out now.
I'm not aware of the preferred way of getting gnumed to run on windows.
So I was using cygwin .
It's really to get gnumed to run on windows, whether the backend is on
cygwin or native.
(I haven't used 8, but 7.5) .
Cygwin is there for bash mainly. The 2 main incompatibities were:
The "ln" command doesn't work for windows, so one script changes all the
python
import Gnumed.. statements to import client.. statements. This should
be run
on a copy of of the client code , although there is a script to reverse
the changes.
(cygwin_path.sh does the changes , cygwin_restore.sh changes it back).
The bootstrap-gm_db_system.py didn't run , but the conf file idea is
really ok,
so the script parse_bootstrap.py parses conf files to get sql file
loading order info,
and install_schema.sh uses it using bash to run the cmd line postgres
commands.
This installs it in the cygwin postgres, and I've just tested it and
modified it so
it will run with the a windows postgres install ( which requires the -h
hostname parameter
mainly, and an installation user name of postgres , done in the windows
install).
So really cygwin with just bash and python is used for the install only .
To run the client using the windows python, there's a run-from-cvs.bat
file , which
requires the windows version of Python and the windows version of wxPython,
windows version of pyPgSQL, and windows version of gmDateTime.
These just download and install like any windows packages.
Nice to know it really is cross-platform.
- [Gnumed-devel] re: cygwin,
sjtan <=