Which files should be included when sharing a Tizen native app project via Git?

Original Created Oct 12, 2017 | Regeneration Apr 22, 2026

Question

I'm planning to share my Tizen native application on a Git server to collaborate across multiple computers. Currently, I'm including these files and folders:

inc
res
shared
src (excluding the managed folder)
tizen-manifest.xml
shared/res

Are these sufficient? I've noticed other hidden files like .cproject, .exportMap, .tproject, etc. Should any of these be included? What about project_def.prop?

Answer

Problem Understanding

The user wants to know which files should be version-controlled when sharing a Tizen native application project via Git, particularly regarding:

Essential project files
Hidden configuration files
UI Builder-generated files (managed folder)

Solution Methods

Use .gitignore: Create a .gitignore file to automatically exclude unnecessary files. Here's a recommended pattern:

/.cproject
/.checkers
/.rds_delta
/.sdk_delta.info
/.sign
/crash-info/
/res/res.xml
/Debug/
/Release/
/lib/*.so*
/lib/*.a
/medialibrary/
*.tmp
*~
res/edje/*.edj

Managed Folder Handling: The managed folder contains UI Builder-generated files. While it can be regenerated, including it in version control ensures all team members have consistent UI configurations.
Project Configuration Files: Include essential configuration files like tizen-manifest.xml and project_def.prop as they contain critical project settings.

Code Examples

For ignoring the managed folder (if desired):

/managed/*

Additional Tips

For more detailed .gitignore recommendations, refer to this StackOverflow thread: Tizen Studio Project .gitignore
Test by deleting the managed folder locally to verify if your team members can regenerate it successfully
When in doubt, err on the side of including files rather than excluding them