Hello!
I have a problem with setting up new project via SG Desktop. When I setup project from Mac OS, it doesn't work on Windows and pops up an error (Printscreen attached ). And vice versa. Can you help us with this?
Best regards,
Yuri
Hi again!
The problem is that firstly I made setup via Desktop. Than I made resetup of the project in command line using tank setup_project --force and edited path for Mac platform. So now on Mac I have an error like I attached in previous comment.
So as I understand I have to debug an existing error or make resetup again but somehow differently.
Waiting for your answer,
Yuri
Hi Yuri,
Sorry, you beat us to the punch here. We have a document in the works that guides you step by step through setting up a project for multiple operating systems. We'll post that once it is done.
Until that is set, could you open a ticket with us at toolkitsupport@shotgunsoftware.com with the details of your current error? We can dig into your particular setup and figure out what is needed to get it working for you on both OSX and Windows.
Just in case somebody else is reading through this post, there was a bad path in one of Yuri's files that needed to be setup for an extra OS. We will definitely post the docs here on how to do this setup once they are ready.
Hello there Yuri!
Apologies for the delay in our response. Rob has asked me to explain more of the details around the current behaviour and how to fix this issue!
What you are seeing is a bit of a wrinkle in the initial 1.0 desktop release that we are currently working on ironing out. Unfortunately, for the moment, it requires some manual config file editing to get things working.
Basically, when you create a new project with toolkit, the setup process creates tank command binaries for windows, linux and mac for your project. These tank command binaries can be used to access toolkit via a shell or terminal, and more importantly, as in your case, they are used to handle the toolkit shotgun web integration.
With our old shell based project setup process, the setup would ask the user for the paths to the different python executables that are used on each platform. These executables are needed to run the tank command and therefore the Shotgun integration.
With the Shotgun Desktop, we are finally able to delivery a ready-built python that just works out of the box. It includes PySide which makes it really easy to distribute UI applications straight to a user's desktop. So when you run the project setup using Shotgun Desktop, it typically sets up your project to use that built-in python interpreter rather than asking the user to specify it.
However, it currently only sets up the python path for the current operating system platform (it doesn't necessarily know where it would be on other machines!). This means that your project that you have created will only run on machines which a) have the Shotgun Desktop application installed and b) are running the same operating system as the machine which was used to set up the project initially.
Fortunately, there is a quick way to fix this. For each project, the python interpreter path is stored in a couple of configuration files. By editing these files, you can quickly add support for a new operating system. You can read more about this here: https://support.shotgunsoftware.com/entries/95443887
Please let us know how it goes and if you have anymore questions and we'll be happy to help!
Manne
