Closed krlmlr closed 1 year ago
You need the build/
directory to build, test and install Diffuse. That's why I cd build
before running the meson command-lines. I don't really see the benefits of asking the dev to go back to the root (build/
parent) if the next command to install Diffuse requires you to go back into the same build/
directory.
Right now I would lean toward no accepting the changes, unless there is a reason I don't see?
Thanks, I reduced the PR to the part I really care about.
Since I don't have a Mac, I'll let your iron out the details here before merging. It seems there are a few questions pending:
diffuse_impl
?For the last point, could it be that a shell wrapper should be installed in something like /usr/local/bin and it would take the command-line arguments and pass it through the Mac application? (There must be a way to send arguments to a Mac application, right?)
Fixed a few remaining changes that I didn't really agreed on + some markdown refactoring to comply with the linter. Will merge once pipeline is green
At least not on my machine.
Includes a change to make the
build/
directory very explicit.