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

SFML framework creation fails on OS X #595

Closed
Ceylo opened this Issue May 12, 2014 · 1 comment

Comments

Projects
None yet
3 participants
@Ceylo
Contributor

Ceylo commented May 12, 2014

On OS X 10.9 with Xcode, the SFML target does not build because of the following error:

cp -r /Users/ceylo/Development/SFML/include/SFML/* SFML.framework/Versions/2.1.0/Headers
/Users/ceylo/Development/SFML/build
usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-apvX] source_file target_file
       cp [-R [-H | -L | -P]] [-f | -i | -n] [-apvX] source_file ... target_directory
make: *** [SFML_buildpart_0] Error 64
Command /bin/sh failed with exit code 2

Replacing line 240 in CMakeLists.txt with:
COMMAND pwd && cp -r ${PROJECT_SOURCE_DIR}/include/SFML/* SFML.
shows that the working directory is wrong: it's /Users/ceylo/Development/SFML/build but it should be /Users/ceylo/Development/SFML/build/Debug.

However simply adding ${CMAKE_BUILD_TYPE} won't do it because when with Unix Makefiles as build system, no Debug subdirectory is created.

What is reliable and could be used are the $<TARGET_FILE_DIR:target> variables.

@eXpl0it3r eXpl0it3r added this to the 2.2 milestone May 13, 2014

@eXpl0it3r eXpl0it3r added OS X labels May 13, 2014

mantognini added a commit that referenced this issue May 13, 2014

Merge pull request #596 from Ceylo/bugfix/595_OSXFrameworkCreation
#595 Fix build of the SFML target on OS X with Xcode

Nevertheless, Xcode generator is not officially supported by SFML

@mantognini mantognini added the resolved label May 13, 2014

@mantognini

This comment has been minimized.

Show comment
Hide comment
@mantognini

mantognini May 13, 2014

Member

PR #596 fixed it and was merged. See discussion over there for more details.

Member

mantognini commented May 13, 2014

PR #596 fixed it and was merged. See discussion over there for more details.

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