Envs are not working on DEBIAN

[user_deleted]

Am adding a couple of Envs to My debian Env file ( Bashrc ) , As

MAYA_PLU_IN_PATH
MAYAMAN_ROOT
MAYA_MEL_PATH

It just appears as they make no difference, Relogined, Restarted, Still nothing happenes.

Thanks

[geoffcrowther]

knecht? i'm a wee bit rusty here.

[user_deleted]

The only suggestion that I can make my self is that is there a possibility that something is wrong with Maya installation ? I mean cause of the conversion from rpm to Deb or what so ever, is the a chance that it is Maya that is not understanding it's paths, And paths are in fact working properly, Since I am adding some echo commands to the Env and I can see them working when I get a console !!!!

Sounds wired some . . . .

Thanks

[knecht]

env variables problem:
it should work when you add as first lines in you .bashrc file in your home folder:
export MAYA_PLU_IN_PATH=whatever
export MAYAMAN_ROOT=whatever
export MAYA_MEL_PATH=wathever

you can check if they are set with:
echo $MAYA_MEL_PATH
then you should see whatever you have set it in .bashrc, does that work ?

all in all you should not need to set these variables to install or run maya

Maya RPM and Alien problem:

convert your maya rpm with
alien -c maya_xxx.rpm
then everything should be fine (-c says alien to take care of symlinks in the package)

here a copy&paste from an older post of me
I think Debian is the best linux for using it with maya 6. I have experiece with maya on suse, redhat and debian sarge. And debian is the best (not the easiest) way . . . .

I use the rpm and convert it with
alien -c packetname.rpm
it will create .deb packages

then install them with
dpkg -i filename.deb

you need to install the packages
maya6-0_xxx.deb
awcommon_6.0xxxx.deb

maya will be installed in the folder /usr/aw
you project folders are under your home directory in folder maya/projects

I have made good experience with installing
openmotif_2.1.30xxx.deb
but this is not necessary

you must have installed a 3D graphic driver and openGL !!

or look at this instruction how to install debian (a bit more detail)
http://www.highend2d.com/boards/showflat.php?Cat=1,6,7,8,9&Board=linuxforum&Number=189551&page=1&view=collapsed&sb=5&o=&fpart=http://www.highend2d.com/boards/showflat.php?Cat=1

i never heard from alien corrupted a package . . . maybe some rpm's not work, but if other got them run, it should also work on your machine

[user_deleted]

Thanks for your attention

Something very strange is happening here

echo shows the right paths, But I can't see the plugins in Maya's plug in manager , Trying to load them manually ( Using brows ) is just useless since there are a lots of Mel and .. . . that need to be loaded as well, and the most important thing is the license file which is embeded in Env ( Software is Mayaman ) .

I actually installed Maya 6 once again after converting with -c tag in alien and must confess some stuff are different, Before couldn't get to Maya using run application ( alt + f2 ) now I can, and some built in shortcuts ( /usr/aw/maya ) wasn't tthere that now it is.

Adding open motif did n't change something that I could find.

By the way now I have a file called bash.bashrc but in RH I had bashrc, Does it make any sense why the name is different, and the final question is does the user effect the Envs in my case which I always use the root.

Thanks again

[knecht]

i am not familiar with mayaman, sorry !

openmotif makes everything a little bit more stable. I works well without, but a little bit better with it installed on my PC)

using the root user should not effect the envs (has the user access problems ?)

/etc/bash.bashrc
is read by every user (global)

/home/username/.bashrc
or
/root/.bashrc
are the same like bash.bashrc, but just in effect when the user which own the home directory
don't ask me why they call it so and not bashrc . . .

[subjectego]

put this in your $HOME/.bashrc file:

export MAYA_PLUG_IN_PATH=/path/to/plugins [not MAYA_PLU_PATH]
export MAYAMANROOT=/usr/local/mayaman_install_dir
export MAYA_SCRIPT_PATH=/path/to/mel

