[futurebasic] Re: [FB] Incorporating External Frameworks into an FB Project

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : May 2013 : Group Archive : Group : All Groups

From: Robert Covington <artlythere@...>
Date: Sat, 4 May 2013 13:31:18 -0400
On May 4, 2013, at 11:43 AM, Ken Shmidheiser <kshmidheiser@...> wrote:

> Robert wrote:
> 
>> Nice find for a problem, Ken. :) Intractable. :)
> 
> 
> (W)racked my brain on this one too. Ended up trying to build the project in Xcode and use the framework Xcode built-- that framework did look similar in structure to the ones in /Library/Frameworks/ with aliases to the actual files-- only to discover that FB (actually clang) choked when it came across a missing header file that Xcode did not, for whatever reason, copy.
> 
> As a last resort, I copied all the ZXingObjC files into one folder (no subfolders-- all files on the same level) and tried linking to that.
> 
> Epic fail to date.
> 
> Definite time for R.P. stroke of genius.
> 
> Sigh.
> 
> Ken 

I was thinking he'd have the answer as well. He was a laser, and I am more a fog. We made a good debugging team because I was good at locating a candidate in the blur, then he'd go in and show the exact outlines.

Maybe the following observation is helpful.

What I notice that is different from this framework from the others I use is that there is no TV'ish icon for the Unix executable with the ZXingObjC name, nor the alias for same, as there probably should be. The one there is different… And maybe is because the target for the framework itself (icon in project) looks to be a Cocoa Library, not a Cocoa Framework per se.

So, I added a new target to ZXingObjC, to recompose the project into a build-able usual Cocoa framework using the files in the project but my attempts to add the existing files to the target were unsuccessful, thanks to how overcomplicated Xcode makes doing any anything. :(
 
There's something not building correctly with the framework is my guess, or the target we think is the framework is actually being made as a library, not a framework (if that matters) and it is missing file and usual appearances, such being maybe a clue. So when Clang seeks to load the framework as FBtoC perhaps likes to think of one, it cannot find anything 'built' to load as the code object? Thus giving the not found error.

Shot in the dark.

rc