draft for 10.x and add pre 10.x support later, this way
at least you can get going.
Best,
Maik Beckmann
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ a
2010/10/19 Michael Wild :
>
> While I agree that it should be added to the documentation of find_package,
> it is what most people would expect (except when they get bitten by it). Most
> people would be pretty stumped if CMake wouldn't search in the installation
> prefix.
>
> My 2 cents...
I d
This is not a question but a finding during a debugging session I like
to share and a documentation enhancement request.
We have a number of projects that reside in different repositories
including library projects that are chained up by find_package in
conjunction with -config.cmake files th
Thank you for the pointer.
I would be surprised if these problems aren't caused by the same bug.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic
The problem seem to be triggered the fact that the toplevel
CMakeLists.txt (
http://gitorious.org/hdf5/hdf5-v18/blobs/master/CMakeLists.txt )
contains
PROJECT (HDF5 C CXX)
and another CMakeLists.txt in a subdirectory (
http://gitorious.org/hdf5/hdf5-v18/blobs/master/hl/fortran/CMakeLists.txt
)
This is the generated CMakeFortranCompiler.cmake
http://pastebin.com/TrUjF6Bh
As you're can see CMAKE_AR is set to ""
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
Hello,
I'm building this
http://gitorious.org/hdf5/hdf5-v18
on windows using msvc and intel's fortran compiler in a minimal cygwin
environment with the Unix Makefile generator. It fails because for
some reason cmake decides to use ar to create a static library (which
isn't even installed), wher
Am 12.05.2010 09:02 schrieb Vladimir Grebenschikov :
>hi
>
> Do you have any results regarding converting ctest results into jnuit
> ones (or any other compatible with hudson) ?
I got some bascis to work, but never finished it. I just attach the
little test project I used back then.
The cmake si
2010/3/3 Bill Hoffman :
> At 4:30, I am going to be interviewed for FLOSS Weekly.
wow!
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check
2009/11/22 Taesoo Kwon :
> I am sorry that this should be an recurring question.
> But I wasn't able to find any working solution after hours of search.
>
> What I tried is as follows:
>
> /root/CMakeLists.txt
>
> set(CMAKE_CXX_COMPILER mpic++)
> set(CMAKE_C_COMPILER mpicc)
The CMakeLists.txt file
2009/11/16 Brad King :
>
> Please update this issue:
>
> http://www.cmake.org/Bug/view.php?id=9450
>
> Thanks,
> -Brad
Done, thanks for the pointer
-- Maik
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.
Oops, missed to cc to the mailing list
2009/11/16 Maik Beckmann :
> 2009/11/16 Bill Hoffman :
>> But, that is not happening in my script. It is ending up on the correct
>> my.cdash.org LAPACK dashboard when I run this script. I am sure there is a
>> bug in here somewhere
2009/11/16 Maik Beckmann :
> 2009/11/16 Bill Hoffman :
>> http://my.cdash.org/viewNotes.php?buildid=38044
>>
>> If nothing is checked out, it will checkout the code, then read the config
>> file after that.
>
> Checking your script now..
I see, CTEST_PROJECT_NAM
2009/11/16 Bill Hoffman :
> http://my.cdash.org/viewNotes.php?buildid=38044
>
> If nothing is checked out, it will checkout the code, then read the config
> file after that. I think I may close that bug. Can you describe exactly
> what is not working for you?
>
I get this error message
{{{
Canno
>> http://public.kitware.com/Bug/view.php?id=5041
>> ? (ctest -S fails on initial checkout, because it doesn't find
>> CTestConfig.cmake, since it isn't present when ctest is started)
>>
>
> I usually put something like this in the script:
>
> if(NOT EXISTS "${CTEST_DASHBOARD_ROOT}/${CTEST_DIR_NAM
2009/11/14 Bill Lorensen :
> IN itk this is what we typically do in ctest scripts.
>
> After
> CTEST_CONFIGURE (BUILD "${CTEST_BINARY_DIRECTORY}")
> place
> CTEST_READ_CUSTOM_FILES("${CTEST_BINARY_DIRECTORY}")
>
Sweet! This solves the CTestCustom.cmake issue with ctest -S.
Is there a similar work
Well well...
After I did this
{{{
--- Source/CTest/cmCTestTestHandler.cxx 25 Jun 2008 13:51:45 - 1.68.2.3
+++ Source/CTest/cmCTestTestHandler.cxx 11 Nov 2009 18:38:38 -
@@ -413,7 +413,7 @@
this->TestResults.clear();
- this->CustomTestsIgnore.clear();
+ //this->CustomTestsIgnore
Ok, it works like this:
cmCTest::ReadCustomConfigurationFileTree searches for
CTestCustom.(cmake|ctest) and reads it. If found, this code the inte
same method
if ( found )
{
cmCTest::t_TestingHandlers::iterator it;
for ( it = this->TestingHandlers.begin();
it != this->TestingH
This is a screenshot
http://imagebin.ca/view/TtO6Iu.html
of an eclipse gdb session, which show that the already populated
CustomTestsIgnore
vector is cleared.
I don't know if this is the source of the bug, since it should be refilled in
cmCTest::PopulateCustomVector(..)
but the cmMakefile in
Hello,
CTEST_CUSTOM_TESTS_IGNORE
Having a CTestCusom.cmake file works fine when running
make test
ctest
see:
http://pastebin.ca/1666592
But it's content is ignored when the build is scripted via ctest -S.
This is the log for ctest --debug -VV -S
http://pastebin.ca/1666597
as you can see,
hm, looks like LC_MESSAGES=C isn't enough, all compiler output has to be ascii.
LANG=C works.
Knowing this, I like to point out that on this site
http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest
this statement
SET( $ENV{LC_MESSAGES}"en_EN" )
beside from it having to be
SET( ENV{LC_MESS
Ups, missing details:
- cmake-2.6.4
- cdash-1.4.2
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cma
I guess something in this chain
gcc->ctest->cdash
goes wrong. See the following example:
While this is what gcc outputs ( where LC_MESSAGES=C):
{{{
warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’
}}}
ctest makes this of it:
{{{
warning: format
<-30><-128><-104>%d<-3
Hello,
When running this script http://dpaste.com/118717/ via ctest -VV -S,
it fails with
{{{
Cannot instantiate test handler ctest_build
CMake Error at ctest_core.cmake:46 (ctest_build):
ctest_build CTEST_BUILD_COMMAND or CTEST_CMAKE_GENERATOR not specified.
Please specify the CTEST_CMAKE_GEN
This is what ifort /help has to say
{{{
/O1 optimize for maximum speed, but disable some optimizations which
increase code size for a small speed benefit
/O2 optimize for maximum speed (DEFAULT)
/O3 optimize for maximum speed and enable more aggressive optimizations
Hello fellow cmakers,
I've encountered a weired bug: Given that CMake is installed in
C:/Programme/CMake
and MATLAB's bin folder is on the path before cygwin's, cmake fails on
{{{
cmake_minimum_required(VERSION 2.6)
project(Foo C)
}}}
with
{{{
mkdir Debug
cd Debug && cmake -G"Unix Makefiles
Clinton Stimpson schrieb am Donnerstag 25 Juni 2009 um 16:38:
> On 06/25/2009 06:47 AM, Maik Beckmann wrote:
> > Hello,
> >
> > What about altering
> >SET (CMAKE_Fortran_FLAGS_INIT "/W1 /nologo /fpp")
> >SET (CMAKE_Fortran_FLAGS_RELE
Hello,
Right now mixing Fortran and C compiled with respectively ifort and cl on
windows doesn't work out of the box. The reason for this is conflicting
runtime libraries.
The default for cl and ifort is, without any flags given, to use LIBC.lib.
This the static single threaded version.
CM
Jesper Eskilson schrieb am Freitag 29 Mai 2009 um 16:49:
> I'm having some trouble in setting up our CMake-system to use MSYS
> Makefiles together with cl.exe. The environments seems all setup, cl.exe
Without looking at the error message you've posted, MSYS doesn't work with cl,
since msvc flags
Arjen Markus schrieb am Donnerstag 16 April 2009 um 12:07:
> On 2009-04-16 10:43, Maik Beckmann wrote:
> > MSYS has its own generator, so this should be
> > cmake -G "MSYS Makefiles"
>
> Hm, could that be the problem? I noticed that CMake is indeed reacting
> di
Arjen Markus schrieb am Donnerstag 16 April 2009 um 09:32:
> Hello,
>
> in the PLplot project I have run into a few problems with the MSYS
> environment under Windows XP. The first one is that the CMake variable
> MSYS does not get set properly - or else I am doing something wrong.
>
> Here is what
Brad King schrieb am Montag 16 März 2009 um 15:48:
> Maik Beckmann wrote:
> > I still didn't test whether fixed format file can include a free format
> > file, or vise versa. In this case having distinct lexers(and parsers?)
> > is the only reliable approach.
>
>
Brad King schrieb am Montag 16 März 2009 um 15:06:
>
> CALL FOO() ; MODULE mymod ! crazy, but possible
Damn, you are right.
> Perhaps it is simplest to use the file extension as a heuristic for now.
> At least some compilers require special flags to build ".f" as free format.
> If this becomes a
Brad King schrieb am Montag 16 März 2009 um 14:24:
> Maik Beckmann wrote:
> > The _third_ option is to make the lexer format agnostic and handle
> > formats at the parser code. This should work well, since we just have to
> > make sure that the valid MODULE und USE s
Maik Beckmann schrieb am Samstag 14 März 2009 um 00:02:
> However, a look at cmFortranLexer.cxx shows that BEGIN is defined as
> #define BEGIN yyg->yy_start = 1 + 2 *
> which IMHO means that the lexer can only have one state at a time. If
> str_dq or str_sq is set, the desired
Brad King schrieb am Freitag 13 März 2009 um 16:51:
> The full fix is of course to discard 'C'-prefixed comments completely,
> but that can only be done in fixed-form sources. Currently our lexer
> has code to support fixed-form files but it is never enabled. CMake
> does not know whether a sourc
Eric Noulard schrieb am Freitag 13 März 2009 um 19:00:
> which makes me think that ALL rules in the lexer are
> currently ignored
> because the start condition never gets activated.
> i.e. there should be some code that's tell the lexer that it is lexing
> a fixed format file.
>
> Note that this
Brad King schrieb am Freitag 13 März 2009 um 16:51:
> Actually, I cannot tell from a quick glance at the code how it ignores
> 'USE' keywords that appear after a ';' separator. It does not ignore
> 'MODULE' after ';'. Maik?
If a piece of code is identifed by the _lexer_ as being a comment, it is
2009/1/29 ankit jain :
> 2009/1/29 Maik Beckmann
>>
>> > but there is another function of a one header file which is called in
>> > the
>> > two C files. also it used to initialize a variable...
>>
>> If this is the case, you shouldn't have an
2009/1/29 ankit jain :
> hi all,
> i have a c file in a folder which contain the line #include "%h" which says
> compile the file with -I option with gcc to tell where %h is located.
> but in cmake as i already add the header files by defining the path through
> a variable and add it through includ
2009/1/29 ankit jain :
> thanks for the help. with ur advice iam able to remove the multiple
> declaration error of main by creating namespace.
Nice!
> but there is another function of a one header file which is called in the
> two C files. also it used to initialize a variable...
If this is the
Am Mittwoch 28 Januar 2009 schrieb ankit jain:
> Then how to include those files containg main() function. anyhow we have
> create a libraries for it. what is the way to create libraries from those.
Alter the source files to make them usable as part of a library and as a
program on its own.
#ifd
Am Mittwoch 28 Januar 2009 schrieb ankit jain:
> thanks maik fo rhte reply.
>
> but actually i have done something like this:
>
> add_library(myapp SHARED ${mypp_srcs})
>
> where myapp_srcs contain around 4 .C files.
>
> in this case how to do that
>
> Regards-
> ankit jain
>
Hm, you are a C++ new
Am Mittwoch 28 Januar 2009 schrieb ankit jain:
> hi all,
>
> in one of my folder i have three files. in each of them a main() function
> is defined. now on building it says that multiple declaration of main. if i
> compile the makefile using gcc only no such error had came.
> Guide me what to do?
>
谢歆 schrieb am Samstag 03 Januar 2009 um 16:22:
> hi,
>
> I decide to use cmake for an old FORTAN program what consists a lot of
> F extension source code and wrote a simple CMakelists.txt.
> Hoever, the default setting did not seem to support F extension.
CMake support the F extension.
>
> And wh
Am Mittwoch, 3. Dezember 2008 schrieb Javier Gonzalez:
> Hi all,
>
> I have a project that links to another project built with Fortran. My
> own project is a C++ project and I usually need to link against a
> fortran library of some sort to use the first one. I use gcc, so it
> usually is libgfortr
Am Dienstag, 2. Dezember 2008 schrieb Robert Dailey:
> Hi,
>
> I execute the following CMake code:
>
> list( LENGTH "foo;bar" listlen )
> message( ${listlen} )
>
> However, this results in the value "0" to be printed. I expect this to
> print "2". What am I doing wrong?
list takes a list-name, so
Am Montag, 1. Dezember 2008 schrieb Hendrik Sattler:
> Maik Beckmann schrieb:
> > Am Montag, 1. Dezember 2008 schrieb Micha Renner:
> >> Why is it helpful to know the location of the Windows-DLL during the
> >> build-process?
> >
> > mingw's linker ign
Am Montag, 1. Dezember 2008 schrieb Micha Renner:
> Why is it helpful to know the location of the Windows-DLL during the
> build-process?
mingw's linker ignores the import .lib and takes .dll directly.
___
CMake mailing list
CMake@cmake.org
http://www.cm
Christian Ehrlicher schrieb am Montag 27 August 2007 um 08:02:
> This is a long awaited feature request:
> http://www.cmake.org/Bug/view.php?id=4068
>
> Christian
I encountered this problem, wrote a patch and added it to
http://www.cmake.org/Bug/view.php?id=4068
Bill, please take a look. The p
Mathieu Malaterre schrieb am Donnerstag 16 Oktober 2008 um 15:42:
> Hi there,
>
> I have started a limited support for C# in my project:
>
> https://gdcm.svn.sf.net/viewvc/gdcm/trunk/CMake/FindCSharp.cmake?view=marku
>p &
> https://gdcm.svn.sf.net/viewvc/gdcm/trunk/CMake/UseCSharp.cmake?view=mark
Am Mittwoch, 24. September 2008 schrieb Jesper Eskilson:
> Don't be so sure. There are quite a few people wanting and working on a
> native Git port for Windows.
>
> OTOH, the Cygwin-port of Git works very nice.
>
> ( Fortunately for
>
> > me, windows is something that happens to other people :p )
Am Dienstag, 23. September 2008 schrieb Myers, Gary:
> I have been using the Fortran dependency generator named makedepf90
> (Erik Edelmann - 2.8.8) for years now. Recently, we have encountered a
> bug in this application (infinite loop within the parser). I noticed
> that Fortran dependencies ar
Am Dienstag, 23. September 2008 schrieb Arjen Markus:
> I do not know what the changes in the code actually are, but one major
> problem was that using the
> word "use" in comments caused a false dependency. I do not know about
> infinite loops though.
>
> Regards,
>
> Arjen
This bug was in cmake-
Am Montag 08 September 2008 schrieb Allen Barnett:
> Hi: I'm running CMake 2.6.1 on my Fedora 7 laptop. I guess I'm getting
> old because the default font size of the GUI is too small for me to
> read. In particular, the output window font is so small that the
> characters are not completely render
Am Freitag 20 Juni 2008 14:49:37 schrieb David Cole:
> Regardless of the answer to your original question, these variable names
> simply cannot be changed now.
Sure!
> There are too many scripts that run dashboards that set them as is. The
> best we could do would be to invent duplicate variab
Am Sonntag 15 Juni 2008 11:35:49 schrieb Maik Beckmann:
> Hello,
>
> I wonder if the following name inconsistency is by intention or an
> oversight. In cmake scripts there are
> CMAKE_SOURCE_DIR
> CMAKE_BINARY_DIR
> and in ctest the counterparts are called
>
It works as follows
1. ctest runs
2. create an index of all generated xml files
{{{
Update.xml
Configure.xml
Test.xml
...
}}}
3. run an xsl processor on this index with an xsl file sucking in all listed
result files
{{{
Hello,
I wonder if the following name inconsistency is by intention or an oversight.
In cmake scripts there are
CMAKE_SOURCE_DIR
CMAKE_BINARY_DIR
and in ctest the counterparts are called
CTEST_SOURCE_DIRECTORY
CTEST_BINARY_DIRECTORY
Why not
CTEST_SOURCE_DIR
CTEST_BINARY_DIR
??
Thanks
I got my head around this stuff and realized that the solution is far simpler
than I thought before. No changes to the cmake codebase are needed. I will
continue this thread during the next days...
Am Donnerstag 22 Mai 2008 16:29:51 schrieb Maik Beckmann:
> Hello again,
>
> Doing i
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
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
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
Am Mittwoch 28 Mai 2008 15:25:06 schrieb Bill Hoffman:
> Yup, sorry, won't work. Each target (library, exe) must be all fortran.
> The IDE does not support mixed CXX and Fortran. So, you would have to
> have:
>
>
>
> CMAKE_MINIMUM_REQUIRED( VERSION 2.6 )
>
> ENABLE_LANGUAGE( Fortran )
>
> ADD_LI
Am Mittwoch 28 Mai 2008 15:03:46 schrieb Allen Barnett:
> Hi: I have a project which consists of a C++ main and a set of FORTRAN
> computational routines which I'm trying to build on windows XP. I'm
> using visual studio 2008 (VC9) and the Intel FORTRAN compiler (10.1) on
> IA32. I'm also using CMa
Am Dienstag 27 Mai 2008 15:56:14 schrieb Brad King:
> Allan Odgaard wrote:
> > project(foo)
> > add_executable(foo MACOSX_BUNDLE main.cc)
> > add_custom_target(run_foo echo running foo DEPENDS foo)
[snip]
> > Without the MACOSX_BUNDLE setting of the target, or trying to build the
> > sa
Am Montag 26 Mai 2008 22:36:03 schrieb Alexander Neundorf:
> Second comment: pkg-config is not widespread outside of Linux (and maybe
> *BSD, don't know), so find modules should works also without pkgconfig
pkg-config on windows is a PITA!
> Third comment: I think much better than the somewhat c
Am Sonntag 25 Mai 2008 09:37:07 schrieb Andreas Schneider:
> Pau Garcia i Quiles wrote:
> > There is the unofficial http://code.google.com/p/cmake-modules/
>
> Where I'm the only developer and as nobody is interested in helping I
> update it rarly. So if someone is interested in helping let me know
Am Freitag 23 Mai 2008 10:15:59 schrieb Alan W. Irwin:
> Thanks, Maik, for your additional response. For now, I have only skimmed
> what you said and don't completely understand the implications, yet, but my
> first impression is it looks like something special for fortran *.mod files
> is done in
Am Freitag 23 Mai 2008 09:54:21 schrieb Aleix:
> Hi list,
>
> With the time, at work, I've been developing some finders
> (find_package-called script).
>
> I can see 2 issues here:
> - Everytime I need to use another library, I have to develop another finder
> (which might have been developed by so
Am Freitag 23 Mai 2008 08:57:21 schrieb Alan W. Irwin:
> On 2008-05-23 07:07+0200 Maik Beckmann wrote:
> >
> > All target directories, Fortran or not, contain a cmake_clean.cmake,
> > i.e. CMakeFiles/foolib.dir/cmake_clean.cmake
> > which in turn contains
> > {{{
Am Freitag 23 Mai 2008 01:08:46 schrieb Alan W. Irwin:
> On 2008-05-21 18:25-0700 Alan W. Irwin wrote:
> > I am finally working again on the CMake language support for Ada
> > (currently implemented just for the gcc gnatmake compiler). One of the
> > issues is the gnatmake compiler not only produc
Am Donnerstag 22 Mai 2008 15:31:23 schrieb Bill Hoffman:
> I suppose that would be myself and Ken. If you want to talk about major
> changes we could move the discussion to cmake-developers:
>
>
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Huh, I didn't know it.
__
Am Montag 19 Mai 2008 13:22:21 schrieb Maik Beckmann:
> Hi,
>
> I thinking about working on ant's junit xml format as a secondary output
> format of ctest. This way it would be much more convenient to integrate
> ctest results into one of the java centric/compatible dashb
Am Mittwoch 21 Mai 2008 04:59:37 schrieb Roger Martin:
> Hi,
>
> See related thread on OpenSceneGraph
> http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2008
>-May/011600.html
>
> I did as Philip suggested and made a small test project. and still
> got the same j option issue
The ctest code needs some love anyway...
-- Maik
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Am Montag 19 Mai 2008 14:02:17 schrieb David Cole:
> That's a great idea! Are cppunit and nunit output formats similar enough to
> junit that they could all be done at once...?
If we want to provide more than two output formats it might be best to
construct an intermediate representation (result
Hi,
I thinking about working on ant's junit xml format as a secondary output
format of ctest. This way it would be much more convenient to integrate
ctest results into one of the java centric/compatible dashboards.
The idea came to my mind when considering hudson
(https://hudson.dev.java.net/
re-post: did send it Bill only, sorry.
Am Montag 19 Mai 2008 00:29:43 schrieb Bill Hoffman:
> Perhaps it is better to use a make that does not do this. mingw-make,
> cygwin make, native win32 gmake. I am not sure you can completely avoid
> / type arguments in the entire tool chain for windows.
>
Am Sonntag 18 Mai 2008 22:35:53 schrieb Stefan Buschmann:
> Hi,
>
> I don't know ifort, but I had the same problem with Makefiles and MSYS a
> while ago.
>
> > Since it works with cygwin I assume ifort knows cygwin and handles the
> > forward slash right. Does anyone know if ifort has a flag or en
Hello List,
Today I found the reason why the MSYS generator fails with ifort.
This line
ifort -fpp test.f
works at the standard cmd, the cygwin shell and msys shell. But this one
ifort /fpp test.f
fails when doing it in msys, because /fpp is considered as an file and ifort
wants to com
Miguel A. Figueroa-Villanueva <[EMAIL PROTECTED]> writes:
>
> Hello,
>
> I recently updated my cmake installation from cvs and now I can't get
> it to configure for 'Unix Makefiles'. I am now getting this error:
>
> ...
> Performing Test curl_cv_recv
> Performing Test curl_cv_recv - Failed
> CM
Am Samstag 17 Mai 2008 23:22:02 schrieb Hendrik Sattler:
> Maik Beckmann schrieb:
> > However, this
> > SET PATH=.;C:\mingw\bin;C:\cmake\bin
> > looks strange, please try
> > SET PATH=%PATH%;C:\mingw\bin;C:\cmake\bin
> >
> > I use the combination WinXP
Am Samstag 17 Mai 2008 18:11:02 schrieb Phil Pellouchoud:
> I saw somewhere online talk about "process_begin" and being a path issue
> (i.e. finding the wrong tools, etc...) for a different problem. So I
> had adjusted my path (SET PATH=.;C:\mingw\bin;C:\cmake\bin). But still
> no luck...
>
> -ph
Am Freitag 16 Mai 2008 22:58:34 schrieb Brad King:
> Maik Beckmann wrote:
> > Well, boost.python fails to compile due to a missing assignment operator.
> > However, something like this
> > struct Foo { std::vector Foos};
> > is IMHO just wrong and should be cor
Am Donnerstag 15 Mai 2008 20:45:09 schrieb Maik Beckmann:
> I'll configure my gcc installation to use concepts-checks and I'll do some
> testing on the code at my workspace (i.e. boost) just to see how common
> this kind of STL abuse is.
Well, boost.python fails to compi
Am Donnerstag 15 Mai 2008 17:16:32 schrieb dizzy:
> Seems CMake is violating ISO C++ then. You may not instantiate standard
> library templates of incomplete types (for example, even "struct A {
> std::auto_ptr a; };" is invalid, C++0x will have an exception to that
> for shared_ptr<>, but for the
Hi all,
I just download the gcc-4.3 binary distribution of mingw. It fails to
compile CMake due to
{{{
class cmSourceGroup
{
...
std::vector GroupChildren; // cmSourceGroup is incomplete!
};
}}}
since libstdc++ is compilied with --enable-concept-checks.
Is gcc right? By default concept-chec
Am Mittwoch 14 Mai 2008 08:12:32 schrieb hsanson:
> I am following the instructions in this page to check for some header
> files and fucntions
> "http://www.cmake.org/Wiki/CMake_HowToDoPlatformChecks"; but so far it is
> not clear, at least to me, how the configure.h.cmake file mentioned is
> crea
Am Donnerstag 01 Mai 2008 19:04:39 schrieb Convey Christian J NPRI:
> I'm using cmake version 2.7-20080501, and I'm having trouble setting
> CMAKE_Fortran_FLAGS. Any suggestions about what I'm doing wrong?
>
> Here's my CMakeLists.txt file:
>
> SET(CMAKE_Fortran_COMPILER "/usr/bin/f77")
> SET(CMAK
Am Donnerstag 01 Mai 2008 15:30:58 schrieb Convey Christian J NPRI:
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Maik Beckmann
> > Sent: Thursday, May 01, 2008 8:43 AM
> > To: cmake@cmake.org
> > Subject:
Am Donnerstag 01 Mai 2008 14:20:20 schrieb Convey Christian J NPRI:
> I've read that CMake 2.6 gives full support for building Fortran 90, but
> does it handle Fortran 77 equally well?
Yes.
> And are there any tricks I should know about for building F77 code with
> CMake and g77 on Linux?
Just s
Hello,
I know this topic isn't new, but I like to bring it up again.
>From
Modules/readme.txt
I get the following. A Find*.cmake file should _always_ set the plural forms
like:
XXX_INCLUDE_DIRS
XXX_LIBRARY_DIRS
...
while the singular forms are appropriate for UI entries and internal us
Am Mittwoch 23 April 2008 22:39:23 schrieb Jason Riedy:
> Ok, the example I have up there *will* work because they're in
> alphabetical order. However,
> ADD_LIBRARY(c STATIC b.f90 a.f90)
> will not if a uses b. a.f90 is built first.
>
> In my actual code, the USE statements are in module proce
Am Mittwoch 23 April 2008 21:46:45 schrieb Jason Riedy:
> Say I have a line
> ADD_LIBRARY(c STATIC a.f b.f)
> where a.f produces module a, b.f produces module b and *uses*
> module a.
>
> Is this expected to work? Currently, cmake 2.6 doesn't detect
> the dependency between b.f and a.f.
Huh? T
Am Freitag 11 April 2008 01:36:26 schrieb Jun Sun:
> I am staring to use cmake for an existing project.
>
> We generate a config.cmake file under current build directory. We like
> to include "config.cmake" in the in-tree CMakeLists.txt. cmake complains
> about not able to find "config.cmake".
>
>
Am Samstag 05 April 2008 07:07:14 schrieb Kelly (KT) Thompson:
> I guess there are too many combinations to make everything work and I
> understand that IVF+MSVC is a lower priority for the CMake dev/testing
> team. Maybe I'll dig into the workings of CMake one of these
> weekends...
Cool
> As
Am Freitag 04 April 2008 23:11:22 schrieb Kelly (KT) Thompson:
> I've spent the last few days trying to convince CMake to configure a
> toy FORTRAN project without success. I'm hoping that someone on this
> list can point me in the right direction. Here are the details:
>
> System setup:
> Window
Hello List,
Even if the cmake video cast of the talk given by Bill at fosdem 2008 not
shown to be available here
http://fosdem.org/2008/media/video
it is:
http://ftp.heanet.ie/mirrors/fosdem-video/2008/maintracks/FOSDEM2008-cmake.ogg
The slides seem not to be available yet. For those who don'
Am Samstag 01 März 2008 19:44:36 schrieb Enrico Scholz:
> CMake is a tool written for developers. So you can expect that they have
> some understanding of grammar and semantics of a computer language.
At the moment I try to teach some long term MSVS Developers to use cmake.
They were scept
1 - 100 of 139 matches
Mail list logo
