Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instructions for running MaterialXGraphEditor on Mac #1948

Open
hybridherbst opened this issue Jul 24, 2024 · 4 comments
Open

Instructions for running MaterialXGraphEditor on Mac #1948

hybridherbst opened this issue Jul 24, 2024 · 4 comments

Comments

@hybridherbst
Copy link
Contributor

I followed the instructions to download the pre-built MaterialX release with graph editor and viewer.

However, the instructions page does only contain info on how to build it, not how to run it. Usual start attempts with python3 bin/MaterialXGraphEditor or ./MaterialXGraphEditor fail.

How do I run the pre-built version on Mac? :)

@ld-kerley
Copy link
Contributor

I just downloaded the pre-built macOS zip - and it looks like the permissions are not set correctly on the executables.

if you open a terminal and change directory in to the root of where you unzip the archive and run

> chmod 775 bin/MaterialX*

Then I was able to run both tools.

I did also hit code security issue, and had to bypass the macOS security to actually launch the apps. I believe these binaries are not properly code signed.

@jstone-lucasfilm
Copy link
Member

We're very open to ideas on improving the automated GitHub Actions step that generates our pre-built binaries for all platforms, and here's where it's currently defined:

https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/.github/workflows/main.yml#L275

@jstone-lucasfilm
Copy link
Member

Here's some earlier discussion of this issue and a potential path forward, if anyone has the bandwidth to take this on:

#847

@hybridherbst
Copy link
Contributor Author

Thank you @ld-kerley – setting the permissions on the files to 755 fixed the issue. I think one part that could be improved is the documentation – even with that being a non-ideal state, some information on the installer being borked and the required extra steps would be good :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants