cocoapods-packager icon indicating copy to clipboard operation
cocoapods-packager copied to clipboard

Dynamic framework pack issue

Open hello-david opened this issue 5 years ago • 0 comments

Command

pod _1.5.3_ package ./Pack_MTGLDebug.podspec --dynamic --verbose

this is the project i am trying: https://github.com/hello-david/Pack_MTGLDebug

Report

What did you do?

Really just run the above command on current supported dynamic packager.

What did you expect to happen?

A dynamic framework should have been created

What happened instead?

    Undefined symbols for architecture armv7s:
      "std::PodPack_MTGLDebug_exception::what() const", referenced from:
          vtable for std::__1::bad_function_call in libMTGLDebug.a(MTGLDebugCore.o)
          vtable for std::__1::bad_function_call in libMTGLDebug.a(MTGLDebugCoreBridge.o)
          vtable for std::__1::bad_function_call in libMTGLDebug.a(MTGLDebugQueue.o)
      "typeinfo for std::PodPack_MTGLDebug_exception", referenced from:
          typeinfo for std::__1::bad_function_call in libMTGLDebug.a(MTGLDebugCore.o)
          typeinfo for std::__1::bad_function_call in libMTGLDebug.a(MTGLDebugCoreBridge.o)
          typeinfo for std::__1::bad_function_call in libMTGLDebug.a(MTGLDebugQueue.o)
      "std::PodPack_MTGLDebug_exception::~PodPack_MTGLDebug_exception()", referenced from:
          std::__1::bad_function_call::~bad_function_call() in libMTGLDebug.a(MTGLDebugCore.o)
          std::__1::bad_function_call::~bad_function_call() in libMTGLDebug.a(MTGLDebugCore.o)
          std::__1::bad_function_call::~bad_function_call() in libMTGLDebug.a(MTGLDebugCoreBridge.o)
          std::__1::bad_function_call::~bad_function_call() in libMTGLDebug.a(MTGLDebugCoreBridge.o)
          std::__1::bad_function_call::~bad_function_call() in libMTGLDebug.a(MTGLDebugQueue.o)
          std::__1::bad_function_call::~bad_function_call() in libMTGLDebug.a(MTGLDebugQueue.o)
    ld: symbol(s) not found for architecture armv7s
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

Solution

For now, I just skip the <exception> file symbol and worked. Can someone tell me how to fix it more safely?

hello-david avatar May 24 '19 02:05 hello-david