Re: Not finding @import module
Re: Not finding @import module
- Subject: Re: Not finding @import module
- From: Quincey Morris <email@hidden>
- Date: Sat, 6 May 2017 23:10:12 -0700
On May 6, 2017, at 22:46 , Steve Mills <email@hidden> wrote:
to keep build folders in more logical places than the stupid DerivedData folder
It’s not worth (say) having an argument about this (he said defensively) but I think it’s better understood as a case of other places being more stupid than logical, and DerivedData being more logical than stupid, at least from a current Xcode workflow perspective.
The point is that everything in DerivedData is *temporary* in some sense, and if you needed to use a fixed, permanent, custom build folder to somehow get a *temporary* build product in a fixed way, you were probably Doing It Wrong™.
I do understand that there can be scenarios with frameworks where it’s sort of easier to set up the workflow using a fixed build folder, but generally it’s going to bite you somewhere along the line, as it just did here.
FWIW — which may not be much.
|
_______________________________________________
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