__WXGTK20__ GTK+ 2.0 or higher
You wish to use wxGTK version 3.0 instead of 2.8, correct?
What is the full path to 'fontconfig/fontconfig.h'?
Edit: Found what may be the upstream source of wxPdfDocument https://utelle.github.io/wxpdfdoc/ (https://utelle.github.io/wxpdfdoc/)
It will be good if you can post the full build log.The thing you've posted is not enough to resolve the problem.
CB builds fine on Linux and I think wxpdfdocument builds fine on OSX, too (which is closer to a BSD than linux).
Assuming that C::B creates a build log, where would I find it? I ask because the majority of the build info seems to be too big for the terminal to contain it all.
make > build.log
The log is huge, so I had to split it up.Better would be to zip, gz or 7zip it and upload it here.
I don't see the error messages there...
make > build.log 2> error.log
make > build.log 2>&1
I don't see the error messages there...
What version are you building?
Why is fontconfig in /usr/local/? On most systems it is not in the default search paths and it is possible that we ignore --includedir=/usr/local/include/.
I don't see the error messages there...
In the third pastebin, you should see "src/pdffontmanager.cpp:51:12: fatal error: 'fontconfig/fontconfig.h' file not found".QuoteWhat version are you building?
17.XXQuoteWhy is fontconfig in /usr/local/? On most systems it is not in the default search paths and it is possible that we ignore --includedir=/usr/local/include/.
GhostBSD is a derivative of FreeBSD. I can only assume that it's in "/usr/local/include" because that's where FreeBSD puts it. However, you know what they say about assumptions. Why ignore "--includedir" while publishing it as a configure option?
Better would be to zip, gz or 7zip it and upload it here.
if soyou have to modify your command and store also the error stream:Codeor put all in one filemake > build.log 2> error.log
Codemake > build.log 2>&1
Thank you for your collaboration!