Re: Porting projects from Windows
Re: Porting projects from Windows
- Subject: Re: Porting projects from Windows
- From: David Dunham <email@hidden>
- Date: Tue, 09 Sep 2008 19:03:31 -0700
On 9 Sep 2008, at 13:19, Thomas Hauk wrote:
Porting this project over to OS X has been a huge pain in the butt.
The biggest issue is that Xcode does not share in this philosophy of
separating packages very well. In trying to match the .vcproj idea
from Windows, and creating a .xcodeproj for each package, I've ended
up with a huge mess of projects, and a big functionality problem: I
can't change the code for a library while in the top-level
(application) project and expect all the dependencies to trigger
automatic rebuilds and relink. Visual Studio handles this with
perfect ease.
I've been able to have Xcode compile dependent projects just fine.
Doesn't seem any different from Visual Studio (though perhaps the
setup process is slightly different).
Also, is there any hope in heck that Apple will adopt the vcproj/sln
design philosophy?
Why is this a good thing? (But maybe that's because I was trained to
2click .vcproj files and keep opening the wrong thing.)
I've always found the multiplying configurations a nightmare with
Visual Studio -- if the names don't match, you're in for a world of
hurt.
David Dunham A Sharp, LLC
Voice/Fax: 206 783 7404 http://a-sharp.com
Efficiency is intelligent laziness.
_______________________________________________
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