https://wiki.blender.jp/index.php?action=history&feed=atom&title=%E5%88%A9%E7%94%A8%E8%80%85%3AJuicyfruit%2FBuilding_For_Linux 2026-06-11T02:30:14Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Juicyfruit/Building_For_Linux&diff=100803&oldid=prev 2018-06-28T19:39:44Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 19:39時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Juicyfruit/Building_For_Linux&diff=100802&oldid=prev 2011-09-20T20:40:45Z

<p></p> <p><b>新規ページ</b></p><div>{{Warning/Working/Development|<br /> WIP documentation and development<br /> }}<br /> <br /> = Building a reloactable Blender 2.5x on Linux =<br /> <br /> == Page is not Done !! ==<br /> <br /> == Asumptions ==<br /> <br /> *Build environment is either ubuntu or Debian based<br /> *We will create a seperate build environment<br /> *GCC as compiler <br /> <br /> == Goals ==<br /> #We want to maximize compatibility of our build<br /> #Preofrmance and features<br /> #Ablility to reproduce crashes and or send traces t0o developers<br /> <br /> <br /> <br /> == Preparing chroot build environment ==<br /> <br /> Having a seperate environment for a build is nice as it allows us to make the whole thing more controled. <br /> 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<br /> <br /> === Todo ===<br /> # GCC options <br /> # visibility<br /> # Building a workable python 3 <br /> # Also building rpm and deb packages.<br /> <br /> <br /> == Points where we can improve the build ==<br /> # remove link depencies when unused.<br /> #* Debian does this somewhere in their builds to illiminate uneeded depencies will investige<br /> # 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)<br /> #*Look at KDE and QT the use this kinds of tricks extensively.<br /> # Linking multiple versions of one module with difference optimizations<br /> #*for example render code with diffrent optimization, minimal CPU requirements in one object and choose at runtime.<br /> # Crash reports and backtraces. <br /> #*Should be possible to keep symbols of the build and use that to make backtrace meaningfull with GDB, <br /> #* more research needed.</div>

wiki>Juicyfruit