Re: Not finding libraries
Re: Not finding libraries
- Subject: Re: Not finding libraries
- From: Howard Moon <email@hidden>
- Date: Mon, 09 Jan 2017 08:47:32 -0800
> On Jan 6, 2017, at 9:00 PM, Alex Zavatone <email@hidden> wrote:
>
> OK. You can add the quotes around the paths straight within the build settings. That's what I was talking about before.
>
Only if you do so in the .xcconfig file. If they are in the settings (whether it’s in Other Linker Flags or Library Search Paths), Xcode (6.4) will mangle them at some point.
> You certainly can add these to an xcconfig, but if you search build settings for "Other Linker Flags", it's right there in your build settings and you already have a Debug and a Release configuration. Just click on the item and there is a hidden arrow on the left that lets you expand this to see both configs.
>
I know that. That’s how I knew what symbol to put in the .xcconfig file, by dragging the current values from the settings to my config file, so that I could edit by hand to exactly what I wanted.
> Seriously, it's pure idiocy for the UI team to hide these REALLY IMPORTANT UI controls. It's complete BS to obscure vital parts of the UI that tell the user that the thing they are looking at is not 1 item, but an expandable item that contains MORE items.
>
> My whole idea was to learn what's provided to us already and learn how to work within that, before I go off and start entering things by hand.
>
> The only thing you had to do was put double quotes around paths within the build settings section for it.
>
No, that is NOT the case. I know about expanding the settings for each configuration. I did that. And I put double-quotes around the paths in the Other Linker Flags settings, including trying entering it all on one line and by making separate lines myself (with the ‘+’ button). Either way ends up the same. When later re-opening Xcode, it adds \ escape characters to the spaces and double-quotes in the paths.
The ONLY method which prevents Xcode from ever mangling the paths is for them to NOT go into the project itself, but keep them in the config file, where Xcode won’t touch them, ever.
> I hope this helps.
> Cheers,
> Alex Zavatone
>
> On Jan 6, 2017, at 5:22 PM, Howard Moon wrote:
>
>> Hi Alex,
>>
>> In case it helps, here’s what I did, which worked beautifully:
>>
>>> I created a .xcconfig file for each configuration (but did NOT add them to any target, because they don’t need to be copied into the product itself).
>>
>>> I created a line like this in each file:
>> OTHER_LD_FLAGS = “some path/build/Debug/lib1.a” “some path/build/Debuglib2.a"
>>
>>> Under the Project Settings / Info, selected the file appropraite file for each configuration (for example, “DebugConfig.xcconfig” for “Debug” configuration).
>>
>>> Then I went to first the Project Settings and then the Target settings, and deleted the overrides I had for the entries in both Library Search Paths, and Other Linker Flags. (I did this by selecting the setting and hitting Delete.) This replaced the Other Linker Flags in the Target settings with the line I had entered into the .xcconfig file.
>>
>> So now, Xcode no longer touches the strings for the libraries I am linking to, and they are used in the “ld” command exactly as I wrote them in the config file.
>>
>> (I have not made any other config file entries, but I probably will, if and when I identify other ones that seem appropriate to keep there. However, my AAX audio plug-in projects have a LOT of entries in them, which were made originally by Digidesign/Avid for use with plug-ins that third parties like us want to create.)
>>
>> -Howard
>>
>>> On Jan 6, 2017, at 1:07 PM, Alex Zavatone <email@hidden> wrote:
>>>
>>> Bernie and Howard, thanks for bringing this to my attention. I'd love to share notes on this process as it would probably help the group as a whole.
>>>
>>> Bernie, what in particular from your project have you moved into these files, where are they within your project and are they shared project-wide? How is what is defined in them propagated to the rest of the workspace/project/subprojects?
>>>
>>> Thanks in advance,
>>> Alex Zavatone
>>>
>>> On Dec 29, 2016, at 7:21 PM, Bernie Maier wrote:
>>>
>>>> Howard Moon:
>>>>
>>>>
>>>> I haven't tried this for myself, but I think you may avoid some of these problems if you moved these settings into .xcconfig files. You could define your build variables there, correctly quoted to cope with the spaces, and the Xcode UI will not futz with them.
>>>>
>>>> Personally, I'm a big fan of .xcconfig files and move as many build settings into them as possible. But to get started you probably only need minimal versions: a debug one and a release one.
>>>>
>>>>
>>>> --Bernie
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>> _______________________________________________
>> 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
_______________________________________________
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