At the bottom of the AudioKit Downloads page there is a section titled "Installing Xcode Documentation" which says:
Un-tar it and place it in the Shared Documentation folder:
tar -xf ~/Downloads/AudioKit.tgz -C /Applications/Xcode.app/Contents/Developer/Documentation/DocSets/
Probably I've missed something, but this seems incomplete and/or out of date. I have two questions:
Where do I download the "AudioKit.tgz" file?
Xcode Help for Xcode 9.1 says documentation should go in ~/Library/Developer/Shared/Documentation/DocSets. Which is correct?
Related
I have to support OpenSSL in my project in building my iPad app for UIKitForMac. Currently, I get these errors.
Building for UIKit for Mac, but the linked library 'libssl.a' was built for freestanding. You may need to restrict the platforms for which this library should be linked in the target editor.
Building for UIKit for Mac, but the linked library 'libcrypto.a' was built for freestanding. You may need to restrict the platforms for which this library should be linked in the target editor.
I was reading about XCFrameworks, but Apple really hasn't put out much information here. Has anyone figured out build scenarios?
The solution in the comments doesn't work for me. However, I just build to different libs: iOS as I used to and another one for Catalyst by adding the build parameters: -target x86_64-apple-ios13.0-macabi and defining Mac SDK in -isysroot. After that, I just conditionally add each of the libraries for each build version and it works.
Amid mounting frustration following many failed attempts and Google searches, I successfully built openSSL 1.1.1g for Catalyst, compiled my project, linked openSSL and launched the app on my Mac by doing the following:
I used the same directory in to which I had previously extracted and built openSSL for IOS.
Following instructions here, I edited <openSSL directory>/Configurations/10-main.conf. Scrolling down to the "darwin64-x86_64-cc" section, I added a second CFLAGS line:
CFLAGS => add("-target x86_64-apple-ios13.0-macabi"),
In the openSSL directory, execute ./Configure darwin64-x86_64-cc -shared Note that I've seen several other versions of this Configure statement, some with many more options. This command worked for me, but I'm not sure what all the other variations do. You may want to research this further.
Execute make clean to clear all the objects from the prior IOS build
Execute make This successfully built openSSL.
In Xcode, under -> General -> "Frameworks, Libraries and Embedded Content" I removed both libcrypto.a and libssl.a this was a critical step
Switching tabs to Build Phases -> Link Binary With Libraries, verify both archives are removed from this section as well. (It appeared that removing them in step 5 also cleared them in step 6, but I'm not certain).
Back on General -> Frameworks, click the + to add new entries, select "add other" in the lower left corner of the popup window, then provide the path to the newly built libcrypto.a. Repeat for libssl.a
Delete the derived data in a terminal window (I'm not certain this was necessary, but did it out of an abundance of caution):
cd ~/Library/Developer/Xcode
mv DerivedData DerivedData.old
Build the project in Xcode. This successfully completed.
Steps 5-7 turned out to be critical. Even though I moved and/or completely replaced the prior libraries, when I tried to build in Xcode I would get linker errors that I was building for MacOS Catalina but trying to link something built for MacOS x86.
In my app I have a default Documentation target that's been there for a long time.
Today, out of the blue (it seems), it stops building with:
objc[3964]: Objective-C garbage collection is no longer supported.
/Users/case/Library/Developer/Xcode/DerivedData/Talk-ghsjogqghrvpujdilbabqcornjqr/Build/Intermediates.noindex/Talk.build/Debug-iphoneos/Documentation.build/Script-48338F031615E3F60033F4C1.sh: line 2: 3964 Abort trap: 6 /Applications/appledoc --verbose xcode $SOURCE_ROOT/$PROJECT_NAME
Command /bin/sh failed with exit code 134
I tried Xcode > Product > Clean Build Folder..., emptying the DerivedData directory, and restarting Xcode.
Any idea how to fix this rather annoying issue?
This looks like you may have an old copy of appledoc in your /Applications directory. I suspect you built it at some point, installed it, and never upgraded it. I suspect your copy is v2.0 (~2010), which had garbage collection turned on. Garbage collection has been deprecated for years, and was recently removed from the OS. The current version is 2.2.1 (released in 2015).
Upgrade appledoc. My preferred way to handle those kinds of packages is with Homebrew
rm /Applications/appledoc
brew install appledoc
Apple is saying
1. Build is invalid
2. ITC.app.preReleaseBuild.errors.invalidBinary
Is it because of of icon which comes in Build. See the following image
Can you see, icon is not showing any icon but apple own default icon.
Is it a cause of this invalid.
I tried
icon.png without Alpha/transparency
Compress images to NO
re-create apple certificates, apple is allowing me to archive, without any error.
I am not using any Launch Image, but LaunchScreen.storyboard.
So, can anyone tell me what is basic cause of this rejection from apple.
Thanks.
I also faced same issue when upload my application developed in swift and supports of Cocoapods as Dependency Manager.
When i upload build it shows exactly as you upload in Screen shot.
But when i update framework.sh file as given, my build accepted by Apple and my app is on App Store now.
Try to upload after comment given code in Pods-ProjectName-frameworks.sh file.
Comment bellow given code in Pods-ProjectName-frameworks.sh file.
# Embed linked Swift runtime libraries. No longer necessary as of Xcode 7.
if [ "${XCODE_VERSION_MAJOR}" -lt 7 ]; then
local swift_runtime_libs
swift_runtime_libs=$(xcrun otool -LX "$binary" | grep --color=never #rpath/libswift | sed -E s/#rpath\\/\(.+dylib\).*/\\1/g | uniq -u && exit ${PIPESTATUS[0]})
for lib in $swift_runtime_libs; do
echo "rsync -auv \"${SWIFT_STDLIB_PATH}/${lib}\" \"${destination}\""
rsync -auv "${SWIFT_STDLIB_PATH}/${lib}" "${destination}"
code_sign_if_enabled "${destination}/${lib}"
done
fi
Hope it helps you.
So I recently had this issue when deploying to my device:
(null): error: bitcode_strip /Users/me/Library/Developer/Xcode/DerivedData/AppName-gximcjgdoodczthglfujqgpzamxl/Build/Products/Debug-iphoneos/Pods.framework/Pods: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/bitcode_strip exited with 1
I didn't encounter this error when deploying to a simulator though.
I found a solution here which says that I should set a user defined attribute 'STRIP_BITCODE_FROM_COPIED_FILES' to no.
Since then, I now get "Found an uxexpected Mach-O header code: 0x72613c21" when trying to export an archive.
Before the bitcode_strip issue, I was having no problem exporting archives so I'm wondering if the fix caused the current issue I'm facing, or if perhaps they are unrelated? If they are unrelated, what could actually be causing this?
here is the verbose IDEDistribution log
critical distribution log
standard distribution log
I have the same issue. I solved the problem when:
Uninstall cocoapods (I had installed cocoapods 0.39):
sudo gem uninstall cocoapods
Install cocoa pods 0.38.2:
sudo gem install cocoapods -v 0.38.2
For me, I went to TARGETS > General > Embedded Binaries
and removed my embedded binary (which was grey instead of yellow and happened to be Realm.framework)
Archive and submitted to iTunes then worked.
I wonder if it is because I had the Realm.framework embedded binary, but hadn't included the realm header or used realm yet - so maybe the compiler 'tried optimize away' my framework?
I'm trying to compile Qt for the iOS simulator, as explained in this article.
At first I ran into this problem but after it (kinda) solved itself I had some more.
First I kept getting this error after executing the first command, which is supposed to build qmake (../qt/configure ... etc etc):
The OpenGL ES 2.0 functionality test failed!
You might need to modify the include and library search paths by editing QMAKE_INCDIR_OPENGL_ES2, QMAKE_LIBDIR_OPENGL_ES2 and QMAKE_LIBS_OPENGL_ES2 in /Qt/qt/mkspecs/qpa/macx-iphonesimulator-g++.
Since I knew that I had the 4.3 SDK, I delved into it some more, analyzed the configure script, and after some tracing I saw that the Makefile generated by qmake, required g++-4.2 (which I didn't have), so I just ln -s g++ g++-4.2 and ln -s gcc gcc-4.2 in /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/.
I'm not sure if the aforementioned steps matter, that's why I'm writing about them. Anyway, with that, the configure step was successful. Now I ran make. After some successfully compiled files I got this:
In file included from /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/WebServicesCore.framework/Headers/WebServicesCore.h:15,
from /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:37,
from ../../include/QtCore/private/../../../../qt/src/corelib/kernel/qcore_mac_p.h:83,
from ../../include/QtCore/private/qcore_mac_p.h:1,
from /Qt/qt/src/corelib/tools/qlocale_mac.mm:49:
/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/WebServicesCore.framework/Headers/WSMethodInvocation.h:759:
error: 'CFXMLTreeRef' has not been declared
The same error appears several more times, from several different lines of WebServicesCore.h. So, basically, here's where I'm stuck now.
Any help? Again?...
Edit: Absolutely, 100% the same thing happens when I configure and try to make Qt for the device (as opposed to the simulator)
Additional info:
gcc --version : i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
iOS SDK: I have both 4.3 and 5
OS X version: 10.7.2
Xcode version (if it matters): 4.2.1
Didn't you forget to add -nomake tools and other -nomake ... to your configure ?
Try poking this guys: http://labs.qt.nokia.com/2011/08/09/update-on-uikit-lighthouse-platform/