dreamworksanimation
No rule to make target 'Makefile'
Okay, so I figured out my last issue (needed to wipe the hard drive Moonray was installed on). Now, however, in Step 3, gmake is telling me there's no rule to make target 'Makefile'. Shouldn't the makefile already exist?
Having the exact same issue rn.
After cmake --preset container-release i get this:
CMake Error at /installs/cmake-3.23.1-linux-x86_64/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find Boost (missing: filesystem program_options) (found version "1.73.0") Call Stack (most recent call first): /installs/cmake-3.23.1-linux-x86_64/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) /installs/cmake-3.23.1-linux-x86_64/share/cmake-3.23/Modules/FindBoost.cmake:2375 (find_package_handle_standard_args) arras/arras4_core/CMakeLists.txt:26 (find_package) -- Configuring incomplete, errors occurred! See also "/build/CMakeFiles/CMakeOutput.log".
After ignoring the error and using this command cmake --build --preset container-release -- -j 64 i got this:
gmake: Makefile: No such file or directory gmake: *** No rule to make target 'Makefile'. Stop. [root@docker-desktop openmoonray]#
Also when starting the openmoonray_build container I couldn't mount “/tmp” because I don't have a shared mount (not sure how to change that)
Having the exact same issue rn. After
cmake --preset container-releasei get this:CMake Error at /installs/cmake-3.23.1-linux-x86_64/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find Boost (missing: filesystem program_options) (found version "1.73.0") Call Stack (most recent call first): /installs/cmake-3.23.1-linux-x86_64/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) /installs/cmake-3.23.1-linux-x86_64/share/cmake-3.23/Modules/FindBoost.cmake:2375 (find_package_handle_standard_args) arras/arras4_core/CMakeLists.txt:26 (find_package) -- Configuring incomplete, errors occurred! See also "/build/CMakeFiles/CMakeOutput.log".After ignoring the error and using this commandcmake --build --preset container-release -- -j 64i got this:gmake: Makefile: No such file or directory gmake: *** No rule to make target 'Makefile'. Stop. [root@docker-desktop openmoonray]#Also when starting the openmoonray_build container I couldn't mount “/tmp” because I don't have a shared mount (not sure how to change that)
Hmm, I didn't get any errors when I ran the cmake --preset command. You might need to delete everything and start over with that because Boost is usually downloaded during Step 2 with the other dependencies.
As far as the /tmp thing, I had to make my own tmp folder to clear out that error. My setup is on my I: drive, so I just created a /tmp folder at the root. It's only needed for output images seemingly, so it shouldn't brick the build process.
That makefile error though, seems to happen even when everything else is correct. Hopefully someone with more knowledge can stop in and shed some light?
Because in the documentation they called it "mounting" the tmp folder I thought there was something more to it... lol. But if I can just create the folder later like any other then that's not a problem. I'll redo the whole thing now. win11 btw.
ps. Do you know where I can find the actual paths to openmoonray_base and openmoonray_build, like where are they actually created on my drive.
Not sure where they live on your drive, but you can manage them using the 'docker' cmd, eg: docker images docker rmi <SHA>
Deleted everything, redid it with admin privileges, same exact errors as before.
Deleted everything, redid it with admin privileges, same exact errors as before.
I'd recommend making a separate issue for this so we don't clutter up this specific issue.
Not sure where they live on your drive, but you can manage them using the 'docker' cmd, eg: docker images docker rmi <SHA>
Would you happen to have a solution for my original issue (the 'rule to make target makefile not found' error)?
On which platform are you trying to build? If you’re on windows, are you using the WSL? I’d recommend adding a bit more context (OS, shell, commands run) to your descriptions so that it’s easier to understand what could be the culprit!
I suggest having a read at https://stackoverflow.com/help/minimal-reproducible-example to understand how to provide reproduction steps that can be easily followed by anyone willing to help, without having to guess the exact state of your machine.
