Yep. When the install command is run there is a missing package of
files from the QtGui.framework/Resources/qt_menu which needs to be
copied into the CMake-Gui.app/Contents/Resources. I think I filed a
"bug" for this although technically CMake only supports Qt 4.3 which
never had a Cocoa version.
I downloaded/installed the Qt libraries (the Cocoa libs), and rebuilt CMake
2.8.0. I'm using a customized version of CMake 2.8.0 so the stock binaries
from Kitware won't work for my project. The gui builds correctly and I can
run the gui from the CMake 2.8.0.app bundle in the build directory.
On Sat, 2009-12-12 at 14:35 -0800, Alan W. Irwin wrote:
> On 2009-12-12 12:02-0500 Bill Hoffman wrote:
>
> > Some things just can not be done cross platform. For example reading/
> > writing the windows registry, creating an OSX application bundle, and
> > sym-links. Also, some computers don'
Michael Wild wrote:
You need to have Qt installed.
http://qt.nokia.com/products
If you only want to build Qt software (i.e. don't care about the IDE), make sure you only download the library package (163MB) and not the SDK (444MB).
You can also download the CMake binary for OSX from Kitware
You need to have Qt installed.
http://qt.nokia.com/products
If you only want to build Qt software (i.e. don't care about the IDE), make
sure you only download the library package (163MB) and not the SDK (444MB).
Michael
On 13. Dec, 2009, at 17:09 , Steven Wilson wrote:
> Do you have to do so
Do you have to do something special to turn it on when you build(2.8.0)
CMake on OS X? My bin directory that contains cmake/ccmake/etc... does not
contain a cmake-gui program.
Thanks,
Steve
On Sat, Dec 12, 2009 at 11:32 AM, David Cole wrote:
> cmake-gui is available on mac, Linux and windows
On Sun, Dec 13, 2009 at 8:20 AM, Mark Jones wrote:
> Hi David,
>
> Thank you for all of your help so far.
You're welcome...
Am I attempting to use cmake in a way that is incompatible with cmake, or in
> a way that it wasn't intended for? It is OK if I am attempting to use it in
> a way it isn'
Can you give exact steps to reproduce and tell me exactly how you are
observing the replacement?
i.e.:
- set your user PATH to something that is N characters long with M
semi-colon separated components
- look at "My Computer > Properties > Advanced > Environment Variables >
user PATH value" to see
Hi David,
I was using the latest installer that I downloaded from the cmake page:
http://www.cmake.org/files/v2.8/cmake-2.8.0-win32-x86.exe
I am using Windows XP SP3.
I have a relatively long PATH already. Is your PATH very long on the system
that you tried to reproduce this on? I wonder if t
Hi David,
I am up to date on my service packs. It is possible that something else
other than cmake is at fault here as I can not say with 100% certainty that
I could edit macros immediately before the cmake install (it has been weeks
since I last edited a macro), but I wanted to check with the li
On Friday 11 December 2009, Nicola Brisotto wrote:
> Hi,
> I want to crosscompile a project. I created a toolchain file. But I've
> problems because the linking step use the compiler to link. My need to uses
> another tool to link. How can I force cmake to use a different linker?
>
> I've posted
On Sunday 13 December 2009, Daniel Stonier wrote:
> I've been digging through the documentation, but I cannot seem to find
> anything which can read the value of a c style defined macro into a cmake
> variable.
>
> There's CheckSymbolExists, but that just flags the resulting cmake variable
> as tru
I've been digging through the documentation, but I cannot seem to find
anything which can read the value of a c style defined macro into a cmake
variable.
There's CheckSymbolExists, but that just flags the resulting cmake variable
as true or false. It doesn't actually read the definition into the
13 matches
Mail list logo