Comments on: How to make an iPhone static library – part 2 http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/ Internet Gaming, Computer Games, Technology, MMO, and Web 2.0 Sun, 05 Sep 2010 20:30:54 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: adam http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-5954 adam Wed, 12 May 2010 13:59:40 +0000 http://t-machine.org/?p=683#comment-5954 @Corin None of our current projects are OS 4, and we're still using Xcode 3.1 for backwards compaitilbity, so I don't know if it's fixed. However, I think one aspect of this is definitely going to be easier. With iPad, Apple "un-deleted" the support for universal binaries (which IIRC I originally used for doing static libraries), so you should at least be able to make a single unified lib again (but this is IIRC). @Corin

None of our current projects are OS 4, and we’re still using Xcode 3.1 for backwards compaitilbity, so I don’t know if it’s fixed.

However, I think one aspect of this is definitely going to be easier. With iPad, Apple “un-deleted” the support for universal binaries (which IIRC I originally used for doing static libraries), so you should at least be able to make a single unified lib again (but this is IIRC).

]]> By: Corin http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-5953 Corin Wed, 12 May 2010 13:47:47 +0000 http://t-machine.org/?p=683#comment-5953 What about iPhone OS 4.0 and Xcode 3.2.3? Do the same bug still exist? What about iPhone OS 4.0 and Xcode 3.2.3? Do the same bug still exist?

]]> By: edgecrush3r http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-4296 edgecrush3r Fri, 12 Feb 2010 01:06:47 +0000 http://t-machine.org/?p=683#comment-4296 Nice article.. I completely agree with you on the arrogant Apple documents why you shouldnt use static opposed to dynamic libraries. For those who are ignorant to see the difference, static libraries has its uses and dynamic libraries are sometimes more hassle than its worth. If you dont think so, try compiling and maintaining more complex environments and you will find yourself recursively compiling just to get that one daemon up and running. I am not saying i favor static compilations, but they do have their uses and anyone who doesnt think so will get their head stuck in the near future. Nice article.. I completely agree with you on the arrogant Apple documents why you shouldnt use static opposed to dynamic libraries. For those who are ignorant to see the difference, static libraries has its uses and dynamic libraries are sometimes more hassle than its worth. If you dont think so, try compiling and maintaining more complex environments and you will find yourself recursively compiling just to get that one daemon up and running. I am not saying i favor static compilations, but they do have their uses and anyone who doesnt think so will get their head stuck in the near future.

]]> By: Victor Costan http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-3521 Victor Costan Mon, 07 Dec 2009 06:02:37 +0000 http://t-machine.org/?p=683#comment-3521 I figured out a way to put together the code for the simulator and the device, in one file. http://blog.costan.us/2009/12/fat-iphone-static-libraries-device-and.html I figured out a way to put together the code for the simulator and the device, in one file.

http://blog.costan.us/2009/12/fat-iphone-static-libraries-device-and.html

]]> By: adam http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-3270 adam Fri, 30 Oct 2009 17:14:24 +0000 http://t-machine.org/?p=683#comment-3270 @fluxon Thanks for commenting. Please read Part 1 of the article (link at the top). This should explain all the ways in which the StormyProds blog post is - effectively - useless here. Sorry. @fluxon

Thanks for commenting. Please read Part 1 of the article (link at the top). This should explain all the ways in which the StormyProds blog post is – effectively – useless here.

Sorry.

]]> By: fluxon http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-3269 fluxon Fri, 30 Oct 2009 16:52:19 +0000 http://t-machine.org/?p=683#comment-3269 this site explains it really nicely with no hassle. http://blog.stormyprods.com/2008/11/using-static-libraries-with-iphone-sdk.html this site explains it really nicely with no hassle.
http://blog.stormyprods.com/2008/11/using-static-libraries-with-iphone-sdk.html

]]> By: T=Machine » How to make an iPhone static library – part 2 | IPhoneMate http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-3213 T=Machine » How to make an iPhone static library – part 2 | IPhoneMate Tue, 20 Oct 2009 20:31:15 +0000 http://t-machine.org/?p=683#comment-3213 [...] this link: T=Machine » How to make an iPhone static library – part 2 Share and [...] [...] this link: T=Machine » How to make an iPhone static library – part 2 Share and [...]

]]> By: adam http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-3205 adam Wed, 14 Oct 2009 10:34:09 +0000 http://t-machine.org/?p=683#comment-3205 Thanks for the comment. I'm sorry that you misread my post, I'll try to make those bits clearer here. I agree entirely that "there is no contradiction" - I never claimed there was. Rather, I pointed out that IN PLACE OF documentation, Apple currently has (or at least "had" when I was reading it) circular references; the Xcode docs for static libs are "missing", and instead there's one of their little notes saying "this is missing because you shouldn't be using static libs any more; click this link to go to the dynamic libs docs" (or something to that effect). I'll skip over the Obj-C-is-a-hack thing - that distraction was my fault, a throwaway comment referring to the language itself, which isn't really at issue here. W.r.t. the linker, I didn't make it clear enough, but my complaints about linking are really only about Xcode's failure to support this in a neat fashion. A proprietary IDE designed around a specific language shouldn't require you to manually add "custom" linker flags for something that is a basic, normal use-case. After all that ... sadly, you had nothing to say about the core problem: how do you ( how are you supposed to ) setup, build, and link static libs on iPhone? I would greatly appreciate it if you would enlighten the rest of us on that problem too. Thanks! Thanks for the comment.

I’m sorry that you misread my post, I’ll try to make those bits clearer here.

I agree entirely that “there is no contradiction” – I never claimed there was. Rather, I pointed out that IN PLACE OF documentation, Apple currently has (or at least “had” when I was reading it) circular references; the Xcode docs for static libs are “missing”, and instead there’s one of their little notes saying “this is missing because you shouldn’t be using static libs any more; click this link to go to the dynamic libs docs” (or something to that effect).

I’ll skip over the Obj-C-is-a-hack thing – that distraction was my fault, a throwaway comment referring to the language itself, which isn’t really at issue here.

W.r.t. the linker, I didn’t make it clear enough, but my complaints about linking are really only about Xcode’s failure to support this in a neat fashion. A proprietary IDE designed around a specific language shouldn’t require you to manually add “custom” linker flags for something that is a basic, normal use-case.

After all that … sadly, you had nothing to say about the core problem: how do you ( how are you supposed to ) setup, build, and link static libs on iPhone?

I would greatly appreciate it if you would enlighten the rest of us on that problem too. Thanks!

]]> By: WTF http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-3201 WTF Wed, 14 Oct 2009 05:51:18 +0000 http://t-machine.org/?p=683#comment-3201 This is one of the most ridiculous things I have ever read. You simply don't know how to use Xcode properly. There is nothing inherently wrong with that, but the fact that you can't/don't know how to use the product correctly does not mean that it has any bugs. Also Objective-C isn't hacky, and linker flags are there for specific cases. In the case of static libraries, object code is not linked into the executable unless it is referenced. In Objective-C, a lot of constructs like categories are bound at launch by the Objective-C runtime, which makes it very dynamic. However, to the compiler, this just looks like unreferenced object code, so the compiler will omit it. When the runtime attempts to execute code that is not actually linked, of course your executable aborts. The -ObjC flag just tells the linker to copy all the executable object code into the final project regardless of whether it is referenced at link time (so that categories and other such dynamically loaded constructs can be used). Also Apple says to use dynamic linking for Mac OS X. There is no contradiction, iPhone OS != Mac OS X. You should continue to build and link dynamically on Mac OS X, unless there is a compelling reason not to (for instance, embedding the lua runtime into some server or application). What kind of programmer did you say you were again? This is one of the most ridiculous things I have ever read. You simply don’t know how to use Xcode properly. There is nothing inherently wrong with that, but the fact that you can’t/don’t know how to use the product correctly does not mean that it has any bugs. Also Objective-C isn’t hacky, and linker flags are there for specific cases. In the case of static libraries, object code is not linked into the executable unless it is referenced. In Objective-C, a lot of constructs like categories are bound at launch by the Objective-C runtime, which makes it very dynamic. However, to the compiler, this just looks like unreferenced object code, so the compiler will omit it. When the runtime attempts to execute code that is not actually linked, of course your executable aborts. The -ObjC flag just tells the linker to copy all the executable object code into the final project regardless of whether it is referenced at link time (so that categories and other such dynamically loaded constructs can be used).

Also Apple says to use dynamic linking for Mac OS X. There is no contradiction, iPhone OS != Mac OS X. You should continue to build and link dynamically on Mac OS X, unless there is a compelling reason not to (for instance, embedding the lua runtime into some server or application). What kind of programmer did you say you were again?

]]> By: T=Machine » How to make an iPhone static library – part 1 http://t-machine.org/index.php/2009/10/14/how-to-make-an-iphone-static-library-part-2/comment-page-1/#comment-3198 T=Machine » How to make an iPhone static library – part 1 Wed, 14 Oct 2009 00:08:42 +0000 http://t-machine.org/?p=683#comment-3198 [...] How to make an iPhone static library – part 2 (No Ratings Yet)  Loading ... Filed under : iphone, programming [...] [...] How to make an iPhone static library – part 2 (No Ratings Yet)  Loading … Filed under : iphone, programming [...]

]]>