Re: Installing and configuring Argyll?
Re: Installing and configuring Argyll?
- Subject: Re: Installing and configuring Argyll?
- From: Graeme Gill <email@hidden>
- Date: Sun, 27 May 2007 11:29:24 +1000
Mike Adams wrote:
This might be asking a lot, but I wonder if any of the members of this
list that have gotten Argyll up and running on OSX might be willing to
help me out or at least point me in the right direction.
The other place to ask is on the Argyll mailing list:
<http://www.freelists.org/list/argyllcms>
profiles. The device I've got to use is a DTP41B which was actually
donated to me by a customer for this project--just to prove there are
some truly nice people left in the world.
The thing has a dark grey case, and a serial connection on the device,
but--and I don't know whether this is standard for these things or it
was an add-on--the connector I got to the computer is USB.
Ahh - one of the USB capable 41's - I've seen one, but don't have
access to one anymore, and I've found no information from X-Rite about
the USB operation which is why USB DTP41 operation isn't supported
in Argyll. The instrument should have come with a normal serial
cable as well, which you'll need to be able to use the instrument.
Evidently I have to do something called set the path to get the shell
to see the executables in the directory, but when I tried that, it told
me it was a directory, as if I wasn't supposed to.
Step-by-step, how do I configure the machine to see the device, and
does it need to be serial?
How do I simply run the programs?
One way is simply to run them. Check what you want to
run is really where you think it is:
ls -l /usr/bin/argyll/targen
You should get information on the files permissions (which should include
x for executable), it's owner, group, size, date & name. If it's
not there, you'll need to find it (ie. have you actually put the
executables in /usr/bin/argyll/bin ? - if so, substitute this in
what follows here)
Then you can simply execute it:
/usr/bin/arygll/targen
since you gave it no arguments, it should return usage information.
If you cd to that directory, you can execute it
without a smaller explicit path:
cd /usr/bin/argyll/targen
check we're in that directory:
pwd
run targen:
./targen
the . is shorthand for the current directory.
You can go back to your home directory using:
cd
or
cd ~
as ~ is shorthand for your home directory.
You can check your current path using echo:
echo $PATH
Note that PATH is the name of the environment variable holding
the executable search path, and $PATH represents it's value.
You can temporarily add the argyll directory to the PATH thus:
PATH=$PATH:/usr/bin/argyll
This is simply setting PATH to a new value, which is the concatenation
of it's current value $PATH with the path separator character : and
the additional path to the Argyll executables.
You can check it got appended:
echo $PATH
You should be able to execute targen without any preceding paths now:
targen
To make this change in PATH permanent, you need to modify the shells
startup file. This depends on which shell you're running. I'm not
sure, but this might be bash by default (I'm running zsh for
historical reasons, which is why I can't be sure what you've got).
Try running ps to see:
ps
This shows the current processes you are running, which should be the shell.
If it bash, then you need to modify your .bashrc file in your home
directory. Your home directory name is in the HOME environment variable:
echo $HOME
(You can see all the environment variable and their values
using set:
set
)
Check you've got the right file:
ls -la $HOME/.bashrc
Because .bashrc begins with . it is normally hidden.
If you want to edit it with a GUI based editor like
TextEdit, then it's probably easiest to make a copy
to edit:
cd
cp .bashrc bashrc.txt
and edit bashrc.txt. Add PATH=$PATH:/usr/bin/argyll to the end,
on a separate line. Save it out and then copy it into place:
cp .bashrc .bashrc.bak
cp bashrc.txt .bashrc
You can check it looks OK:
cat .bashrc
You'll need to start a new shell to see the new file have
any effect. You can check by looking at your PATH:
echo $PATH
Hope this helps.
Graeme Gill.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden