static-libraries

I have a question regarding static libraries. I need to localize some text inside my library. So I created a bundle where I put my different localized files. Then, I created a function like this : NSString *MyLocalizedString(NSString* key, NSString* comment) { static NSBundle* bundle = nil; if (!bundle) { NSString* path = [[[NSBundle mainBundle] resourcePath] stringByAppendingPathComponent:@"MyStaticLib.bundle"]; bundle = [[NSBundle bundleWithPath:path] retain]; } return [bundle localizedStringForKey:key value:@"" table:nil]; } But when I use it, it always return the english localized string

I'm trying to setup a library for simulator or device building and everywhere I see explains that SDKROOT should expand to a /Developer/Platform/<>/SDKs/<>/, where <> is filled in by your project settings. Many links on the internet explain that SDKROOT will expand to a path, but the newer versions of XCode, SDKROOT expands to "iphoneos2.2.1" - which isn't nearly as helpful (for this task). Clearly enough if you look at apples documentation, the behavior changed: http://developer.apple.com/mac/library/DOCUMENTATION/DeveloperTools/Reference/XcodeBuildSettingRef/9-Revision-3.1/history.html I

I want to create a static library (actually, a framework, but I know how to do that part) that bundles up code from, among other things, another static library. However, the OBJC_CLASS exports from the original library end up as undefined symbols. For example, in Xcode 5.1.1 (using default settings/choices at every step, unless otherwise specified): Create a new "iOS Framework & Library Cocoa Touch Static Library" project named LibA. Build (for either simulator or a real device, doesn't matter). Create another new "iOS Framework & Library Cocoa Touch Static Library" project named LibB. Drag

When working on a PHP project that takes advantage of the OOP paradigm with PHP's __autoload() function, which of the following is considered the best practice for managing stand-alone functions: ( Examples provided are simplified for the sake of brevity ) tl;dr : How is stand-alone function loading commonly handled: pseudo-autoloading (via __callStatic magic for example) [ Option 1 ] abstract helper class grouped static methods [ Option 2 ] an alternative Also note, I've posted a related question regarding a parameter/reference issue with option 1 , which can be found here: __callStatic(),

I am trying to create a static library and link it on MacOS X (several versions): File foo.c : char foo[111]; File bar.c : #include <string.h> extern char foo[]; int bar(char *src) { strcpy(foo, src); return strlen(foo); } Create a library: $ cc -c foo.c bar.c $ ar r libfoobar.a foo.o bar.o ar: creating archive libfoobar.a $ ranlib libfoobar.a $ nm libfoobar.a libfoobar.a(foo.o): 000000000000006f C _foo libfoobar.a(bar.o): U ___strcpy_chk 0000000000000000 T _bar U _foo U _strlen Create a small test program: File main.c : #include <stdio.h> int bar(char *); int main(void) { printf("foobarbar =

I built universal static library with help of this template The problem that is my library libWrapper.a has size 1.3 mb??? :0 while my source code has 130 kb. How I can reduce the size of my static lib? Other strange thing - Each lib has the same size - 1.3 mb. I supposed that universal (fat) libs should have bigger size. Also make sure that you set Generate Debug Symbols to NO in your build settings. This can reduce the size of your static library by about 30%. in terminal run strip -x [youStaticlib.a] Description For dynamic shared libraries, the maximum level of stripping is usually -x (to

We have an application written in C/C++ which is broken into a single EXE and multiple DLLs. Each of these DLLs makes use of the same static library ( utilities.lib ). Any global variable in the utility static library will actually have multiple instances at runtime within the application. There will be one copy of the global variable per module (ie DLL or EXE) that utilities.lib has been linked into. (This is all known and good, but it's worth going over some background on how static libraries behave in the context of DLLs.) Now my question.. We want to change utilities.lib so that it becomes