Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes trouble when setting archive output dir #465

Merged
merged 1 commit into from
Jan 27, 2014

Conversation

dbarbier
Copy link
Collaborator

If the indented use was to copy the mingw .a files in the install path,
it should be done inside the OCE_BUNDLE_AUTOINSTALL section.
In MSVC this is unnecessary.

…all path

If the indented use was to copy the mingw .a files in the install path,
it should be done inside the OCE_BUNDLE_AUTOINSTALL section.
In MSVC is unnecessary.
@dbarbier
Copy link
Collaborator Author

This was the last commit at #456, I moved it to its own pull request because it looked controversial to me, and I wanted to merge other commits.

Anyway, +1 from me.

dbarbier added a commit that referenced this pull request Jan 27, 2014
Fixes trouble when setting archive output dir
@dbarbier dbarbier merged commit 3197c8c into master Jan 27, 2014
@dbarbier dbarbier deleted the review/fix-ARCHIVE_OUTPUT_DIRECTORY branch January 27, 2014 20:08
camio pushed a commit to camio/oce that referenced this pull request Mar 7, 2014
…ECTORY.

If 'CMAKE_ARCHIVE_OUTPUT_DIRECTORY' is used to customize the output
folders of oce-win-bundle libraries, the oce build will set
FREETYPE_LIBRARY and related variables to the wrong paths.

This patch fixes that bug.

The commit that inserted this removal in the first place
(tpaviot#465) did not provide any explination
for it.
camio pushed a commit to camio/oce that referenced this pull request Mar 9, 2014
…ECTORY.

If 'CMAKE_ARCHIVE_OUTPUT_DIRECTORY' is used to customize the output
folders of oce-win-bundle libraries, the oce build will set
FREETYPE_LIBRARY and related variables to the wrong paths.

This patch fixes that bug.

The commit that inserted this removal in the first place
(tpaviot#465) did not provide any explination
for it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants