> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Alexander Neundorf
> Sent: Tuesday, May 22, 2007 8:15 PM
> To: cmake@cmake.org
> Subject: Re: [CMake] [Dev] CMake 2.5-20070519 and tool chain support
>
> Hi,
>
> On Tuesday 22 May 2007 10:32, Kishore
On 5/23/07, Alan W. Irwin <[EMAIL PROTECTED]> wrote:
On 2007-05-23 09:50+0800 Clark J. Wang wrote:
> In Cygwin environment I have a C source file named `grep.c' which needs
> `libpcre' to compile. The CMakeLists.txt writes:
>
> PROJECT(myGrep)
>
> SET(CMAKE_VERBOSE_MAKEFILE ON)
>
> FIND_PROGRAM
On 2007-05-23 09:50+0800 Clark J. Wang wrote:
In Cygwin environment I have a C source file named `grep.c' which needs
`libpcre' to compile. The CMakeLists.txt writes:
PROJECT(myGrep)
SET(CMAKE_VERBOSE_MAKEFILE ON)
FIND_PROGRAM(PCRE_CONFIG pcre-config)
IF(PCRE_CONFIG)
ADD_EXECUTABLE(grep_pcr
On 5/22/07, Clark J. Wang <[EMAIL PROTECTED]> wrote:
For PROJECT(project), what's the difference between CMAKE_SOURCE_DIR,
PROJECT_SOURCE_DIR and project_SOURCE_DIR? And XXX_BINARY_DIR?
I found quite a few of similar variables on the wiki page (
http://www.cmake.org/Wiki/CMake_Useful_Variable
In Cygwin environment I have a C source file named `grep.c' which needs
`libpcre' to compile. The CMakeLists.txt writes:
PROJECT(myGrep)
SET(CMAKE_VERBOSE_MAKEFILE ON)
FIND_PROGRAM(PCRE_CONFIG pcre-config)
IF(PCRE_CONFIG)
ADD_EXECUTABLE(grep_pcre grep.c)
SET_TARGET_PROPERTIES(grep_pcre
James Bigler wrote:
I have a some code that I need to test and I need to feed it a default
set of compiler flags. I'm trying to set CMAKE_C_FLAGS via the -D
system to override the default ones CMake provides.
SET(COMPILE_TEST_SOURCE ${CMAKE_BINARY_DIR}/test/compile-test.c)
FILE(WRITE ${CO
I think the only thing that will break is a MESSAGE(FATAL_ERROR call... And
that's not really convenient when you want to keep going.
Other than that, you have to use IF constructs within the loop to avoid
hunks of cmake script.
I could be wrong, though. See who else says what. :-)
HTH,
David
On Tuesday 22 May 2007 17:07, James Bigler wrote:
> Is it possible to break out of a for loop?
No.
Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Is it possible to break out of a for loop?
Thanks,
James
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
With latest CVS (in an attempt to see if the problem was fixed), I was
attempting the following:
SET_SOURCE_FILES_PROPERTIES(Somefile.dat PROPERTIES
MACOSX_PACKAGE_LOCATION Resources)
This works great and does exactly what I expected it would do (assuming
it doesn't copy each and ever
On 2007-05-22 12:56-0600 Joshua Jensen wrote:
Rob Mathews wrote:
Anybody out there used CMake to generate C# .vcproj files?
That is, I've got a large C++ code base, and a few C# projects on the
side, and I want to use CMake for the C# projects as well.
I'd like to know what ideas people have o
Rob Mathews wrote:
Anybody out there used CMake to generate C# .vcproj files?
That is, I've got a large C++ code base, and a few C# projects on the
side, and I want to use CMake for the C# projects as well.
I'd like to know what ideas people have on this, too. There are no
references to .
I have a some code that I need to test and I need to feed it a default
set of compiler flags. I'm trying to set CMAKE_C_FLAGS via the -D
system to override the default ones CMake provides.
SET(COMPILE_TEST_SOURCE ${CMAKE_BINARY_DIR}/test/compile-test.c)
FILE(WRITE ${COMPILE_TEST_SOURCE} "i
Anybody out there used CMake to generate C# .vcproj files?
That is, I've got a large C++ code base, and a few C# projects on the
side, and I want to use CMake for the C# projects as well.
Rob.
___
CMake mailing list
CMake@cmake.org
http://www.cmake
On 2007-05-22 13:53-0400 David Cole wrote:
They did not get rid of it... It's fairly new functionality.
Newer than the CMake you are using.
(What's the output of "cmake --version" for you?)
Update your CMake and you will get INSTALL(DIRECTORY...
:-)
All good advice. Also, Kent, have a look
They did not get rid of it... It's fairly new functionality.
Newer than the CMake you are using.
(What's the output of "cmake --version" for you?)
Update your CMake and you will get INSTALL(DIRECTORY...
:-)
On 5/22/07, kent williams <[EMAIL PROTECTED]> wrote:
No, not silly advice. I just us
No, not silly advice. I just use the documentation on cmake.org out of
habit, and they apparently don't keep it up to date. For a while,
apparently, during 2.4 CMake, there was an INSTALL(DIRECTORY ) form
available and they got rid of it.
A pity because other than that, there is no portable way t
Then the subject line of your original email is a typo? I'm sorry if I
offered silly advice, I thought you were using CMake 2.5-20060616...
On 5/22/07, kent williams <[EMAIL PROTECTED]> wrote:
Um, I use a newer CMake, just read the docs on CMake.org which are
apparently older?
On 5/22/07, Dav
Jacob,
Thanks. It's ok now.
Regards,
Liang
On 22/05/07, Jacob Foshee <[EMAIL PROTECTED]> wrote:
You should call target_link_libraries only after you have called
add_executable for the given project. Otherwise, CMake doesn't yet know
about the executable.
--
KDE China: http://www.kdecn.org
Q
Um, I use a newer CMake, just read the docs on CMake.org which are
apparently older?
On 5/22/07, David Cole <[EMAIL PROTECTED]> wrote:
20060616 is a snapshot from CVS that is almost a year old now. You should
use the --help with your local CMake for what existed in CMake as of that
time...
Or -
Hi Trevor,
On Tuesday 22 May 2007 11:34, Trevor Kellaway wrote:
...
> > > this, but no. Trying
> > > "-DCMAKE_TOOLCHAIN_FILE:string=Toolchain-Freescale-HC12.cmake" also
> >
> > I didn't test it yet under Windows, but actually relative
> > paths should work.
> > Does prepending ".\" help ?
>
> I t
You should call target_link_libraries only after you have called
add_executable for the given project. Otherwise, CMake doesn't yet know
about the executable.
On 5/22/07, Liang Qi <[EMAIL PROTECTED]> wrote:
Hi,
I am a new one for cmake. Now I am using Qt 4.3.0 rc 1 Commercial
Edition(VS2005)
Nevermind, I found it it was in the CVS
http://public.kitware.com/cgi-bin/viewcvs.cgi/Docs/cmake-syntax.vim?root=CMake&view=markup
I simply added two new operators:
$ cvs di
Index: cmake-syntax.vim
===
RCS file: /cvsroot/CMake/CMak
Hello there,
I would like to know how one is supposed modify the cmake syntax file:
http://www.cmake.org/CMakeDocs/cmake-syntax.vim
How can I submit my changes ?
Thanks,
--
Mathieu
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman
Hello Alan,
* Alan W. Irwin <[EMAIL PROTECTED]> [21-05-07 10:16]:
> CONFIGURE_FILE(
> ${CMAKE_CURRENT_SOURCE_DIR}/format/standard_eng.sty
> ${CMAKE_CURRENT_BINARY_DIR}/format/standard_eng.sty
> COPYONLY
> )
thx a lot for that tip. I am sure it will help me in the near future.
Best regards,
Alex,
> So you are not only cross compiling, you are also using a
> completely different toolchain. This means you have to write
> a cmake file which sets all the required cmake variables for
> this toolchain (like CMAKE_C_LINK_EXECUTABLE etc.). This
> usually either goes into the SYSTEM-COMPI
20060616 is a snapshot from CVS that is almost a year old now. You should
use the --help with your local CMake for what existed in CMake as of that
time...
Or - better yet - update to a more current CMake.
HTH,
David
On 5/22/07, kent williams <[EMAIL PROTECTED]> wrote:
According to the man p
According to the man pages for 2.4-patch 7 RC-6 on CMake.org, there is
a form of the INSTALL command for directories. After reading through
the description, I added a command to install a subdirectory into the
bin install directory:
INSTALL(DIRECTORY pipeline_approved DESTINATION bin)
i.e. pipe
Hi,
On Tuesday 22 May 2007 10:32, Kishore, Jonnalagadda (IE10) wrote:
...
> It would make it very easy for one to distribute the project with the
> respective cmake support files when cmake officially does not support
> the configuration. Or if the for some reason one wants to override the
> defau
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Alexander Neundorf
> Sent: Tuesday, May 22, 2007 7:35 PM
> To: cmake@cmake.org
> Subject: Re: [CMake] [Dev] CMake 2.5-20070519 and tool chain support
> So to make it short I suggest to set CMAKE_SYST
Hi Trevor,
On Monday 21 May 2007 18:00, Trevor Kellaway wrote:
> Alex,
>
> > > CMAKE_TOOLCHAIN_FILE that is in the current development CVS tree.
> >
> > - CMAKE_C_COMPILER - e.g. ppc_74xx-gcc
> > - CMAKE_SYSTEM_NAME - e.g. "Linux"
>
> OK, not sure I really understand the intention of CMAKE_SYSTEM
Hi,
I am a new one for cmake. Now I am using Qt 4.3.0 rc 1 Commercial
Edition(VS2005) + Microsoft Visual C++ 2005 Express Edition on Windows
XP SP2.
cmake 2.4 patch 6
I just used one example code of Qt 4, analogclock. Following is my
CMakeList.txt:
project (analogclock)
find_package(Qt4 REQUIR
For PROJECT(project), what's the difference between CMAKE_SOURCE_DIR,
PROJECT_SOURCE_DIR and project_SOURCE_DIR? And XXX_BINARY_DIR?
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
33 matches
Mail list logo
