KhronosGroup / KhronosGroup/OpenCOLLADA

Can OpenCollada be split into separate modules?

Open
#468 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
679
Forks
260
PR merge metrics
No merged PRs in 30d

Description

Hi;
First: please apologize if i am asking at the wrong place, but it appears to me like here is where i can get the answers :)

The Collada libraries make up about 30-40 MByte of the Blender distribution. The entire Blender distribution is about 100 MBytes in size. So there is a desire to reduce the size of the Collada libraries in the blender shipping.

Since Blender does not use all of Collada's possibilities, we just discussed in Blender IRC if it is possible to split up the OpenCollada libraries into smaller parts, so that the total size of the Collada module can become significantly smaller.

Is this doable? Is anybody working on this? or... where should we start digging? I guess it is somewhere in the area where the library sources are generated... right? Is there any documentation about how the libraries are generated? anything that helps getting to speed with this quickly?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how the OpenCOLLADA library sources are generated and looking for documentation about that process; the issue names no files or tests. Define module boundaries around the functionality Blender uses, then verify that the resulting Collada libraries are materially smaller in the shipped distribution.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.