Closed GoogleCodeExporter closed 8 years ago
the project seems to be outdate there has been some changes now you have to
install XCode as an application from the App Store so the sdks are not longer
under the /Developer directory.
You have to open the file iOS.cmake and make the following change:
< set (CMAKE_IOS_DEVELOPER_ROOT
"/Developer/Platforms/${IOS_PLATFORM_LOCATION}/Developer")
---
> set (CMAKE_IOS_DEVELOPER_ROOT
"/Applications/Xcode.app/Contents/Developer/Platforms/${IOS_PLATFORM_LOCATION}/D
eveloper")
I still have some problems since building the generated project ends succesfuly
but no *.a file is being generated.
Original comment by leon.moc...@gmail.com
on 25 Apr 2014 at 4:28
I had to pass absolute paths to clang compilers to get cmake3 generating an
Xcode project. The attached file is a patch of my local changes.
Original comment by go.cuevo...@gmail.com
on 1 Jul 2014 at 3:39
Attachments:
Fixed as of rev:13
Original comment by wizzr...@gmail.com
on 24 Jul 2014 at 8:51
I am having problems passing the absolute paths to the clang compilers using
the diff file. I'm getting the error:
CMake Error at CMakeLists.txt:11 (project):
The CMAKE_C_COMPILER:
/usr/bin/clang
is not a full path to an existing compiler tool.
Tell CMake where to find the compiler by setting the CMake cache entry
CMAKE_C_COMPILER to the full path to the compiler, or to the compiler name
if it is in the PATH.
CMake Error at CMakeLists.txt:11 (project):
The CMAKE_CXX_COMPILER:
/usr/bin/clang++
is not a full path to an existing compiler tool.
Tell CMake where to find the compiler by setting the CMake cache entry
CMAKE_CXX_COMPILER to the full path to the compiler, or to the compiler
name if it is in the PATH.
This is really weird because when using command which clang it brings the exact
path that cmake believes is not an absolute path.
Does anyone know why this is happening?
Original comment by mytext...@gmail.com
on 29 Aug 2014 at 7:55
Original issue reported on code.google.com by
tim.klin...@gmail.com
on 13 Apr 2014 at 8:48