tag:blogger.com,1999:blog-6848022.post4549120905568099687..comments2020-05-04T05:03:48.229-04:00Comments on it's a radish: HOWTO: Wrap a libpurple plugin for AdiumNoahhttp://www.blogger.com/profile/12638229035633367208noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6848022.post-8388288778700913432010-12-03T13:13:58.318-05:002010-12-03T13:13:58.318-05:00Just curious, but how would I go about doing this ...Just curious, but how would I go about doing this with Xcode 4? Many of the steps have changed, and it's quite difficult to puzzle through. Thanks!Jeff Bhttps://www.blogger.com/profile/11647828767762256496noreply@blogger.comtag:blogger.com,1999:blog-6848022.post-59317777888853448452008-09-25T11:45:00.000-04:002008-09-25T11:45:00.000-04:00@evan - Great tip, thanks a lot. I'll have to try...@evan - Great tip, thanks a lot. I'll have to try it out.Noahhttps://www.blogger.com/profile/12638229035633367208noreply@blogger.comtag:blogger.com,1999:blog-6848022.post-22178897268629876562008-09-18T07:48:00.000-04:002008-09-18T07:48:00.000-04:00Great article!One comment: Rather than linking aga...Great article!<BR/><BR/>One comment: Rather than linking against all those frameworks, a less fragile solution is to use the following (assuming you put all the frameworks in Frameworks):<BR/><BR/>OTHER_LDFLAGS = -undefined dynamic_lookup<BR/>FRAMEWORK_SEARCH_PATHS = $(inherited) "$(SRCROOT)/Frameworks"<BR/>HEADER_SEARCH_PATHS = "$SRCROOT/Frameworks/libglib.framework/Headers"<BR/><BR/>(Set these in the appropriate places in the target's Build settings).<BR/><BR/>You can then remove the shell script which modifies the linker path, and all you actually need are the appropriate headers, not the framework binaries themselves.Evan Schoenberghttps://www.blogger.com/profile/13540202511918021011noreply@blogger.com