./configure says --enable-run-in-place is a deprecated flag. Elsewhere in the rebranded v2.5_branch and in the Wiki, "run-in-place" is alive and well. My latest build even introduces the abbreviated form "rip" in ./scripts/rip-environment.
I realize there is a difference between a thing or act and its label, but I hope the language can be rationalized after the stress of rebranding and releasing v2.5 has receded.
Regards,
Kent
"run in place" builds aren't going away. Rather, they are now the default when you configure linuxcnc. In older versions, it was necessary to specify --enable-run-in-place explicitly.
yse, it is the default and I use it all the time while following v2.5 developments. I was trying to put myself in the shoes of a new user to whom the Swiss-Army knife nature of the build process is daunting. In this case, though, I probably overreached. The problem is more one of consistent documentation, starting with the "Installing LinuxCNC" wiki page stating in bold font "This is why we recommend to always use --enable-run-in-place when you build your own EMC2." Granted this line is down the page from the place where it says the run-in-place method is the default but....Move this bug to the documentation column.