We work with a lot of remote teams and are finding a way to distribute our plugins in a cross-platform manner keeping in mind the TK’s agnostic approach to code delivery while ensuring code obfuscation.
- Windows 10
- CentOS 7
- Core v0.19.3
What we are hoping to achieve:
- Compile all our hooks/python files into *.so and *.pyd files
- Bundle the compiled code in our config, which is using a centralized setup
- We are locally versioning the centralized config on git
- On updates to master a CI job will trigger to traverse the tree and compile relevant python files into platform specific binaries
- The compiled version of the config is then made available to remote teams as a zip which can be downloaded and extracted to the appropriate location
- Will it be alright to keep both the *.pyd and *.so files in the same location, setting aside the duplication of data which would add to the bundle size would there be any other concerns by doing this?
- Would it be better to break apart the binaries by os and have a wrapper script which would then be able to import the appropriate path based on the running?
We are just trying to understand the recommended approach to this.