Question about CMake and Boost
Moderator: PPS-Leaders
I already found out that Mac can be detected as "APPLE". And a ConfigMac.cmake has also been created. Unlike Ogre on Linux and Windows, there is only an Ogre framework available, with a unix executable and headers in it. Thats why no lib can be found there.
Anyway, after tons of tries, all prerequisites can be found now, and it also says "Build files have been written to ......". Every thing seems to be found. But there is still no executable. Does this error occur if it got a wrong Ogre lib path?
Anyway, after tons of tries, all prerequisites can be found now, and it also says "Build files have been written to ......". Every thing seems to be found. But there is still no executable. Does this error occur if it got a wrong Ogre lib path?
I hope it is clear to you that CMake does not create an executable? It only writes makefiles, visual studio files, code::block files, xcode files, etc.
There is an XCode project generator for CMake, but it does not seem to be available in my binaries. Maybe you have to get separately. Anyway the command line would be "cmake -G XCode .."
There is an XCode project generator for CMake, but it does not seem to be available in my binaries. Maybe you have to get separately. Anyway the command line would be "cmake -G XCode .."
http://www.xkcd.com/
A webcomic of romance, sarcasm, math, and language.
A webcomic of romance, sarcasm, math, and language.
I think that would be an additional feature. All cool one though, but I think it should first be working with plain Unix Makefiles, but I may also be wrong. Maybe XCode is the only way...1337 wrote:There is an XCode project generator for CMake, but it does not seem to be available in my binaries. Maybe you have to get separately. Anyway the command line would be "cmake -G XCode .."
"I'm Commander Shepard and this is my favorite forum on the internet."
I know so little about Mac, I couldn't even tell you whether makefiles work on. I hope they do. It would make things easier.
http://www.xkcd.com/
A webcomic of romance, sarcasm, math, and language.
A webcomic of romance, sarcasm, math, and language.
They do, most things do, which also work for Linux. But little things differ. Like applications and the location of utilities and libraries.1337 wrote:I know so little about Mac, I couldn't even tell you whether makefiles work on. I hope they do. It would make things easier.
"I'm Commander Shepard and this is my favorite forum on the internet."
Seems like the whole Mac thing is not that easy (never said that though).
Plugins for OGRE are supported via bundles. There is some code in Main.cc to find the bundle path, but I have no idea about that stuff. There's also some docs with CMake about it.
Then Chai reported that all libraries were found (they're all in usr, opt or sw) except OGRE and CEGUI due to the fact that they use frameworks (Cocoa if I'm right). I don't know why but I'm sure it has advantages.
Again, I'm sorry Chai, I cannot help you there. I wanted to have a quick look at library linking on Mac, but it's way too much for a has-never-used-a-Mac guy.
However I can tell that XCode projects should have way better support now because it uses multiple configurations (debug, release, etc.) like MSVC. And I have sorted that out. But it only works if the actual output directory is the CMake one plus the configuration name. For instance build/bin/Debug. With makefiles, you just have build/bin. I really that the CMake guys configured the XCode project like that too.
Plugins for OGRE are supported via bundles. There is some code in Main.cc to find the bundle path, but I have no idea about that stuff. There's also some docs with CMake about it.
Then Chai reported that all libraries were found (they're all in usr, opt or sw) except OGRE and CEGUI due to the fact that they use frameworks (Cocoa if I'm right). I don't know why but I'm sure it has advantages.
Again, I'm sorry Chai, I cannot help you there. I wanted to have a quick look at library linking on Mac, but it's way too much for a has-never-used-a-Mac guy.
However I can tell that XCode projects should have way better support now because it uses multiple configurations (debug, release, etc.) like MSVC. And I have sorted that out. But it only works if the actual output directory is the CMake one plus the configuration name. For instance build/bin/Debug. With makefiles, you just have build/bin. I really that the CMake guys configured the XCode project like that too.
http://www.xkcd.com/
A webcomic of romance, sarcasm, math, and language.
A webcomic of romance, sarcasm, math, and language.
maybe i'm missing something, but shouldn't it be enough for him to just build the whole thing with
?
Code: Select all
make -j2
There are only 10 types of people in the world: Those who understand binary, and those who don't.
no use if there is no ogre and cegui library...
http://www.xkcd.com/
A webcomic of romance, sarcasm, math, and language.
A webcomic of romance, sarcasm, math, and language.
Code: Select all
/* TODO: Check what this actually is and whether we need it or not */
#if 0
# if ORXONOX_PLATFORM == ORXONOX_PLATFORM_APPLE
# define ORXONOX_PLATFORM_LIB "OrxonoxPlatform.bundle"
# else
/* ORXONOX_PLATFORM_LINUX */
# define ORXONOX_PLATFORM_LIB "libOrxonoxPlatform.so"
# endif
#endif
http://www.xkcd.com/
A webcomic of romance, sarcasm, math, and language.
A webcomic of romance, sarcasm, math, and language.
I found out that Cmake probably can use mac frameworks as libs directly, by adjusting some variables. Anyway, I accidently deleted some files from the orxonox folder. So I was forced to run svn up. Now it seems that the paths of FindFOO are not correct anymore? Can someone tell me whether the problem is in the current branch, or I did something wrong?
There haven't been any changes since your last checkout.
But you can always delete the CMake Cache and try again (CMakeCache.txt), maybe that helps.
But you can always delete the CMake Cache and try again (CMakeCache.txt), maybe that helps.
http://www.xkcd.com/
A webcomic of romance, sarcasm, math, and language.
A webcomic of romance, sarcasm, math, and language.
Thx 1337!
Am I allowed to run "svn ci" for buildsystem2? I made some changes in several files to make it compile and created "ConfigMac.cmake" file.
Anyway, every dylib seems to have different bugs, either more frameworks are needed, or paths to libs are not correct, e.g. sys/wait.h instead of wait.h.
I am stuck in libutil.dylib now. Signalhandler.h cannot be linked correctly. It depends on Xlib.h and has an error that several X functions are declared but not implemented. The strange thing is, I looked into all dependency headers and cannot even find these mentioned functions. I am asking myself, where are the damned declarations????
BTW, guide for mac on wiki has been updated.
Am I allowed to run "svn ci" for buildsystem2? I made some changes in several files to make it compile and created "ConfigMac.cmake" file.
Anyway, every dylib seems to have different bugs, either more frameworks are needed, or paths to libs are not correct, e.g. sys/wait.h instead of wait.h.
I am stuck in libutil.dylib now. Signalhandler.h cannot be linked correctly. It depends on Xlib.h and has an error that several X functions are declared but not implemented. The strange thing is, I looked into all dependency headers and cannot even find these mentioned functions. I am asking myself, where are the damned declarations????
BTW, guide for mac on wiki has been updated.
Who is online
Users browsing this forum: No registered users and 1 guest