I've just spent about two hours getting this to compile on macOS Sonoma on an M1 MacBook Pro.
A few things I had to change:
brew install poppler-qt5 rather than just poppler
Had to edit the qmake file in pdf_extract to manually add the correct include directories, as well as bump the c++ version up to CONFIG += c++17 otherwise I was getting compilation errors with the current brew poppler-qt5 bottle.
Had to edit the qmake file in kicad to add QT += core.
By default, the built app crashes with macdeployqt uconfig_gui.app -libpath=./ because of the requirement for code signing.
I had to self-sign with sudo codesign -s - --deep --force --verbose uconfig_gui.app.
Then, the poppler dylib wasn't included by default, so I had to manually copy it in with cp /opt/homebrew/Cellar/poppler-qt5/24.11.0/lib/libpoppler.143.dylib uconfig_gui.app/Contents/Frameworks.
I would try again on a fresh Mac VM and submit a PR, but I'm in the middle of a schematic capture deadline - hope this gives some kind of guidance to someone else with the same issue!
I've just spent about two hours getting this to compile on macOS Sonoma on an M1 MacBook Pro.
A few things I had to change:
brew install poppler-qt5rather than justpopplerHad to edit the qmake file in
pdf_extractto manually add the correct include directories, as well as bump the c++ version up toCONFIG += c++17otherwise I was getting compilation errors with the current brewpoppler-qt5bottle.Had to edit the qmake file in
kicadto addQT += core.By default, the built app crashes with
macdeployqt uconfig_gui.app -libpath=./because of the requirement for code signing.I had to self-sign with
sudo codesign -s - --deep --force --verbose uconfig_gui.app.Then, the poppler dylib wasn't included by default, so I had to manually copy it in with
cp /opt/homebrew/Cellar/poppler-qt5/24.11.0/lib/libpoppler.143.dylib uconfig_gui.app/Contents/Frameworks.I would try again on a fresh Mac VM and submit a PR, but I'm in the middle of a schematic capture deadline - hope this gives some kind of guidance to someone else with the same issue!