- Remove changes in main.m, turns out we cannot actually catch it here. Tried some other methods, however none worked. - Change dupeguru submodule to a more "known" commit that did not have partial work in it. NOTE: Issue with picture mode appears to be from python 3.8+ changing to use `spawn` as the method for multiprocessing. While this is most likely better we currently have issues when application is run normally (running from run.py does not have issues). I am manually going to change to `fork` instead since other methods did not work. This needs to be done on line 20 of matchblock.py. Either need to find a workaround or make a way to detect we are running with cocoa vs. qt to make this switch. Just on macos would affect qt build which does not need this change.
|3 months ago|
|cocoa||3 months ago|
|cocoalib||3 months ago|
|dupeGuru.xcodeproj||3 months ago|
|dupeguru @ bf7d720126||3 months ago|
|.gitignore||3 months ago|
|.gitmodules||3 months ago|
|Makefile||3 months ago|
|README.md||3 months ago|
|build.py||3 months ago|
|package.py||3 months ago|
|requirements.txt||4 years ago|
|run.py||4 years ago|
This is the Cocoa UI for dupeGuru. This code was previously directly in the main repo, but since I’m not planning on supporting MacOS myself any longer, I’m splitting it out.
Also, to make the job easier on a would-be maintainer for the Cocoa UI of dupeGuru, I’m planning on restoring the XCode/XIB version of the UI from the grave.
My Mac Mini is already a couple of years old and is likely to be my last Apple purchase. When it dies, I will be unable maintain the OS X version of moneyGuru. I’ve already stopped paying for the Mac Developer membership so I can’t sign the apps anymore (in the “official way” I mean. The download is still PGP signed) If you’re a Mac developer and are interested in taking this task, don’t hesitate to let me know.
You can build the app with
$ make $ make run
pyenv is a popular way to manage multiple python versions. However, be aware that dupeGuru
will not compile with a pyenv’s python unless it’s been built with
--enable-framework. You can do
$ env PYTHON_CONFIGURE_OPTS="--enable-framework" pyenv install 3.4.3