Databases
StackOverflow2013
Postsdbo
POiOS Unit Testing - Issue accessing functions from Native Library
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS Unit Testing - Issue accessing functions from Native Library
    primarykey
    data
    text
    <p>I'm creating a Wrapper library project which uses another Native-C library. I'm able to use the Wrapper library functions in other applications, through which am able to accessing the functions, which are present in Native-C library.</p> <p>Now, in Wrapper Library project, when I added 'Unit Testing' (using OCUnit, ), it is giving the errors for all the functions which are present in Native C library. The error is coming while executing the Unit Testing only.</p> <p>The error it shows is,</p> <p>**Undefined symbols for architecture i386: "_SQMT_FUNC_close", referenced from: _funcClose in libWrapperLibraryAlter.a(wrapperAPI.o)</p> <pre><code> ld: symbol(s) not found for architecture i386 </code></pre> <p>clang: error: linker command failed with exit code 1 (use -v to see invocation)**</p> <p>The function, 'funcClose' is present in current Wrapper Library project (.m file). The function, 'SQMT_FUNC_close' is present in Native-C library project (.c file). </p> <p>Unit test execution shows error for all the Native-C functions.</p> <p>Kindly help in resolving this issue.</p> <p>The Lirary path:</p> <pre><code>**/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch i386 -bundle -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.1.sdk -L/work/Final_code/test/iOS/Debug-iphonesimulator -L/work/Final_code/test/iOS/iOSWrapper/../../Product/Library/iOS/Release-iphoneos -F/work/Final_code/test/iOS/Debug-iphonesimulator -F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.1.sdk/Developer/Library/Frameworks -F/Applications/Xcode.app/Contents/Developer/Library/Frameworks -filelist /work/Final_code/test/iOS/Build/Intermediates/iOSWrapper.build/Debug-iphonesimulator/wrapperTests.build/Objects-normal/i386/wrapperTests.LinkFileList -Xlinker -objc_abi_version -Xlinker 2 -fobjc-arc -fobjc-link-runtime -Xlinker -no_implicit_dylibs -mios-simulator-version-min=5.0 -liOSWrapper -lHomeLittle -framework SenTestingKit -framework Foundation -framework UIKit -o /work/Final_code/iOS/Debug-iphonesimulator/wrapperTests.octest/wrapperTests** </code></pre> <p>iOSWrapper - is the current wrapper library that i'm testing. HomeLittle - is the Native C library</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USArun
    1. USArun
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POiOS Unit Testing - Issue accessing functions from Native Library
      1. USArun
      1. VTFavorite
    1. COCan you just add -L <path to directory where .a/.o library file is> -l<yournativelib>? your native library should have a name lib<something>, then you add it like -l<something>
      singulars
      1. POiOS Unit Testing - Issue accessing functions from Native Library
      1. USexebook
    2. COexebook : i added the library path. please check.
      singulars
      1. POiOS Unit Testing - Issue accessing functions from Native Library
      1. USArun
    3. COCan you check if compiler reports `cannot find library HomeLittle` before it goes to `undefined symbols`?
      singulars
      1. POiOS Unit Testing - Issue accessing functions from Native Library
      1. USexebook
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload