Closed tomas16 closed 2 months ago
Hi @tomas16
These insctructions are still valid and are still the recommended way of using a local build/fork of the project: https://mitsuba.readthedocs.io/en/latest/src/developer_guide/compiling.html
Hi @njroussel, thanks for the feedback. My goal is slightly different from simply compiling mitsuba though: I want to distribute an unreleased (but non-customized) version of mitsuba to users, as a dependency of another project.
Do I understand correctly that I should basically do a custom build and host the wheels somewhere myself? (e.g. my own pip server)
Before I embark on that: do you have a rough idea when you guys will release a next official version?
Hi @tomas16
I want to distribute an unreleased (but non-customized) version of mitsuba to users, as a dependency of another project.
Aha. In that case, the best solution would indeed be to self-host your custom built wheels.
Before I embark on that: do you have a rough idea when you guys will release a next official version?
I'd say 2-3 weeks if all goes smoothly.
Summary
Some fixes were added to mitsuba recently, and I'd like to start using them without waiting for a new official release.
Mitsuba is a dependency of a project I'm working on, so I modified its pip requirements.txt file to include
During installation, mitsuba fails to build.
This issue is probably related to: https://github.com/mitsuba-renderer/mitsuba3/issues/1147 https://github.com/mitsuba-renderer/mitsuba3/issues/1293
It would be great to fix the pip build, but I'm open to other suggestions for being able to use the latest commit of mitsuba.
System configuration
System information:
OS: macOS 14.6.1 CPU: Intel Core i-9 GPU: AMD Radeon Pro 5500M Python version: 3.11.9 LLVM version: 16 CUDA version: n/a NVidia driver: n/a
Description
Running
pip install
on the project that hasmitsuba @ git+https://github.com/mitsuba-renderer/mitsuba3.git
in its requirements file produces the following output:At the time of writing, mitsuba's main branch is at 96e0af2d.