version control - Developing with Qooxdoo and multiple developers -

I am interested in Qualcomm as a possible web development framework. I downloaded SDK and installed it in a central location on my PC because I hope it has to be used on many projects. I used the create-application.py script to apply a new test and added all versions to my version control system.

I want to be able to collaborate with other developers on other PCs, they are likely to install SDK at a different location. Automatically generated files in Qooxdoo include the SDK path in both config.json and generator.py : if the SDK path runs, then generator Py script stops working generator.py does not appear to be too much of a problem because it looks in config.json for an update path But I'm not sure how to manage the best config.json .

I had thought about so far that there are only one option:

1. When it is removed from the VCS, it seems to be a script to automatically create it again , So it can be dangerous.
2. Add it to VCS but modify the path line for each developer and acknowledge that whenever the changes dissolve, it may need to be adjusted.
3. Change the config.json to the path and the single 'included' row which points to the second file that contains all the non-SDK path information.
4. Keeps a different, closely located copy of SDK for the relative path of SDK and for every project.

Approach 1 would be ideal if the generation script is in existence; Approach 2 is really bad; I can not approach 3 for working and 4 views are a bit confusing because it means that many copies of SDK are full of this place.

Android SDK looks very handy in this way (approach 1), with a script in its own file with SDK path which automatically generates that file as far as I I can tell, Quxdu has many other important information in config.json and the only way to automatically create that file is to create a new project.

Is there a better / recommended way to deal with this? As an alternative to using symlinks, you can overlap QOOXDOO_PATH macros on the command line:

/ P>

  ./represent.py source -MQOOXDOO_PATH: & lt; Local_path_to_qooxdoo & gt;  

(depending on the shell you are using you may have to apply some reasonable quotation to the M logic), in this way, every programmer can use its locally installed Quxdoo SDK Are there. You can also leave the QOOXDOO_PATH entry from config.json to apply it.