Hello-
I'm wondering if anyone has been able to get the Swift 2.0 support in NUCLIOS working - in particular I'm trying to integrate IGChart into my existing Swift 2.0 project, but I don't seem to be able to even just link in the IGChart. I am running XCode 7.2 (7C68).
(To reproduce the problem, just create a blank single-page app in XCODE using Swift, Add the IG and IGChart libraries as embedded binaries, and try to compile - I continually get a Linker error "Linker command failed with exit code 1 (use -v to see invocation)" IN expanding the message within the issue navigator, there is a message that the "Framework not found IG")
I have found a workaround - and it may just indicate a bug in XCode. The basic idea is that for manually-added frameworks, within a Swift project, the Framework search path is not automatically added. You have to locate the Frameworks Search Path in the build settings - and add the path.
NOTE: in my case the path to my NUCLIOS install includes a space in the name of one of the components of the path - meaning I had to enclose the path in quotes. Once I did that, it seems to stop compaining!
However, I do wonder if I am missing a step here.
If anyone else has been able to get this working a different way, please let me know.
Thanks!
We currently don't have any Swift examples or walkthroughs, but if there's a control you'd like to see in a swift sample let us know and we'll get it created.
Hi There -
Thanks for the prompt response! I am still just getting started with NUCLIOS, but have definitely encountered this type of thing before so it wasn't too big of a deal.
I am now wondering if there are any Swift 2.0 examples or walkthroughs available? I really can't find much more than the mention of Swift in the "What's new" section.
Anyway, thanks again.
BH
Hi,
Yes, we are aware of the issue and are sorry for the extra work you had to do. Apple had recently made a change or introduced a bug that causes framework paths in the build settings with spaces to act as separate entries, which requires users to wrap the path in quotes. From what I can tell you didn't miss any steps and the work around you mention in the same one we've had to share.