I assume you want to setup Mayaman? In that case do:

export MAYAMANROOT=/path/to/where/you/installed/mayaman
export MAYA_PLUG_IN_PATH=$MAYAMANROOT
export MAYA_SCRIPT_PATH=$MAYAMANROOT/mel

you also have to set ANIMAL_LICENSE_FILE in case you license it with a file, read mayaman docs for doing that.

Bash reads $HOME/.bashrc _every time_ no matter if its a "login shell" or just an "interactive" shell (ie. if you want a full login shell then start an xterm with a "-ls" flag. If you start a login shell all regular login procedures will be executed as if you logged in a tty terminal (before you do a startx), bash will read /etc/profile (like all Korn type shells in fact) too, then $HOME/.bash_profile then $HOME/.bashrc.). $HOME/.bashrc seems to be the most usfull since every type of bash shell session reads it (interactive and login alike).

you also need to add:
export XBMLANGPATH=$MAYAMANROOT/mel/%B
in order to see mayaman icons in hypershade.
I also find this usefull (removing of default X cursor setback bug with Maya for Linux):

export MAYA_MMSET_DEFAULT_XCURSOR=1

to check all your maya environment variables, in a shell type:
export | grep -i maya

read man bash and man tscsh to learn about the 2 standard command line interpreters in a Unix system. Maya docs mention a lot of environment variables Maya uses too, search the docs.

hope this helped a bit, cheers

[user_deleted]

HI, Thanks for the reply

I actually have set all these Envs based on the Mayaman manuall, But still it doesn't look as if it works.

Using export | grep -i maya I get these stuff:

declare -x ANIMALL_LICENSE_FILE="/opt/mayaman/animall.dat"
declare -x LD_LIBRARYN32_PATH="/opt/mayaman"
declare -x MAYAMANROOT="/opt/mayaman"
declare -x MAYA_LOCATION="/usr/aw/maya"
declare -x MAYA_PLUG_IN_PATH="/opt/mayaman"
declare -x MAYA_SCRIPT_PATH="/opt/mayaman/mel"
declare -x XBMLANGPATH="/opt/mayaman/mel/%B"

However I can brows the plug ins in Maya but as you can simply guess when the envs are not working for Maya they are definitly not working for the license files as well, which in fact I can't BRWOS this time .

Have sorted everything about Debian ( Will send later about how I did it )
The only Current problem is Envs don't let the license for Renderman and Mayaman.

As for Renderman they don't declare the path to Renderman.

Cheers

[subjectego]

what I'm _guessing_ is that you are not starting Maya from the same terminal where export|grep -i maya returns that stuff, right?

Needless to mention, be very carefull about upper case/lower case spelling (Linux/bash/csh etc are all case sensitive). If you are starting it from that terminal thats really teally wierd then. Given your lic is not working with mayaman, give Animal Logic a shot - i'm sure they'll be helpful.. Wierd stuff though, I don't believe it has to do with your distro as distros have nothing much to do with the way bash and Linux kernel work..

[user_deleted]

Jesus, I couldn't ever imagine that starting Maya from a terminal might be different than run application ( alt+f2 ).

How ever using export | grep -i maya and export | grep -i mayaman and of course using the same council I could sort everything, Besides a very fact that I shouldn't be in root mode to run renderman/mayaman .

Thanks guys for all the kind help.

Amir

[joojaa]

Actualy even same holds true in windows. If you make a env var in a command propmt in m$ windows then the vars live only for that prompt and stuff spawned from it only (in some cases windows even does not inherit them!)! Just so you know.

[subjectego]

that whole mambo has to do with a "login" shell versus an "interactive" shell. (http://www.lesbell.com.au/Home.nsf/0/ec1040fb1ecd6097ca256f0d002361f4?OpenDocument)
Bash reads some scripts when you use it with interactive shell and other when you use it with a login shell