Futurescale, Inc.
PureMVC Home
The PureMVC Framework
Code at the Speed of Thought
Over 10 years of community discussion and knowledge are maintained here as a read-only archive.
New discussions should be taken up in issues on the appropriate projects at
https://github.com/PureMVC
PureMVC Architects Lounge
PureMVC Manifold
Port to Objective C
Standard Version
(:
btknorr
)
Using the obj-c port with X-Code 3.23
Pages: [
1
]
« previous
next »
Author
Topic: Using the obj-c port with X-Code 3.23 (Read 12529 times)
reduxdj
Jr. Member
Posts: 11
Using the obj-c port with X-Code 3.23
«
on:
June 29, 2010, 09:55:09 »
I am having all kinds of problems compiling the current version to xCode, i get a boat load of errors like:
1. I've tried recompiling the puremvc project
2. I've tried to include all the classes with no success
3. Can't get this to work either way
Undefined symbols:
"_OBJC_METACLASS_$_Proxy", referenced from:
_OBJC_METACLASS_$_TimerProxy in TimerProxy.o
_OBJC_METACLASS_$_DeviceProxy in DeviceProxy.o
_OBJC_METACLASS_$_LoginProxy in LoginProxy.o
_OBJC_METACLASS_$_PowerProxy in PowerProxy.o
_OBJC_METACLASS_$_ServiceProxy in ServiceProxy.o
_OBJC_METACLASS_$_StatusProxy in StatusProxy.o
_OBJC_METACLASS_$_IpProxy in IpProxy.o
_OBJC_METACLASS_$_UserProxy in UserProxy.o
"_OBJC_METACLASS_$_Mediator", referenced from:
_OBJC_METACLASS_$_DeviceListMediator in DeviceListMediator.o
_OBJC_METACLASS_$_LoginViewMediator in LoginViewMediator.o
_OBJC_METACLASS_$_VoxSTRUCTUREMediator in VoxSTRUCTUREMediator.o
"_OBJC_IVAR_$_Notifier.facade", referenced from:
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in StartupCommand.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in LogOutCommand.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in ValidateUserCommand.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in LoginUserCommand.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in GetDevicesCommand.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in TimerProxy.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in DeviceProxy.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in LoginProxy.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in PowerProxy.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in StatusProxy.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in IpProxy.o
_OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in UserProxy.o
(maybe you meant: _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr)
"_OBJC_CLASS_$_Mediator", referenced from:
_OBJC_CLASS_$_DeviceListMediator in DeviceListMediator.o
_OBJC_CLASS_$_LoginViewMediator in LoginViewMediator.o
_OBJC_CLASS_$_VoxSTRUCTUREMediator in VoxSTRUCTUREMediator.o
"_OBJC_CLASS_$_Proxy", referenced from:
_OBJC_CLASS_$_TimerProxy in TimerProxy.o
_OBJC_CLASS_$_DeviceProxy in DeviceProxy.o
_OBJC_CLASS_$_LoginProxy in LoginProxy.o
_OBJC_CLASS_$_PowerProxy in PowerProxy.o
_OBJC_CLASS_$_ServiceProxy in ServiceProxy.o
_OBJC_CLASS_$_StatusProxy in StatusProxy.o
_OBJC_CLASS_$_IpProxy in IpProxy.o
_OBJC_CLASS_$_UserProxy in UserProxy.o
"_OBJC_CLASS_$_SimpleCommand", referenced from:
_OBJC_CLASS_$_StartupCommand in StartupCommand.o
_OBJC_CLASS_$_LogOutCommand in LogOutCommand.o
_OBJC_CLASS_$_ValidateUserCommand in ValidateUserCommand.o
_OBJC_CLASS_$_LoginUserCommand in LoginUserCommand.o
_OBJC_CLASS_$_GetDevicesCommand in GetDevicesCommand.o
"_OBJC_IVAR_$_Mediator.viewComponent", referenced from:
_OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr in DeviceListMediator.o
_OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr in LoginViewMediator.o
_OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr in VoxSTRUCTUREMediator.o
(maybe you meant: _OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr)
"_OBJC_METACLASS_$_Facade", referenced from:
_OBJC_METACLASS_$_ApplicationFacade in ApplicationFacade.o
"_OBJC_METACLASS_$_SimpleCommand", referenced from:
_OBJC_METACLASS_$_StartupCommand in StartupCommand.o
_OBJC_METACLASS_$_LogOutCommand in LogOutCommand.o
_OBJC_METACLASS_$_ValidateUserCommand in ValidateUserCommand.o
_OBJC_METACLASS_$_LoginUserCommand in LoginUserCommand.o
_OBJC_METACLASS_$_GetDevicesCommand in GetDevicesCommand.o
"_OBJC_IVAR_$_Proxy.data", referenced from:
_OBJC_IVAR_$_Proxy.data$non_lazy_ptr in TimerProxy.o
_OBJC_IVAR_$_Proxy.data$non_lazy_ptr in DeviceProxy.o
_OBJC_IVAR_$_Proxy.data$non_lazy_ptr in PowerProxy.o
_OBJC_IVAR_$_Proxy.data$non_lazy_ptr in ServiceProxy.o
_OBJC_IVAR_$_Proxy.data$non_lazy_ptr in StatusProxy.o
_OBJC_IVAR_$_Proxy.data$non_lazy_ptr in IpProxy.o
_OBJC_IVAR_$_Proxy.data$non_lazy_ptr in UserProxy.o
(maybe you meant: _OBJC_IVAR_$_Proxy.data$non_lazy_ptr)
"_OBJC_CLASS_$_Facade", referenced from:
_OBJC_CLASS_$_ApplicationFacade in ApplicationFacade.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
Logged
reduxdj
Jr. Member
Posts: 11
Re: Using the obj-c port with X-Code 3.23
«
Reply #1 on:
June 30, 2010, 12:42:50 »
I eventually got this to work, instead of using the compiled .a objective c class. I downloaded the project
and used the class files instead, and now this works.
Logged
puremvc
Global Moderator
Hero Member
Posts: 2871
Re: Using the obj-c port with X-Code 3.23
«
Reply #2 on:
July 04, 2010, 07:32:17 »
Sounds like we need to recompile with the latest X-Code...
-=Cliff>
Logged
krange
Newbie
Posts: 8
Re: Using the obj-c port with X-Code 3.23
«
Reply #3 on:
September 14, 2010, 05:22:53 »
They might need a re-compile again for Xcode 3.24 now as I'm getting similar errors with the latest version...
Logged
uncleunvoid
Full Member
Posts: 27
Re: Using the obj-c port with X-Code 3.23
«
Reply #4 on:
November 24, 2010, 03:25:41 »
I also just added the files to my class list, works fine there...
Logged
Chordol
Newbie
Posts: 2
Re: Using the obj-c port with X-Code 3.23
«
Reply #5 on:
April 06, 2011, 03:46:30 »
Ditto for Xcode 4.0.1. I added the source files instead of the .a file and it works like a charm. Thanks reduxdj.
Logged
Pages: [
1
]
« previous
next »
Stack Overflow
GitHub
Linked In
Google Plus
Twitter
Powered by SMF 2.0.15
|
SMF © 2006-2007, Simple Machines LLC
|
Content © 2006-2018, Futurescale, Inc.
Loading...