Re: Xcode Build Location

2020-05-07 Thread Rob Petrovec via Cocoa-dev
Have you considered using a workspace to handle building all of your individual 
projects?  That should solve your file path & linking problem.

btw, the 28 character string is a UUID.  I’m not sure about its lifetime.

—Rob


> On May 7, 2020, at 9:57 PM, Richard Charles via Cocoa-dev 
>  wrote:
> 
> I have a project that has several large dynamically linked libraries which 
> are located in the application bundle. Each linked library is a separate 
> project.
> 
> The setting in Xcode > Preferences > Locations > Advanced > Build Location is 
> set to use Shared Folder > Build. Historically has worked well but now with 
> Xcode 11 there are some drawbacks. For example Clean Build Folder cleans the 
> entire shared build folder not just the target. Also archiving has never 
> worked and still does not work with this configuration.
> 
> So now I have changed the Xcode setting from Shared Folder to Unique which 
> apparently is the default.
> 
> When using the Unique setting a 28 character string is appended to the 
> project name in DerivedData. The string appears to be random characters but 
> most likely is not.
> 
> During build when linking to the dynamic libraries this 28 character string 
> is in the file path. So if it ever changes then linking will fail.
> 
> So my question is will this 28 character unique string always remain constant 
> for a given project?
> 
> Any insight would be appreciated.
> 
> --Richard Charles
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com
> 
> This email sent to petr...@mac.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Xcode Build Location

2020-05-07 Thread Richard Charles via Cocoa-dev
I have a project that has several large dynamically linked libraries which are 
located in the application bundle. Each linked library is a separate project.

The setting in Xcode > Preferences > Locations > Advanced > Build Location is 
set to use Shared Folder > Build. Historically has worked well but now with 
Xcode 11 there are some drawbacks. For example Clean Build Folder cleans the 
entire shared build folder not just the target. Also archiving has never worked 
and still does not work with this configuration.

So now I have changed the Xcode setting from Shared Folder to Unique which 
apparently is the default.

When using the Unique setting a 28 character string is appended to the project 
name in DerivedData. The string appears to be random characters but most likely 
is not.

During build when linking to the dynamic libraries this 28 character string is 
in the file path. So if it ever changes then linking will fail.

So my question is will this 28 character unique string always remain constant 
for a given project?

Any insight would be appreciated.

--Richard Charles

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: Cocoa-dev Digest, Vol 17, Issue 62

2020-05-07 Thread Steve Mills via Cocoa-dev
On May 7, 2020, at 17:53:43, Gabriel Zachmann via Cocoa-dev 
 wrote:
> 
> Should I skip this statement in case -startAnimation has been compiled into 
> the app?

It's not "compiled into the app". It's part of the OS. Calling it will cause it 
to do its thing, but in an environment it wasn't designed to run in. I'm 
suggesting you not use ScreenSaverView.

--
Steve Mills
Drummer, Mac geek

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: Cocoa-dev Digest, Vol 17, Issue 62

2020-05-07 Thread Gabriel Zachmann via Cocoa-dev
>> 
>> Well, in my own -startAnimation, I do
>>  [super startAnimation];
> 
> Which could be doing all sorts of things that assume it's running in a known 
> screensaver environment.

True.

Should I skip this statement in case -startAnimation has been compiled into the 
app?


Best regards, Gabriel


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com