Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARC Compatibility #42

Merged
merged 1 commit into from
Jul 26, 2011
Merged

ARC Compatibility #42

merged 1 commit into from
Jul 26, 2011

Conversation

wezm
Copy link
Contributor

@wezm wezm commented Jul 26, 2011

I've successfully got Kiwi working in an ARC using iOS project. I had to make this one small code change to get the code building. Instead of adding the non-ARC compatible files to my project I set up my test target to link against the the Kiwi static library. This involved:

  1. Add libKiwi.a as a dependency of my test target
  2. Add libKiwi.a to the linked frameworks of the test target
  3. Add -ObjC -force_load ${BUILT_PRODUCTS_DIR}/libKiwi.a to the Other Linker Flags project setting of the test target

After this the specs run.

lukeredpath added a commit that referenced this pull request Jul 26, 2011
@lukeredpath lukeredpath merged commit 5452f14 into kiwi-bdd:master Jul 26, 2011
@ma11hew28
Copy link
Contributor

Sweet. This worked for me as well.

  • In Terminal, I added Kiwi as a Git submodule:

    git submodule add https://github.com/allending/Kiwi.git Vendor/Kiwi
    git submodule update --init
    git commit -am 'Add Kiwi as a submodule & update --init.'
    
  • In Xcode, I created the Vendor group and added the Kiwi.xcodeproj file (from the submodule repo) to that group, leaving all targets unchecked.

  • I followed the three steps above, but for target dependencies, for me, it was Kiwi (Kiwi) not libKiwi.a.

  • I also had to add Vendor/Kiwi to the tests target Header Search Paths. Then, at the top of specs files:

    #include <Kiwi/Kiwi.h>
    
  • I also put the above in ProjectNameSpecs-Prefix.pch (which I created and set as ProjectNameSpecs' Prefix Header (in Build Settings)). E.g.:

    // ProjectNameSpecs-Prefix.pch
    #include <Kiwi/Kiwi.h>
    #include "ProjectName-Prefix.pch"
    

@dimsumthinking
Copy link

I would recommend that the directions for how to make this work be carefully written up for Xcode newbies and other folks who've never had to take this step before and added to the Kiwi docs.

One of the things that makes Kiwi so attractive is it's ease of set-up. These additional steps aren't much more difficult but the path to making them work must be given with painfully clear detail. IMO.

@allending
Copy link
Member

Agreed, apologize for the slacking. New job, new country, busy, yeah excuses.

I think it's finally time to move all the docs to Github. Would love any help but feedback on what docs are essential is easier and just as valuable. I don't have that much time and would rather post up useful information instead burning out on a laundry list of things most people will never be interested in.

https://github.com/allending/Kiwi/wiki

@MattesGroeger
Copy link
Contributor

By the way, I moved all docs over to the wiki. Because of the markdown, I had to put some ugly spaces between some square brakets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants