Re: Problem with #import <>
Re: Problem with #import <>
- Subject: Re: Problem with #import <>
- From: Dave <email@hidden>
- Date: Fri, 15 Apr 2016 15:36:24 +0100
Hi,
> On 15 Apr 2016, at 15:19, Steve Mills <email@hidden> wrote:
>
> On Apr 15, 2016, at 09:10 AM, Dave <email@hidden> wrote:
>
>> Meant to add, if I change the <> to “” it works ok, I’ve tried setting “Framework Search Paths” and “Header Search Paths” to the folders that contains the header files, but I still get errors.
>>
>> Is there another path I need to set? I really don’t want to have to change the <> to “” everywhere…….
>
>
> Is Always Search User Paths turned on in the project/target? <> and "" really do mean different things. Always using <> for project files (i.e. user paths) is wrong and should be avoided for this very reason.
I’ve tried it with it set to YES and set to NO but I still get the same errors.
I realise the <> and “” are for different things. This is a bit of a special case, normally this would be a a framework, but for this special temporary Workspace, I need to get it to compile with the header files in the workspace/project hierarchy. Basically I’m plug-replacing a 3rd party framework, but want the source code to remain the same e.g. not change <> to “”.
Any ideas on how to do this would be greatly appreciated.
All the Best
Dave
_______________________________________________
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