「利用者:Juicyfruit/Building For Linux」の版間の差分
細 (1版 をインポートしました) |
|
(相違点なし)
|
2018年6月29日 (金) 04:39時点における最新版
This page has been marked for development documentation changes.
Feel free to comment on the talk page.
Feel free to comment on the talk page.
WIP REASON:
WIP documentation and development |
目次
Building a reloactable Blender 2.5x on Linux
Page is not Done !!
Asumptions
- Build environment is either ubuntu or Debian based
- We will create a seperate build environment
- GCC as compiler
Goals
- We want to maximize compatibility of our build
- Preofrmance and features
- Ablility to reproduce crashes and or send traces t0o developers
Preparing chroot build environment
Having a seperate environment for a build is nice as it allows us to make the whole thing more controled. We will opt for an enviroment bases on Ubuntu LTS and we choose the one before the current. In our case that means Ubuntu 8.04 LTS. Gcc 4.2 and Glibc2.7
Todo
- GCC options
- visibility
- Building a workable python 3
- Also building rpm and deb packages.
Points where we can improve the build
- remove link depencies when unused.
- Debian does this somewhere in their builds to illiminate uneeded depencies will investige
- build parts of colalda we need as shared library with all releaven visibility and spacesaving tricks then make that into a staic object and only then link it into blender. (requires more research)
- Look at KDE and QT the use this kinds of tricks extensively.
- Linking multiple versions of one module with difference optimizations
- for example render code with diffrent optimization, minimal CPU requirements in one object and choose at runtime.
- Crash reports and backtraces.
- Should be possible to keep symbols of the build and use that to make backtrace meaningfull with GDB,
- more research needed.