Greetings opensource developers. Tomorrow, Thursday 7/21, between 12:00 noon and 1:00 PM PST, the Webkit source tree will upgrade to XCode 2.1 project files. Since most of you are already using XCode 2.1, this shouldn't affect you. However, if you are still using XCode 2.0, you will need to upgrade to 2.1 before then. Once this upgrade takes place, you should remove your old build products directory and your old project file directories. A quick way to remove your old project file directories is: find . -name \*.pbproj | xargs rm -rf; find . -name \*.xcode | xargs rm -rf. Cheers, Geoff Garen
Shouldn't it be \*.xcodeproj rather than \*.xcode? It's probably obvious to people who are more familiar with the command line than I am, but it slowed me down a bit. Kurt Kohler Geoffrey Garen wrote:
Greetings opensource developers.
Tomorrow, Thursday 7/21, between 12:00 noon and 1:00 PM PST, the Webkit source tree will upgrade to XCode 2.1 project files. Since most of you are already using XCode 2.1, this shouldn't affect you. However, if you are still using XCode 2.0, you will need to upgrade to 2.1 before then.
Once this upgrade takes place, you should remove your old build products directory and your old project file directories. A quick way to remove your old project file directories is: find . -name \*.pbproj | xargs rm -rf; find . -name \*.xcode | xargs rm -rf.
Cheers, Geoff Garen
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
*.xcode will find the old-style project files, which are the ones that should be deleted. New-style project files have the extension .xcodeproj. John On Jul 22, 2005, at 12:38 PM, Kurt Kohler wrote:
Shouldn't it be \*.xcodeproj rather than \*.xcode?
It's probably obvious to people who are more familiar with the command line than I am, but it slowed me down a bit.
Kurt Kohler
Geoffrey Garen wrote:
Greetings opensource developers.
Tomorrow, Thursday 7/21, between 12:00 noon and 1:00 PM PST, the Webkit source tree will upgrade to XCode 2.1 project files. Since most of you are already using XCode 2.1, this shouldn't affect you. However, if you are still using XCode 2.0, you will need to upgrade to 2.1 before then.
Once this upgrade takes place, you should remove your old build products directory and your old project file directories. A quick way to remove your old project file directories is: find . -name \*.pbproj | xargs rm -rf; find . -name \*.xcode | xargs rm -rf.
Cheers, Geoff Garen
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
Well I guess I'm really confused. Why did I get "move out of the way" errors from cvs on e.g. .cvsignore in the *.xcodeproj directories until I deleted those directories? John Sullivan wrote:
*.xcode will find the old-style project files, which are the ones that should be deleted. New-style project files have the extension .xcodeproj.
John
On Jul 22, 2005, at 12:38 PM, Kurt Kohler wrote:
Shouldn't it be \*.xcodeproj rather than \*.xcode?
It's probably obvious to people who are more familiar with the command line than I am, but it slowed me down a bit.
Kurt Kohler
Geoffrey Garen wrote:
Greetings opensource developers.
Tomorrow, Thursday 7/21, between 12:00 noon and 1:00 PM PST, the Webkit source tree will upgrade to XCode 2.1 project files. Since most of you are already using XCode 2.1, this shouldn't affect you. However, if you are still using XCode 2.0, you will need to upgrade to 2.1 before then.
Once this upgrade takes place, you should remove your old build products directory and your old project file directories. A quick way to remove your old project file directories is: find . -name \*.pbproj | xargs rm -rf; find . -name \*.xcode | xargs rm -rf.
Cheers, Geoff Garen
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
I think I understand what happened. If you were previously building with XCode 2.1, .xcodeproj directories would be automatically created when you launched the .xcode project. (You'd get an alert telling you this and giving you the opportunity to choose where to place the new project file.) Anything created that way would not be in cvs, so when the new .xcodeproj files were checked in, cvs would give that "move out of the way" error. So that's probably what happened. So for people who had been using XCode 2.0, the script did the right thing by removing .xcode directories. But for people who had been uxing XCode 2.1, the script did not remove the .xcodeproj directories, thus leading to the "move out of the way" message. Removing both .xcode and .xcodeproj directories would have worked correctly for everyone, I believe. John On Jul 23, 2005, at 4:10 PM, Kurt Kohler wrote:
Well I guess I'm really confused. Why did I get "move out of the way" errors from cvs on e.g. .cvsignore in the *.xcodeproj directories until I deleted those directories?
John Sullivan wrote:
*.xcode will find the old-style project files, which are the ones that should be deleted. New-style project files have the extension .xcodeproj.
John
On Jul 22, 2005, at 12:38 PM, Kurt Kohler wrote:
Shouldn't it be \*.xcodeproj rather than \*.xcode?
It's probably obvious to people who are more familiar with the command line than I am, but it slowed me down a bit.
Kurt Kohler
Geoffrey Garen wrote:
Greetings opensource developers.
Tomorrow, Thursday 7/21, between 12:00 noon and 1:00 PM PST, the Webkit source tree will upgrade to XCode 2.1 project files. Since most of you are already using XCode 2.1, this shouldn't affect you. However, if you are still using XCode 2.0, you will need to upgrade to 2.1 before then.
Once this upgrade takes place, you should remove your old build products directory and your old project file directories. A quick way to remove your old project file directories is: find . -name \*.pbproj | xargs rm -rf; find . -name \*.xcode | xargs rm -rf.
Cheers, Geoff Garen
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
Ah! I think you've got it. I was indeed using XCode 2.1. This brings up something I've been meaning to mention, shouldn't information like this (and the earlier SVG changes) be on the web site? Some people who want to build webkit may not be subscribed to this mailing list. John Sullivan wrote:
I think I understand what happened.
If you were previously building with XCode 2.1, .xcodeproj directories would be automatically created when you launched the .xcode project. (You'd get an alert telling you this and giving you the opportunity to choose where to place the new project file.) Anything created that way would not be in cvs, so when the new .xcodeproj files were checked in, cvs would give that "move out of the way" error. So that's probably what happened.
So for people who had been using XCode 2.0, the script did the right thing by removing .xcode directories. But for people who had been uxing XCode 2.1, the script did not remove the .xcodeproj directories, thus leading to the "move out of the way" message. Removing both .xcode and .xcodeproj directories would have worked correctly for everyone, I believe.
John
On Jul 23, 2005, at 4:10 PM, Kurt Kohler wrote:
Well I guess I'm really confused. Why did I get "move out of the way" errors from cvs on e.g. .cvsignore in the *.xcodeproj directories until I deleted those directories?
John Sullivan wrote:
*.xcode will find the old-style project files, which are the ones that should be deleted. New-style project files have the extension .xcodeproj.
John
On Jul 22, 2005, at 12:38 PM, Kurt Kohler wrote:
Shouldn't it be \*.xcodeproj rather than \*.xcode?
It's probably obvious to people who are more familiar with the command line than I am, but it slowed me down a bit.
Kurt Kohler
Geoffrey Garen wrote:
Greetings opensource developers.
Tomorrow, Thursday 7/21, between 12:00 noon and 1:00 PM PST, the Webkit source tree will upgrade to XCode 2.1 project files. Since most of you are already using XCode 2.1, this shouldn't affect you. However, if you are still using XCode 2.0, you will need to upgrade to 2.1 before then.
Once this upgrade takes place, you should remove your old build products directory and your old project file directories. A quick way to remove your old project file directories is: find . -name \*.pbproj | xargs rm -rf; find . -name \*.xcode | xargs rm -rf.
Cheers, Geoff Garen
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
On Jul 23, 2005, at 11:47 PM, Kurt Kohler wrote:
Ah! I think you've got it. I was indeed using XCode 2.1.
This brings up something I've been meaning to mention, shouldn't information like this (and the earlier SVG changes) be on the web site? Some people who want to build webkit may not be subscribed to this mailing list.
Probably in the blog but not the website proper. For people who are just checking out for the first time, the only real issue is that Xcode 2.1 is required and we should change the website to say that. Migration issues for people who already built in the past are more blog-fodder than website fodder. -- Darin
I agree that the blog is where it belongs. I wasn't properly distinguishing the blog from the web site. Darin Adler wrote:
On Jul 23, 2005, at 11:47 PM, Kurt Kohler wrote:
Ah! I think you've got it. I was indeed using XCode 2.1.
This brings up something I've been meaning to mention, shouldn't information like this (and the earlier SVG changes) be on the web site? Some people who want to build webkit may not be subscribed to this mailing list.
Probably in the blog but not the website proper. For people who are just checking out for the first time, the only real issue is that Xcode 2.1 is required and we should change the website to say that.
Migration issues for people who already built in the past are more blog-fodder than website fodder.
-- Darin
participants (4)
-
Darin Adler
-
Geoffrey Garen
-
John Sullivan
-
Kurt Kohler