On Thu, Aug 28, 2008 at 12:10 AM, Craig Miller
[EMAIL PROTECTED] wrote:
I've read good things about cmake and would like to start using it. I spent
the afternoon reading the online tutorials and trying to get a simple hello
world c++ project setup and running. I started with the documentation
2008/8/27 Vitor Vasconcelos Araujo Silva [EMAIL PROTECTED]:
Hello Eric,
Hi Vitor,
Well, that's what I needed. My Linux doesn't give me the DEB nor RPM
generators (NSIS also doesn't exists in my environment, but I knew that in
advance). So, my Linux environment probably lacks
Hi there,
While I am not a mac user myself, users reported to me that at
least in Tiger and Leopard, gl.h is located in directory GL
(as in any other *NIX), not directory OpenGL.
Is this a bug in the module? Or are there OS X systems out there where
gl.h is located under OpenGL?
TIA
Craig, here are some tips from using CMake that might help you get over the
hump.
You _first_ need to have a valid CMakeLists.txt file. The simplest file
would be:
# Start CMakeLists.txt
project(HelloWorld)
add_executable(HelloWorld main.cpp)
#End CMakeLists.txt
Put that in a folder called
Hm ok, found it by myself
I'm trying to install some generated files (example):
CMAKE_MINIMUM_REQUIRED(VERSION 2.4)
SET(XFILE foo.x)
SET(ZFILE foo.z)
SET_SOURCE_FILES_PROPERTIES(${ZFILE} PROPERTIES GENERATED TRUE)
ADD_CUSTOM_COMMAND(OUTPUT ${ZFILE}
COMMAND cp
ARGS ${XFILE} ${ZFILE}
DEPENDS
The header is located in a framework called OpenGL.framework and the include
style for frameworks is the name of the framework (minus the extension) and
then the header file, so on OS X the proper include would be:
#include OpenGL/gl.h
Sometimes having your own OpenGL.h header with the following
Mike Jackson wrote:
The header is located in a framework called OpenGL.framework and the include
style for frameworks is the name of the framework (minus the extension) and
then the header file, so on OS X the proper include would be:
#include OpenGL/gl.h
But do you know for a fact that it is
/System/Library/Frameworks/OpenGL.framework/Versions/A/Headers/gl.h
That is the path on both Tiger and Leopard. Don't know what to tell
you. It has been like this for at least 10.3 on up. I am not sure how
they are getting away with GL/gl.h ... WAIT... Is this an X11
Application?
In that
Fernando Cacciola wrote:
Mike Jackson wrote:
The header is located in a framework called OpenGL.framework and the
include
style for frameworks is the name of the framework (minus the
extension) and
then the header file, so on OS X the proper include would be:
#include OpenGL/gl.h
Hmmm,
On Thu, Aug 28, 2008 at 5:12 AM, Vandenbroucke Sander
[EMAIL PROTECTED] wrote:
-Original Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: woensdag 27 augustus 2008 14:37
To: Vandenbroucke Sander
Cc: cmake@cmake.org; Brad King
Subject: Re: [CMake] re-config on make
Vandenbroucke Sander wrote:
Hi,
Sometimes CMake re-configures my build tree when running make.
Unfortunately CMake uses wrong options, I normally set those on the
command line. This forces me to re-config rebuild my entire source
tree. This is a bit annoying since, in most
Mike Jackson wrote:
/System/Library/Frameworks/OpenGL.framework/Versions/A/Headers/gl.h
That is the path on both Tiger and Leopard. Don't know what to tell you.
It has been like this for at least 10.3 on up. I am not sure how they
are getting away with GL/gl.h ... WAIT... Is this an X11
Now we're getting somewhere...
Which 2.4 are you on?
To force caching of -D variables with older cmake versions, specify a type
for each one (the :STRING in the modified version below). Also, I would
put the -D values before naming the source directory:
cmake -G MSYS Makefiles
Question:
What about those of us that do not want the header files compiled (no
pre-compiled headers, etc.), but still want the folders to show up in Visual
Studio (or any other IDE)?
Personally, I think that having to add them as 'source' when they are
explicitly _not_ source but definitions
What about those of us that do not want the header files compiled (no
pre-compiled headers, etc.), but still want the folders to show up in Visual
Studio (or any other IDE)?
That is how it works in my example.
John
___
CMake mailing list
That would be 2.4 patch 7... :-( So I try the update first before adding the
:STRING.
Thanks!
From: David Cole [mailto:[EMAIL PROTECTED]
Sent: donderdag 28 augustus 2008 16:03
To: Vandenbroucke Sander
Cc: cmake@cmake.org
Subject: Re: [CMake] re-config
Which version of Qt are you using? Qt 4.x is only officially supported
on the native window system (Quartz/Carbon) NOT X11. Qt 3.x _may_ run
under X11 on OS X so I don't know.
If some one new to OS X just did a locate on gl.h then they may have
found the wrong gl.h, or they really are
On Aug 28, 2008, at 10:16 AM, John Drescher wrote:
What about those of us that do not want the header files compiled (no
pre-compiled headers, etc.), but still want the folders to show up
in Visual
Studio (or any other IDE)?
That is how it works in my example.
John
This is how I have
Dear list,
I am a bit confused on the use of add_custom_target, I hope someone can
help me.
Here is what I am trying to do:
I have a number of subdirectories that build libraries, and then I build
the final executable with a custom command (I am wrapping all the
libraries in a tclkit
Here is some valuable info:
cmake version 2.6-patch 1
system: Ubuntu Hardy
Giampiero
Giampiero Salvi wrote:
Dear list,
I am a bit confused on the use of add_custom_target, I hope someone can
help me.
Here is what I am trying to do:
I have a number of subdirectories that build libraries, and
My objection is to do thing following (taken from John's example):
ADD_EXECUTABLE( CropDICOMImages ${UPMC_CROP_SRCS}
${UPMC_CROP_MOC_SRCS} ${UPMC_CROP_HDRS}
${UPMC_CROP_MOC_HDR} ${UPMC_CROP_RC_SRCS} ${UPMC_CROP_UI_HDRS}
)
I would rather having something like this instead:
ADD_HEADER(
Mike Jackson wrote:
Which version of Qt are you using? Qt 4.x is only officially supported
on the native window system (Quartz/Carbon) NOT X11. Qt 3.x _may_ run
under X11 on OS X so I don't know.
We still use Qt 3.x as a matter of fact.
If some one new to OS X just did a locate on gl.h
On Aug 28, 2008, at 3:00 PM, Fernando Cacciola wrote:
Mike Jackson wrote:
Which version of Qt are you using? Qt 4.x is only officially
supported on the native window system (Quartz/Carbon) NOT X11. Qt
3.x _may_ run under X11 on OS X so I don't know.
We still use Qt 3.x as a matter of
On 28.08.08 10:16:48, BRM wrote:
My objection is to do thing following (taken from John's example):
ADD_EXECUTABLE( CropDICOMImages ${UPMC_CROP_SRCS}
${UPMC_CROP_MOC_SRCS} ${UPMC_CROP_HDRS}
${UPMC_CROP_MOC_HDR} ${UPMC_CROP_RC_SRCS} ${UPMC_CROP_UI_HDRS}
)
I would rather having something
Giampiero Salvi wrote:
Here is some valuable info:
cmake version 2.6-patch 1
system: Ubuntu Hardy
Giampiero
Giampiero Salvi wrote:
Dear list,
I am a bit confused on the use of add_custom_target, I hope someone
can help me.
Here is what I am trying to do:
I have a number of subdirectories
OK, as everyone else on the planet probably realized instantly, I now believe
this is a make issue, not a CMake issue. Sorry 'bout that.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Smith
Sent: Wednesday, August 27, 2008 6:09 PM
To:
Hello,
I have a sub-directory in my project, doc, which contains pod markup of a
manual page:
doc
doc/prog.pod
doc/CMakeLists.txt
I want to generate and install a manual page from this. The command to
generate a manual page is:
pod2man -s 1 prog.pod prog.1
...which creates prog.1 - the
prog.1 is a file, not a target.
Use INSTALL(FILES instead.
TARGETS is for CMake ADD_LIBRARY and ADD_EXECUTABLE targets.
HTH,
David
On Thu, Aug 28, 2008 at 5:16 PM, Matthew Gates [EMAIL PROTECTED]wrote:
Hello,
I have a sub-directory in my project, doc, which contains pod markup of a
Craig, Sending to the list as I have no idea about CMAKE_RC_COMPILER.
The only thing I could suggest would be the following:
Open up the Visual Studio Command Prompt and launch CMakeSetup.exe
from the command prompt. Maybe something in your environment is either
NOT getting picked up or
Thank you Mike. I deleted the cache related file/directory and tried again
by executing CMakeSetup.exe from within the Visual Studio 2005 Command
Prompt (which has all Visual Studio environment variables set). I receive
the same error message.
Craig
-Original Message-
From: [EMAIL
This has been seen before if you google a bit. What I could not find
was a solution.
Mike
Sent from my iPod
On Aug 28, 2008, at 17:58, Craig Miller
[EMAIL PROTECTED] wrote:
Thank you Mike. I deleted the cache related file/directory and
tried again
by executing CMakeSetup.exe from
Yeah, I did the same (google) yesterday and couldn't find an answer either..
so here I am with you fine folks. :-)
Craig
-Original Message-
From: Mike Jackson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2008 3:55 PM
To: Craig Miller
Cc: Mike Jackson; Cmake Mailing List
Sorry for not posting in-line, but the Yahoo! e-mail editor makes it quite
hard...
CMake does a wonderful job at _managing_ build systems and helping with
projects move between environments, and yes even IDEs, etc. It's one of the big
reasons I like it - the fact that I can run CMake and get
33 matches
Mail list logo
