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

Fix CMake Xcode generator. #503

Merged
merged 1 commit into from Nov 23, 2019

Conversation

vespakoen
Copy link
Contributor

By setting CMAKE_RUNTIME_OUTPUT_DIRECTORY to $<1:${CMAKE_BINARY_DIR}/bin>

Without this, the resources did not end up into the SolveSpace.app file, causing a crash on startup (where it was unable to load the locales.txt file)

The reason is that the XCode project puts things into the "bin/Debug/SolveSpace.app" or "bin/Release/SolveSpace.app" folders (depending on the target), and some files ended up in "bin/SolveSpace.app" instead, this seems to fix the locales ending up in the wrong place, but I still see some files (libraries) ending up in "bin/Debug" or "bin/Release" folders.

Here is a list of them:

$ ls bin/Debug
libcairo.a               libpixman-1.a            libslvs.dylib
libdxfrw.a               libpng16d.a              libsolvespace-core.a
libflatbuffers.a         libslvs.1.dylib          libsolvespace-headless.a
libfreetyped.a           libslvs.3.0.dylib        libz.a

This is done by setting `CMAKE_RUNTIME_OUTPUT_DIRECTORY` to `$<1:${CMAKE_BINARY_DIR}/bin>`
@CLAassistant
Copy link

CLAassistant commented Nov 23, 2019

CLA assistant check
All committers have signed the CLA.

@whitequark
Copy link
Contributor

Thank you for the PR. The SolveSpace project has a CLA. It looks like our CLA tracking tool requires your commit email to be added to the GitHub account—can you take a look at that?

Regarding libraries ending up in bin/Debug, none of those are runtime dependencies of SolveSpace.app, so it doesn't matter where they go.

@whitequark whitequark merged commit b5ccf5a into solvespace:master Nov 23, 2019
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.

None yet

3 participants