From: Scott H. <st...@ma...> - 2014-10-01 23:36:43
|
It may be that the last compile of radmind that I did was in 2012. The MAXPATHLEN on that compiler may have been shorter than on current systems. It may be a simple rebuild of the radmind tools will make it work. However, for me a recompile will break all my versions that run on PPC so I have a quandary. I am still maintaining a bunch of PPC systems. I may have to maintain a different lapply for those dozen systems. Possibly rebuild a new version of lapply an use lipo to put the new 64 bit executables in fat binaries. Other solutions? -Scott On Oct 1, 2014, at 18:00, Ann Schwartz <ans...@ca...> wrote: > Well, this is a first for me! I updated Xcode and now have a number of lines that radmind complains have names that are too long. The transcript uploaded fine, it's radminding the client that's the problem. Here's one, just so you can see it. I agree-they are awfully long, sheesh, but what can I do about it? > > /Applications/Xcode.app/Contents/Developer/Documentation/DocSets/com.apple.adc.documentation.AppleiOS8.0.iOSLibrary.docset/Contents/Resources/Tokens/swift/func/-/CMTextFormatDescriptionGetDefaultStyle(CMFormatDescription!,UnsafeMutablePointer<UInt16>,UnsafeMutablePointer<Boolean>,UnsafeMutablePointer<Boolean>,UnsafeMutablePointer<Boolean>,UnsafeMutablePointer<CGFloat>,UnsafeMutablePointer<CGFloat>)->OSStatus.xml.radmind.780: File name too long |