This is a followup to a question I asked on April 19.
My current path is:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
I do not currently have a $Home/.bash_profile in my Home directory
Please let me know if I have interpreted your answer correctly:
1) I do not currently have a "bin" subdirectory under Home, so I need to create this. I should copy the OpenSees executable to this subdirectory.
2) Under the Home directory I should create a profile file called $Home/.bash_profile. Such a file currently does not reside in my Home directory.
3) I should add a PATH statement into the profile. You said that you have placed the following line in the profile:
PATH=./:HOME/bin:/usr/local/bin:usr/local/rappture/bin:$PATH
Should I be placing the same statement in my profile, or should it be different given my current path?
I would also like to reiterate my original problem:
Currently I have the OpenSees executable and an example test1.tcl in the SAME folder on my desktop. If I run OpenSees from this folder (the program opens just fine) and type the command "source test1.tcl" I get the error "Couldn't read file "test1.tcl": no such file or directory". The same thing happens if I type "OpenSees test1.tcl" from the Terminal prompt, having moved into the directory containing both OpenSees and the example. As an old DOS hand, I don't see how changing the PATH would fix this. Please note that I can type in model building commands into OpenSees and everything seems to work.
I apologize for so many questions, but I am new to both OpenSees and Mac. I have OpenSees working in a Windows XP environment, wherein both the OpenSees source and example reside in the same directory. Everything works fine there.
A Followup question on MAC OS
Moderators: silvia, selimgunay, Moderators
A Followup question on MAC OS
F. Charney
Virginia Tech
Virginia Tech
as for the test.tcl, that is an interesting problem and i apologize for not ready your last post thoroughly. If you start OpenSees from the terminal by typing OpenSees you should be in the current directory. if you type the command pwd you should see the current directory.
if you start OpenSees by double clicking on it and you issue pwd you will be in your home dircetory. If this is the case you will need to cd into the current directry before you start OpenSees.
as for placing OpenSees on the PATH, i find it much easier that way as i deal with scripts in multiple directories and i always use a terminal window. i also do it on windows as i have a habit of running OpenSees from a dos terminal window.
the .bash_profile depends on your shell, you can see what shell you use when you type env. a simple solution would be to just copy the OpenSees executable to /usr/local/bin which is already on your path.
if you start OpenSees by double clicking on it and you issue pwd you will be in your home dircetory. If this is the case you will need to cd into the current directry before you start OpenSees.
as for placing OpenSees on the PATH, i find it much easier that way as i deal with scripts in multiple directories and i always use a terminal window. i also do it on windows as i have a habit of running OpenSees from a dos terminal window.
the .bash_profile depends on your shell, you can see what shell you use when you type env. a simple solution would be to just copy the OpenSees executable to /usr/local/bin which is already on your path.