Open johncrane opened 11 years ago
Can you confirm following?
The first 2 lines of warnings says that you do not have the directories.
If the answer to the questions above, please post your environment here (Where's you Xcode5 path?)
Xcode is at "/Applications/Xcode.app". There is no "Xcode 2.app". I don't know where it came from. The first 2 lines of warning seems not fatal. the linker does not understand "-dependency_info". Can this caused by Xcode updater messed up my dev environment?
Sorry but "Xcode 2.app" comes from my environment. I did not intend to Xcode to search framework on that paths but It looks that Xcode want the framework on that paths. Hm... I do not know why Xcode says so in your environment sicne others can compile it.
I'll try to fix it but as a temporary fix you can rename your Xcode.app to Xcode 2.app . It should fix the compile error.
Let me know if you have further problems.
Yea I confirmed that the problem is -depencency_info. I do not know what this is....
I can build xvim with xcode5, but it doesn't show up in the menu, or work... help? xcode version is Version 5.0 (5A1413) and I renamed the app as Xcode 2.app OS X Version 10.8.5 Macbook pro...
So you restart the Xcode but you do not have XVim menu?? How about trying to change your Xcode2.app to Xcode.app?
I have restarted Xcode and restarted the machine -- neither works. I have also tried building with Xcode.app, Xcode2.app -- same results for both.
I am very grateful for this plugin -- it has saved my sanity -- I would love to get it to work on xcode5.
Thank you for your help.
Questions, concerns, comments, corrections, always welcome.
Rick Zemer E-gineering, LLC (317) 997-8985 (c) rick.zemer@e-gineering.commailto:rick.zemer@e-gineering.com
On Oct 11, 2013, at 8:42 AM, JugglerShu notifications@github.com<mailto:notifications@github.com> wrote:
So you restart the Xcode but you do not have XVim menu?? How about trying to change your Xcode2.app to Xcode.app?
— Reply to this email directly or view it on GitHubhttps://github.com/JugglerShu/XVim/issues/472#issuecomment-26133962.
Try following
I updated previous post. The scheme name is "XVim for Xcode5"
Bless you!
Thanks -- it now works! (I didn't see the other scheme). I am somewhat of a iOS newbie, but I would love to help with the plugin. If there are some simple tasks (to start:), let me know. I have been coding for years, but mostly embedded systems.
Thanks again!
Questions, concerns, comments, corrections, always welcome.
Rick Zemer E-gineering, LLC (317) 997-8985 (c) rick.zemer@e-gineering.commailto:rick.zemer@e-gineering.com
On Oct 11, 2013, at 10:05 AM, JugglerShu notifications@github.com<mailto:notifications@github.com> wrote:
I updated previous post. The scheme name is "XVim for Xcode5"
— Reply to this email directly or view it on GitHubhttps://github.com/JugglerShu/XVim/issues/472#issuecomment-26139347.
@johncrane Have you fixed this problem??
I didn't try it since last time encounter the same issue. Finally I switched back to XCode4.6.3 because our proejct does not work well with XCode5. XCode5 caused a lot of problem to the team and finally the team decide to stay in Xcode4.
On Fri, Oct 11, 2013 at 10:32 AM, JugglerShu notifications@github.comwrote:
@johncrane https://github.com/johncrane Have you fixed this problem??
— Reply to this email directly or view it on GitHubhttps://github.com/JugglerShu/XVim/issues/472#issuecomment-26141463 .
I'm having the same issue as EG-raz.
XVim master (sha 9d48e7e135d95835624cdd02c434ab1faf027e95) with XCode 5.0.2 on OSX 10.9.2.
Xvim builds absolutely fine, (with a few warnings) but doesn't show up in menu or output any debug logs (when compiled in debug mode).
Appstore pushed the new Xcode today. After I updated Xcode, the XVim is disabled. So I uninstalled the old XVim plugin, downloaded the source code, then rebuild failed.
I tried to clean up, set schema to "XVim for Xcode5", set to release build. Nothing works.
My Macbook pro information: Darwin Kernel Version 12.5.0 x86_64
Is this a known issue? Is there a work around? Thanks
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.