> On 20 May 2026, at 15:11, FZiegler <[email protected]> wrote: > >> On May 20, 2026, at 4:50 AM, Christiaan Hofman <[email protected]> wrote: >> >> >> You should not have to do all this. > > I agree, I shouldn’t have to :-) I’ve since found that I *could* have build > in Xcode, had I only known what a “Scheme” even is and that you must set it > to “BibDesk” in a menu that unrolls by clicking where it just said “relaunch > >”: > > <Xcode.png> > > Not very discoverable...😇 *Then* Product > Build does at least *something* -- > i.e., complains about those missing frameworks. >
That’s part of how Xcode works. Xcode is indeed a rather complex app, not entry level. >> You probably did not properly install the sources, the externals are >> missing. Did you get the sources using svn? It certainly used to be that >> externals were also included when you do an svn checkout. > > Yes, I wished to avoid installing svn (which unlike git is not part of the > developer tools), so I tried getting a tarball by clicking “Download > Snapshot” at https://sourceforge.net/p/bibdesk/svn/HEAD/tree/trunk/. Then no, > it doesn’t include those frameworks nor say how/where to find them. > Indeed, a snapshot from the website will not give you the externals, the sourceforge source web services also don’t reference the externals at all. You can of course get the externals yourself separately from that website, but you need to know which one and where to put them. There are 3 externals (as you noted): QuickLook-BibDesk, vendorsrc, and SkimNotes. You can get the first two also as a tarball, look in the trunk (the latter has a different name there). The SkimNotes can be downloaded from the skim-app sources. >> You should not comment out. The problem is not so much that the code is >> wrong, but the compiler complains too much, as it does not know the class >> that is returned. You can fix this by typing the return value so the >> compiler knows: >> >> skIndex = [(BDSKPublicationArray *)[[[self selectedGroups] firstObject] >> publications] indexForField:field]; >> >> I’ve already changed that in the source. > > Perfect, thanks !! > > (But Xcode Product > Build produces a Debug build; what’s the invocation to > get a Release build instead?) You can get a release build using Product > Build For > Profiling (Shift-Cmd-I). You will have to look a bit for the product though, as Products always points to the debug build (go up one folder to Products, and then go into the Release folder). >> On May 20, 2026, at 8:57 AM, Christiaan Hofman <[email protected]> wrote: >> >> Also, it probably won’t build from Xcode 26 because the deployment target is >> 10.13 for backwards compatibility. And unfortunately that requires older >> Xcode versions to build. Perhaps you could set the MACOSX_DEPLOYMENT_TARGET >> in the xcconfig files of the various projects to a version higher than >> 10.13. > > Well, it did build for me, and seems to run fine. Fingers crossed. > That’s good, so Apple did not make any more trouble then. > Francois Christiaan
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
