I thought everyone would like to know that I've managed to significantly reduce the time that "Checking Dependencies" takes for us
PATH_PREFIXES_EXCLUDED_FROM_HEADER_DEPENDENCIES = $(inherited) "$(WXWIN)"/include "$(WXWIN)"/src "$(BOOST)"/include/boost-$(BOOST_VERSION)
Any relatively static external API gets added to this list. For us, the above is effectively the same as:
PATH_PREFIXES_EXCLUDED_FROM_HEADER_DEPENDENCIES = $(inherited) $(HEADER_SEARCH_PATHS)
This assumes that any project-local header search paths go into $(USER_HEADER_SEARCH_PATHS). Boost is so big with so many header interdependencies that this can make a huge difference. The downside is that Xcode will no longer notice when header files in these APIs change, but hopefully, that will be rare enough that the decrease in time will outweigh the time of doing an additional clean and rebuild.
Another lesser setting that can make a difference: EXCLUDED_RECURSIVE_SEARCH_PATH_SUBDIRECTORIES
Good luck!
------------------------------- Hank Schultz Cedrus Corporation
On Feb 25, 2009, at 12:51 PM, Emile Tobenfeld wrote: At 7:27 PM -0800 2/24/09, Chris Espinosa wrote: On Feb 24, 2009, at 5:52 PM, Emile Tobenfeld (a. k. a Dr. T) wrote:
I'm still having severe problems. The hang up seems to come in the clean process, but when I folloow your instructions to make the usage file, I get new-host-2:~ emile$ $sudo fs_usage Xcode > ~/XcodeFSUsage.txt 'fs_usage' must be run as root...
Don't type the $. I put it there to represent the shell prompt.
Chris,
OK, now it asks me for my password, and then presumably does something. Where should I look for XcodeFSUsage.txt
The hang up, seemed to go away when I cleaned dependencies also -- when I didn't have clean dependencies checked, Xcode would hang for so long I would force quit and start again.
If it is actually hanging, please do a sample and submit it. But the fs_usage log will be more helpful.
The Xcode team really ought to make this process more transparent and controllable by the user. Code Warrior users remember being able to manually prevent recompiles by hitting a button within the project.
I would rather Just Make It Work than find ways for people to work around when it doesn't.
Yesterday I was encountering situations where Xcode sat for several minutes checking dependencies, with no other feedback, and no way to stop the process other than by force quitting. Today I wanted to interrupt a compile which had given unexpected errors, and I had to force quit.
This makes for an inefficient work environment.
Chris
--
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|