hi, all
I installed the lapack library on my fedora box but the cmake seems
can't find it. Can someone provid a find file for that package? Thanks
a lot.
zl2k
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
I added a CTestCustom.ctest file to my build directory as suggested on
the CMake website, and it doesn't appear to be doing what it is supposed to.
I'll include my CTestCustom.ctest file below, but basically I want to
suppress warning messages that occur because of third party libraries
built
Von: "Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA" <[EMAIL PROTECTED]>
> We had similar problem. It turned out that it takes
> a long time for it to appear on the website (up to 10 minutes).
> You can change this behavior by changing Project.xml file inside
> of your Dart2 project direc
We had similar problem. It turned out that it takes
a long time for it to appear on the website (up to 10 minutes).
You can change this behavior by changing Project.xml file inside
of your Dart2 project directory. Search for
"Process queued task every 10 minutes" and change the value.
Mike Jackson wrote:
On Jan 3, 2007, at 9:51 AM, Bill Hoffman wrote:
Mike Jackson wrote:
Bill,
icpc is the Intel C++ compiler. icc is the C compiler.
Exactly.. the flags _do not_ match. If you look closely in all the
mumbo jumbo.. in the compile the flag is "-wd981" but in the link
phase
On 1/3/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
Why does the cont. build need a CTestConfig.cmake but the nightly build
works ok if the settings are inside the CMakeLists.txt ?
CTestConfig.cmake is used by ctest *before* a configure run during a
dashboard execution. This would also w
Alexander Neundorf wrote:
Von: Bill Hoffman <[EMAIL PROTECTED]>
An: Roman Yakovenko <[EMAIL PROTECTED]>
Roman Yakovenko wrote:
Thanks for help. I think I have enough information to deal with the
problem.
You should make a feature request in the bug tracker. The code for
bui
On Jan 3, 2007, at 9:51 AM, Bill Hoffman wrote:
Mike Jackson wrote:
Bill,
icpc is the Intel C++ compiler. icc is the C compiler.
Exactly.. the flags _do not_ match. If you look closely in all the
mumbo jumbo.. in the compile the flag is "-wd981" but in the link
phase the flag is "d981"
Mike Jackson wrote:
Bill,
icpc is the Intel C++ compiler. icc is the C compiler.
Exactly.. the flags _do not_ match. If you look closely in all the
mumbo jumbo.. in the compile the flag is "-wd981" but in the link
phase the flag is "d981". note the missing characters up front. This
is caus
Hi!
I have several directories in my src dir, like:
src /
dir_a
dir_b
I have sources in all of them: src, dir_a, dir_b.
In CMakeLists in src I have eg.:
set(sources
foo.cpp
dir_a/bar.cpp
dir_b/ding.cpp
)
The .obj files are built CMakeFiles/project.dir/
and the tree is recreated, ie:
fo
Hi,
so it seems I got the cont. build basically working. It runs all 5 minutes,
updates, builds if necessary and submits the result to our dart2 server.
Problem: the data arrives at the server (in Temporary/Filexxx.xml.gz) but
doesn't seem to be processed. This means it stays there and doesn't a
Hi Alex,
thanks for your help.
Reinhard
On Tuesday, 2. January 2007 22:04, Alexander Neundorf wrote:
> Hi Reinhard,
>
> Von: Reinhard Thies <[EMAIL PROTECTED]>
>
> > Hello,
> >
> > I am quiet new to cmake. It looks very nice, at least what I have seen
> > so far.
> > I just want to convert some o
Hi,
I'm running nightly builds for some months now already, and have therefor
created a file CTestCustom.cmake, which contains upper error limit, exclude
regexps and other things like this.
In the top level CMakeLists.txt I have the settings for NIGHTLY_START_TIME,
DROP_METHOD, DROP_SITE, DROP_
Hi,
I'm currently setting up a continuous build and had a look at an example ctest
script:
http://public.kitware.com/KDE/Testing/Sites/dash17.kitware/Linux-Debian-gcc4.1/20060322-2101-Continuous/Notes.html
For a lot of the commands used there (CTEST_START(), _UPDATE(), _SLEEP() etc.)
I can't f
Von: Bill Hoffman <[EMAIL PROTECTED]>
An: Roman Yakovenko <[EMAIL PROTECTED]>
> Roman Yakovenko wrote:
> > Thanks for help. I think I have enough information to deal with the
> > problem.
> >
> You should make a feature request in the bug tracker. The code for
> building is already in ctest a
Von: Bill Hoffman <[EMAIL PROTECTED]>
> Bill Hoffman wrote:
...
> It should look for qmake4 after qmake, but it should also look for
> qmake4 if it finds a qmake that is qt3.
> Basically do the same thing that is done for qmake-qt4.
Ok, so
1) check for qmake
2) if found, check that it's a Qt4
16 matches
Mail list logo