Yeah, I’m building on an old system running Mavericks, and I don’t even have
10.13 installed. Weak import requires the symbol to exist on the build system,
and prevents crashes if it doesn’t exist at runtime. I’d say just make
__FVCGImageGetBytePtr return NULL on 10.13, if it’s causing that sort of
problem. There’s a fallback code path that doesn’t use SPI.
From: Christiaan Hofman [mailto:cmhof...@gmail.com]
Sent: Thursday, December 14, 2017 2:38 AM
To: About BibDesk development. <bibdesk-develop@lists.sourceforge.net>
Subject: Re: [Bibdesk-develop] nightly build problem
It looks like you use an older system to build. Is it possible to use a
function that exists on newer systems but not on the build system? I thought
the weak import attribute would do it. The problem is that the private function
you were using gives warnings at runtimes and leaks on 10.13.
Christiaan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bibdesk-develop mailing list
Bibdesk-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
