Eliminate Header & Library Search Paths #323

Closed
blakewatters opened this Issue Sep 2, 2011 · 1 comment

Comments

Projects
None yet
1 participant
@blakewatters
Member

blakewatters commented Sep 2, 2011

We can simplify the installation process by eliminating the need to configure Library and Header Search paths. See http://mrox.net/blog/2011/06/19/framework-like-static-libraries/

@ghost ghost assigned blakewatters Sep 2, 2011

@blakewatters

This comment has been minimized.

Show comment
Hide comment
@blakewatters

blakewatters Sep 2, 2011

Member

This change also eliminates the need to use the Copy Headers & Protect Headers script tasks, which speeds up library builds (even though the rsync task has relatively low overhead).

Note that this change makes the use of Derived Data a requirement. I think that this a reasonable trade-off for simplified build process and installation. If there is push-back, we can bring back the use of the copy headers task and document it on the Wiki.

Member

blakewatters commented Sep 2, 2011

This change also eliminates the need to use the Copy Headers & Protect Headers script tasks, which speeds up library builds (even though the rsync task has relatively low overhead).

Note that this change makes the use of Derived Data a requirement. I think that this a reasonable trade-off for simplified build process and installation. If there is push-back, we can bring back the use of the copy headers task and document it on the Wiki.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment