New: Sparrow.framework - drag & drop deployment

Shilo

Alright, I can't figure this out no matter what I try, and need help please.

My projects now use the "Sparrow.framework" instead of "libSparrow.a" and everything builds fine. My issue is that modifying Sparrow and re-compiling "Sparrow.framework" doesn't reflect any of my changes.

For example, lets say I add a new class method to SPUtils. Here are my steps after my changes:

I click "Product > Archive" and wait for it to successfully complete.
Then I navigate to the appropriate "build/" directory and make sure the "Sparrow.framework" file/folder exists and was changed.
After that, I make sure my own project is properly linked to "Sparrow.framework".
Upon attempting to build my own project which attempted to access this "new class method in SPUtils" it will throw a build error saying that the method does not exist.

Upon investigation, the "Sparrow.framework" directory has the correct SPUtils.h file, but I assume the .m isn't being recompiled or something. Inside the "Sparrow.xcodeproj" (within my own project), it shows my header and implementation changes correctly.

I even did extra steps such as:

Deleted "build/Sparrow.framework" before clicking "Product > Archive".
Removed the reference of "Sparrow.framework" from my project and re-linked it.

I have also tried many other changes, such as modifying methods that already exist in Sparrow.

Also, is there a way of displaying NSLogs from source files inside of Sparrow, when running from my own project? I assume this is no longer possible because Sparrow is being pre-compiled before hand, right?

Alternative, I also tried just linking the "libSparrow.a" file instead of "Sparrow.framework" to avoid using the compiled version, but I get tons of errors with category methods on Sparrow objects that I have never got before. (Disclaimer: I am using a little trick to expose Sparrow instance variables) So this isn't an option at the moment.

I noticed that the "Sparrow.framework" scheme no longer exists to build and create the compiled framework, but I assume "Product > Archive" is the new alternative, right?

Thank you very much.

@off-topic
Another question:
Will leaving -ObjC and -all_load have any negative effect on Sparrow and Sparrow related categories, now that those flags are no longer needed?

Daniel

Hey Shilo,
sorry to hear about this troubles! I hope you haven't lost too much time on this. 🙁

In your sample, you talk about adding a new class. When you do that, there is a new step involved: that class has to be marked as being publicly accessible (compared to just being available within the framework).

To do that, you have to change the "Target Membership" of the new ".h" file in Xcode to "Public", as shown here:

That should do the trick! With that out of the way, everything should work after recompiling; and you can use NSLog in Sparrow just like before (e.g. the audio methods still log something out).

Please try it out, and let me know if it helps!

That said: you can still use Sparrow just like before, via SPARROW_SRC source tree variable and having it as a subproject inside Xcode. I'm doing all the development like this! It's much faster, because Archiving is an extra step that takes quite a lot of time. You don't want that when you constantly make changes.

The new ".framework" usage is just meant for stable releases. Developers who don't want to mess around with Sparrow should be able to add it to a project quickly, without much set-up time.

Power users like you and me will probably keep the sub-project setup.

Re @off-topic:
No, that shouldn't have any negative effect! At least I haven't heard of any problems in that respect!

Shilo

Hello Daniel,

Quote from Daniel:

In your sample, you talk about adding a new class.

Quote from Shilo:

For example, lets say I add a new class method to SPUtils. Here are my steps after my changes:

I'm afraid you misunderstood me. I said "class method", not "class". 🙂

Quote from Daniel:

To do that, you have to change the "Target Membership" of the new ".h" file in Xcode to "Public", as shown here:

I know how to specify a class header as "Public", but I never knew you can do it from the "Properties Pane". Thank you for this tip! Unfortunately, that doesn't help my issue.

Quote from Daniel:

and you can use NSLog in Sparrow just like before (e.g. the audio methods still log something out).

I am assuming my NSLogs are not showing up because the archiving/compiling of the framework isn't working 100% correctly, and it may not be re-compiling the implementation files. Any changes I make to Sparrow don't appear after archiving and running my project, whether it is a new class, new method, edited method, or NSLog.

I even downloaded the newest bleeding-edge version of Sparrow that recently got rid of "setCachingEnabled:" method, I archived it, added "Sparrow.framework" to my project, and it still seemed to be using an older version of Sparrow.

These issues aside, I do agree that using the compiled version of Sparrow is not the best route, if I plan on modifying code. So I forked Sparrow and made instance variables protected/public instead of hidden, made a header file public, and added a category directly to Sparrow. This has solved all my issues, and I am now running Sparrow from "libSparrow.a".

Also, it seems your new SPTexture caching method is no longer leaking, so I thank you!

Daniel

I'm afraid you misunderstood me. I said "class method", not "class". 🙂

Damn, sorry, I really misread this. Then what you describe is super-odd ...!
I'll take another look at it and will report back soon.

Daniel

So, I just tried that, in worked perfectly fine for me. 😐

I created a project that uses "Sparrow.framework".
I added a new method to "SPUtils" that logs a message.
I archived Sparrow.
I called that method from the project. Code-completion suggested it correctly to me, and the log appeared in the console.

There *must* be something wrong in your setup! Could you try to repeat the experiment with a brand new project? Please use this tutorial to do that.

If it happens there, as well then ... well ... then I'm out of ideas, to be honest. But one step after the other! 😉

Daniel

BTW, I even deleted Sparrow from my disk and pulled it again, to be sure there's nothing special in my setup.

« Previous Page