The Three20 documentation did not solve this issue for me (unfortunately...). Eventually what worked for me was a mix of a few solutions. There is a difference between "Archive" and "Build for Archiving" (or build for run) and using these steps I have both of them working with no build issues.
The Three20 documentation did not solve this issue for me (unfortunately...). Eventually what worked for me was a mix of a few solutions. There is a difference between "Archive" and "Build for Archiving" (or build for run) and using these steps I have both of them working with no build issues: You will need to change the scripts as Manni mentioned above, set the "Skip Install" flag for each Three20 project linked to your project tree and add the following paths to your project's "Header search paths": "$(BUILT_PRODUCTS_DIR)/../three20" "$(BUILT_PRODUCTS_DIR)/../../three20" this will get you to work with the Build option.
When you want to perform the archive action, then you will also need to change the "Locations" preference in Xcode as featherless mentioned above. I documented these steps in this post.
That was wonderful post and saved my lot of time. Thanks – Pruthvid Jul 21 '11 at 19:43 AWESOME, I appreciate your time documenting the steps. THANK YOU!
– Tuyen Nguyen Nov 28 '11 at 14:38.
Configuration that works both for build and archive in Xcode4. Https://github.com/pazustep/three20/commit/4a9aa... src/common/Configurations/Paths. Xcconfig REPO_ROOT_PATH = $(SRCROOT)/../.. ROOT_SOURCE_PATH = $(REPO_ROOT_PATH)/src //OBJROOT = $(REPO_ROOT_PATH)/Build //SYMROOT = $(OBJROOT)/Products // Search Paths LIBRARY_SEARCH_PATHS = $(STDLIB_LIBRARY) //HEADER_SEARCH_PATHS = $(STDLIB_HEADERS) "$(CONFIGURATION_BUILD_DIR)/../three20" HEADER_SEARCH_PATHS = $(STDLIB_HEADERS) "$(BUILT_PRODUCTS_DIR)/../three20" "$(BUILT_PRODUCTS_DIR)/../../three20" src/scripts/Protect.
Command # Ignore whitespace characters in paths IFS=$'\n' #cd ${CONFIGURATION_BUILD_DIR}${PUBLIC_HEADERS_FOLDER_PATH} if "${DEPLOYMENT_LOCATION}" == "YES" ; then PREFIX=${BUILT_PRODUCTS_DIR}/.. else PREFIX=${BUILT_PRODUCTS_DIR} fi cd ${PREFIX}${PUBLIC_HEADERS_FOLDER_PATH} chmod a-w *. H 2>> /dev/null chmod a-w private/*. H 2>> /dev/null exit 0.
After this changes, I get "Three20/Three20. H: No such file or directory" in my source code: #import "Three20/Three20. H" – Manni Mar 11 '11 at 8:16 any way to fix it?
– aherlambang May 20 '11 at 5:02.
I'm looking into this right now and will hopefully put together an adequate patch that works in both Xcode 3.2. # and Xcode 4. Edit: So it looks like the easiest way to get old Xcode 3.2 projects to work with Xcode 4 is to do the following: Go into Xcode 4's preferences (Cmd+,). Select the "Locations" tab.
Where it says "Build Locations", select the drop down and pick "Place build products in locations specified by targets" I'll write up a three20. Info article going into more details about this.
Thank you Jeff! – sudo rm -rf Mar 10 '11 at 16:18 That sounds very good, I'll test it tomorrow! – Manni Mar 10 '11 at 20:08 I changed the build location but I still get the "no such file or directory" error message :-( – Manni Mar 11 '11 at 7:42 I tried this and it still didn't work.
– Daniel O May 24 '11 at 15:39 I had to compile it the usual way once before trying to create archive for this to work! – fredrik Aug 12 '11 at 15:27.
Three20. Info: Xcode 4 Transition Guide three20.info/article/2011-03-10-Xcode4-S... This guide has been put together by the Three20 team in order to help you migrate your apps to Xcode 4 successfully.
1 Please use this article to transition to Xcode 4. All other methods are not officially supported. – featherless Mar 14 '11 at 16:33 Alas, this article is not working for me.
Will keep trying different things though. :( – Joe D'Andrea Jun 17 '11 at 18:03.
Another thing that could throw off the build process is using a scheme name that contains spaces. XCode won't stop you from doing it, but if you use a name like "Ad Hoc" for your scheme, you'll end up the same errors: Three20/Three20+Additions. H: No such file or directory.
I've re-learned this rule several times. I tend to see errors during the link phase. – Kristopher Johnson Nov 1 '11 at 14:16.
Open the file /src/common/Configurations/Paths. Xcconfig old code: HEADER_SEARCH_PATHS = $(STDLIB_HEADERS) "$(CONFIGURATION_BUILD_DIR)/../three20" new code: HEADER_SEARCH_PATHS = $(STDLIB_HEADERS) "$(CONFIGURATION_BUILD_DIR)/../../three20" So, I still have 7 errors, but I can create the archive...
Google Groups: Xcode 4, Three20 and Project -> Archive groups.google.com/group/three20/browse_f....
Amir Naor's answer is perfect. I verified his answer on xcode 4.2 and it worked. I missed the step "You will need to change the scripts as Manni mentioned above" so I kept getting the similar error as quoted in the original question post.
Hope you don't make the same mistake. Also as of xcode 4.2, the step "then you will also need to change the "Locations" preference in Xcode as featherless mentioned above. " isn't needed any more.
Make sure your scheme name doesn't contains spaces. That also leads to the "File not found" build error.
I had to go under Project Info > Build (tab) and add the following to the header search path: three20/Build/Products/three20 This path may be specific to my project, but there it is in case it works for someone else.
Configuration that works both for build and archive in Xcode4. Https://github.com/pazustep/three20/commit/4a9aad4eb90a6962dd729d245f9293a7cc0d7f36.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.