Re:Filament (3D renderer from Google) for the Web
by izacus on Saturday November 03, 2018 @07:44AM
(#18369756)
All of what you listed is build tooling, not something that gets linked into end binary. It's pretty standard fare for C++ projects.
[ Parent
| on HN ]
Re:Filament (3D renderer from Google) for the Web
by TekMol on Saturday November 03, 2018 @08:08AM
(#18369823)
That's a complex standard. I would think 'g++ theproggy.cpp' should be enough.
Re:Filament (3D renderer from Google) for the Web
by flohofwoe on Saturday November 03, 2018 @08:13AM
(#18369844)
It's a cross-platform project which needs to access system APIs. For instance on Linux you need to install a number of required development packages for this. Similar details on other platforms.
Re:Filament (3D renderer from Google) for the Web
by TekMol on Saturday November 03, 2018 @11:58AM
(#18370814)
Ok, but I am only interested in the web version.
Re:Filament (3D renderer from Google) for the Web
by slavik81 on Saturday November 03, 2018 @09:40AM
(#18370111)
The sample app loads HDR images, compiles and optimizes GLSL shaders, loads PNG textures, processes mesh data, has GUI controls, and more. You didn't even list half the dependencies—they're vendored under "third_party/"
Re:Filament (3D renderer from Google) for the Web
by RomainGuy on Monday November 05, 2018 @07:55PM
(#18387441)
The engine itself only has two external dependencies: STL (internal use only, not part of the APIs) and robin-map. The (optional) Vulkan backend adds a third one: vkmemalloc.
The host tools (material compiler, etc.) do have more dependencies indeed.