Sponsors
Sponsor Products
Maya 2019 Dependency Script (Verification)
posted by Mike Rochefort  on Jan. 23, 2019, 9:20 p.m. (1 month, 24 days ago)
1 Responses     0 Plus One's     0 Comments  
Hey all,

Last week after Maya 2019 dropped I spun up a container with it to try and figure out the dependencies. Word of warning: the documentation is out of date and doesn't include a few new additions, and could drop a few. Due to that, I decided to try and figure out all of the actual link-time(?) dependencies of the application and its tooling. The following script is what I've come up with.

https://gitlab.com/snippets/1798656

I didn't get any warning while running the application itself, but I also didn't do a fully comprehensive test run (there's only so much of Maya one person can know, and you know, time is a thing). How I got the list of all binary executables in the installation:

find /usr/autodesk/{maya2019,bifrost} -type f -executable -exec file -i '{}' \; | grep 'x-executable; charset=binary' | sed 's|:.*||'

I did a similar thing for all of the shared objects (*.so) in those parent directories, recursively. I then whipped up this Python script for running ldd on everything to see what was missing (using two functions probably wasn't necessary). All that was left was any small discrepancy that Maya spat at me when launching from the console, which was two, I think.

https://gitlab.com/snippets/1800558

This was all done starting from a minimal CentOS 7.6 docker image. Just posting this here to see if anyone wanted to verify this. There's a fair amount of small-time extras in here that could probably be removed, but I wanted to be as thorough as possible.

Also, does anyone know if openssl098e is necessary anymore? Maya seems more than happy to link (at install time, and this doesn't change) it's internal libssl.so.6 to libssl.so.10 from openssl if a system-level .so.6 doesn't exist.

Cheers,
Mike


Thread Tags:
  discuss-at-studiosysadmins 

Response from Jean-Francois Panisset @ Jan. 24, 2019, 12:30 a.m.
This is very interesting stuff, to answer one question in your posted documents, I believe senddmp.bin is the binary that sends crash dumps back to Autodesk, and which you can control with the MAYA_DEBUG_ENABLE_CRASH_REPORTING environment variable. JF On Wed, Jan 23, 2019 at 6:18 PM Michael Rochefort wrote: > > Hey all, > > Last week after Maya 2019 dropped I spun up a container with it to try and figure out the dependencies. Word of warning: the documentation is out of date and doesn't include a few new additions, and could drop a few. Due to that, I decided to try and figure out all of the actual link-time(?) dependencies of the application and its tooling. The following script is what I've come up with. > > https://gitlab.com/snippets/1798656 > > I didn't get any warning while running the application itself, but I also didn't do a fully comprehensive test run (there's only so much of Maya one person can know, and you know, time is a thing). How I got the list of all binary executables in the installation: > > find /usr/autodesk/{maya2019,bifrost} -type f -executable -exec file -i '{}' \; | grep 'x-executable; charset=binary' | sed 's|:.*||' > > I did a similar thing for all of the shared objects (*.so) in those parent directories, recursively. I then whipped up this Python script for running ldd on everything to see what was missing (using two functions probably wasn't necessary). All that was left was any small discrepancy that Maya spat at me when launching from the console, which was two, I think. > > https://gitlab.com/snippets/1800558 > > This was all done starting from a minimal CentOS 7.6 docker image. Just posting this here to see if anyone wanted to verify this. There's a fair amount of small-time extras in here that could probably be removed, but I wanted to be as thorough as possible. > > Also, does anyone know if openssl098e is necessary anymore? Maya seems more than happy to link (at install time, and this doesn't change) it's internal libssl.so.6 to libssl.so.10 from openssl if a system-level .so.6 doesn't exist. > > Cheers, > Mike > > To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

0 Plus One's     0 Comments