hpp.
test.cpp and test.hpp do not depend on any other files.
But every time when I comment test.cpp test.hpp or uncomment
new_func.hpp regenerated and foo.cpp rebuild happened.
is it possible to fix this behaviour?
I use make file generatation.
>cmake --version
cmake version 2.7-20080530
> cat
Yes. me too. it's very annoying. If a cmakelists file is touched when I
build paraview (but individual projects are not actually changed), the
entire 120 odd project/targets need to be reloaded and its quicker to
just terminate the app and restart. For a while cmake did some sort of
macro wizar
Am Freitag 30 Mai 2008 02:13:09 schrieb Adam Weiss:
> Hey Folks,
>
> I'm new to cmake and am in the process of converting a Linux based project
> over to use it. The project I'm converting includes a lot of Matlab mex
> extensions. I've done a good deal of internet research (both archives of
> th
John Biddiscombe wrote:
Yes. me too. it's very annoying. If a cmakelists file is touched when I
build paraview (but individual projects are not actually changed), the
entire 120 odd project/targets need to be reloaded and its quicker to
just terminate the app and restart. For a while cmake did
Indeed, after upgrading to cmake 2.6.0 I don't have those problems anymore.
Thanks a lot!
David
Zitat von Bill Hoffman <[EMAIL PROTECTED]>:
John Biddiscombe wrote:
Yes. me too. it's very annoying. If a cmakelists file is touched
when I build paraview (but individual projects are not actual
Hi all!
I'm trying to build my project on Windows using "GNU Makefiles" and
cl.exe under Cygwin. I'm using CMake-2.6-patch 0 and Microsoft Visual
Studio 2008 Professional.
I know this issue has come up every now and then, and it seems that it
should not be too hard to set this up. However, aft
On 2008-05-30 12:50+0400 Dave Milter wrote:
The problem become arris on big project.
It used qt, and when I add new file, it regenerate all stuff,
like moc files, ui_*.h files and so on,
this lead to rebuild corresponding C++ files,
and this is too long for me, and I also do not see, why
this sh
Stefan Buschmann wrote:
Hi all!
I'm trying to build my project on Windows using "GNU Makefiles" and
cl.exe under Cygwin. I'm using CMake-2.6-patch 0 and Microsoft Visual
Studio 2008 Professional.
Here is my setup:
export CC=cl
export CXX=cl
export INCLUDE="C:\Program Files\Microsoft Visual
Hi,
I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
Fortran 10) project that needs to use the link flags "/libs:dll
/threads" (alternate "/MD"). I am generating a "Visual Studio 8 2005"
project. I have reduced the problem to a "hello world" F90 code:
program main
print
Am Freitag 30 Mai 2008 17:41:21 schrieb Kelly (KT) Thompson:
> Hi,
>
> I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
> Fortran 10) project that needs to use the link flags "/libs:dll
> /threads" (alternate "/MD"). I am generating a "Visual Studio 8 2005"
> project. I have
On 2008-05-30 18:00+0200 Maik Beckmann wrote:
Am Freitag 30 Mai 2008 17:41:21 schrieb Kelly (KT) Thompson:
Hi,
I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
Fortran 10) project that needs to use the link flags "/libs:dll
/threads" (alternate "/MD"). I am generating a
regex are driving me nuts... could someone please let me know what is
wrong with my 'REPLACE' expression.
Thanks !
FILE(READ /proc/cpuinfo cpuinfo)
STRING(REGEX REPLACE "\r?\n" ";" cpuinfo "${cpuinfo}")
SET(myoutput "")
FOREACH(line ${cpuinfo})
STRING(REGEX MATCH "processor" proc_line ${line})
Thanks! I finally got it to work now. The problem was that invoking the
script does not really "export" the variables to the shell - so in my
own tests, "cmake" had it's environment variables set right, because I
invoked it directly from the script, but when running "make" later, the
variables
Stefan Buschmann wrote:
Thanks! I finally got it to work now. The problem was that invoking the
script does not really "export" the variables to the shell - so in my
own tests, "cmake" had it's environment variables set right, because I
invoked it directly from the script, but when running "mak
Am Freitag 30 Mai 2008 20:36:02 schrieb Bill Hoffman:
> Stefan Buschmann wrote:
> > Thanks! I finally got it to work now. The problem was that invoking the
> > script does not really "export" the variables to the shell - so in my
> > own tests, "cmake" had it's environment variables set right, beca
On 2008-05-30 18:00+0200 Maik Beckmann wrote:
Am Freitag 30 Mai 2008 17:41:21 schrieb Kelly (KT) Thompson:
Hi,
I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
Fortran 10) project that needs to use the link flags "/libs:dll
/threads" (alternate "/MD"). I am generating a
Hi All,
I'm running an application that uses a handful of semi-standard
libraries (freetype, libpng, zlib). Before I switched over to cmake, I
was linking to the static version of those libraries, and my app seemed
to run fine on machines as long as it was a recent version of linux.
However,
On 30.05.08 17:06:28, Eric Torstenson wrote:
> Hi All,
>
> I'm running an application that uses a handful of semi-standard
> libraries (freetype, libpng, zlib). Before I switched over to cmake, I
> was linking to the static version of those libraries, and my app seemed
> to run fine on machin
18 matches
Mail list logo