I looked around for precompiled header support and couldn't figure out
how/if it works for intel compilers.
The links such as:
http://www.mail-archive.com/cmake@cmake.org/msg05456.html appear to be
pretty MSVC centric and I don't think the stdafx.cpp approach will work on
intel.
If there i
Eric Noulard wrote:
2009/2/26 Alex Flint :
Hi there,
I've noticed that when I run "make blah" then the makefile is
automatically re-generated if I've changed anything in CMakeLists.txt
since the last time I built "blah". However, if I add a new target to
CMakeLists.txt then I have to run cmake
Hello everybody,
I would like to know a little more about the MAKECOMMAND variable in CMake. I
have a parallel compiler I would like to use with CTest to speed up the
compilation.
I know what to put in this MAKECOMMAND variable to use my compiler but I do not
know how it is build by default,
However, I was not able to find this in the Changelogs leading from
2.6.2 to 2.6.3, but I may have overlooked it. If this is the case, then
"Sorry!".
Just for the record it is in the ChangeLog:
Changes in CMake 2.6.3 RC 5
...
- Fix Fortran compiler specified with -D issue
-Bill
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.
>
> I just tried these cases and gcc
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.
I just tried these cases and gcc chokes on both cases:
! main-free.f90
include 'fixed.f'
! main
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
Maik Beckmann wrote:
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 statements are catche
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 statements are catched. Remeber
Asmodehn Shade wrote:
I am currently converting my old cmake 2.4 scripts to cmake 2.6.3, as I
am enjoying the new possibilities offered by the export / import system
I previously implemented my self a little dirty workaround this
limitation... so I am pretty happy to see this coming along ;-)
Maik Beckmann wrote:
The _second_ option proposed in the book is to have two distinct fortran
lexers (and probably two parsers). This is the cleanest solution, but would
be engineered for this special problem, IMHO.
Fixed and free format are practically two different languages from the parsi
Bill Hoffman wrote:
> Bill Hoffman wrote:
>> Joachim Geiger wrote:
>>> Hello,
>>> this is more or less to document a bug in the cmake version 2.6.2 seen
>>> on AIX version 5.3 when using the option to redefine the fortran
>>> compiler. For example:
>>> 11:13> ../cmake-2.6.2-AIX-powerpc/bin/cmake ..
Bill Hoffman wrote:
Joachim Geiger wrote:
Hello,
this is more or less to document a bug in the cmake version 2.6.2 seen
on AIX version 5.3 when using the option to redefine the fortran
compiler. For example:
11:13> ../cmake-2.6.2-AIX-powerpc/bin/cmake ../test_project
-DCMAKE_Fortran_COMPILER=f95
Joachim Geiger wrote:
Hello,
this is more or less to document a bug in the cmake version 2.6.2 seen
on AIX version 5.3 when using the option to redefine the fortran
compiler. For example:
11:13> ../cmake-2.6.2-AIX-powerpc/bin/cmake ../test_project
-DCMAKE_Fortran_COMPILER=f95
What if you do thi
2009/3/16 Mattias Helsing
> Hi Ankit,
>
> ok, so we have problems with our terminologies. You can't link a shell
> script with anything!
>
> So back to guessing. This time I'm guessing that you (or your script)
> isn't setting LD_LIBRARY_PATH correctly. Could you check this?
>
> Mattias
>
> T
2009/3/16 Mattias Helsing
> Hello Ankit,
>
> I think I know what you are trying to do. Correct me if I'm wrong.
>
> Your CMake code produces an executable file (you can't run libraries
> from the commandline) and you want to produce a shellscript that calls
> this executable?
>
Thanks for the re
Hello,
this is more or less to document a bug in the cmake version 2.6.2 seen
on AIX version 5.3 when using the option to redefine the fortran
compiler. For example:
11:13> ../cmake-2.6.2-AIX-powerpc/bin/cmake ../test_project
-DCMAKE_Fortran_COMPILER=f95
-- The Fortran compiler identification is Vi
Hi Wim,
Try this:
FOREACH(file a.js b.js)
FILE(READ ${file} f0 )
SET( f1 "char* myFile = \r\n${f0}" )
STRING( REGEX REPLACE "\"" "\"" f2 "${f1}" )
STRING( REGEX REPLACE "\r?\n" "\"\r\n\"" f3 "${f2}" )
STRING( REGEX REPLACE "\r?\n.$" ";" f4 "${f3}" )
STRING( REGEX REPLACE " = ." "
Hi!
You may want to look at
http://www.cmake.org/pipermail/cmake/2009-March/027774.html I generate *.cpp
files from CORBA *.idl files before the project is compiled. The same you can
do for header files.
Exactly at PRE_BUILD - it works only on Visual Studio. Why no everywhere? I
also wonder.
19 matches
Mail list logo
