[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] gnumed installation problem
From: |
Jim Busser |
Subject: |
Re: [Gnumed-devel] gnumed installation problem |
Date: |
Mon, 10 May 2004 21:51:57 -0700 |
I got stuck back on April 11 when trying Karsten' s suggestion yielded
only the terminal output shown at bottom (and then in the meantime have
had other priorities.) I have just tried again with the same result.
On Apr 11, 2004, at 3:50 AM, Karsten Hilbert wrote:
Jim,
you are really close !
<snip>
d66-183-119-10:~ jb$ cd gnumed/gnumed/client
d66-183-119-10:~/gnumed/gnumed/client jb$ ls
CVS gm-slave-test-from-cvs.sh
__init__.py gnumed.sh
bitmaps locale
business manual
code_examples pycommon
data python-addons
doc python-common
etc python-tools
exporters test-slave.py
gm-from-cvs.sh wxpython
^^^^^^^^^^^^^^
this is what you are after
run it from the shell prompt (eg in a terminal window) like
this:
$> ./gm-from-cvs.sh
and you *should* be good to go
Karsten
Terminal output (Mac OS 10.3 running bash)
d154-20-203-171:~/gnumed/gnumed/client jb$ ./gm-from-cvs.sh
Gnumed -> client
log file is [/Users/jb/gnumed/gnumed/client/gm-from-cvs.log]
Activating verbose log level for debugging.
Determining GnuMed base directory ...
- environment variable GNUMED_DIR not set
(only necessary if nothing else works, though)
- standard path [/usr/share/gnumed/] not accessible
- seems like we are running from an arbitrary
directory (like a CVS tree or on Windows)
Determining GnuMed resource directory ...
- standard resource path [/usr/share/gnumed/] not accessible
- seems like we are running from an arbitrary
directory (like a CVS tree or on Windows)
WARNING: option <client encoding> not set in config file
This program needs access to the screen. Please run with
'pythonw', not 'python', and only when you are logged in on the main
display
of your Mac.
You should name this workplace to better identify the machine !
To do this set the option "name" in the group [workplace] in the config
file !
## Component Manager: attempting to find symbols in a component alias
of type (regR/carP/x!bt)
Notes:
I had by that point reached a "Welcome to Gnumed" window whose Login
was depicted as - xxxDEFAULTxxx, but I could not click, nor tab, into
the userid/password fields, which behaved as disabled as did the user
popup and the buttons below the fields.
As I exited the Mac OS 10.3 (bash) Terminal application, its
confirmation dialog indicated "Closing this window will terminate the
following processes: login, bash, sh, python" (Options: Cancel
Terminate)
Within my Mac toolbar, which displays the running applications, no new
application icon had appeared to join those already in my toolbar.
Should there have been, or is Python here just a process? And if it is
"normal" for no new application icon to have joined those "running",
how would I even navigate back to the GnuMed "application", if I were
in the meantime to have left GnuMed briefly in order to do a bit of
work in some concurrently running application?
When I had installed from CVS (which I did on the local computer), was
it adequate to have been logged in as myself as the computer's main
administrator (but not as root), so that I installed and am running
gnumed from the files residing in my machine's Users directory?
- Re: [Gnumed-devel] gnumed installation problem,
Jim Busser <=