Hello,
Kitware maintains a separate release of Ninja in order to support Fortran:
https://github.com/Kitware/ninja
I kind of want to ask what Kitware changed, but I probably won't understand
the details. Instead, I was hoping someone could give me a toy example of a
Fortran program that cannot
On 16 December 2016 at 14:38, Brad King wrote:
> On 12/15/2016 09:10 PM, Daniel Carrera wrote:
> > set(CMAKE_Fortran_PREPROCESS_SOURCE
> > " -Mpreprocess-E
> > ")
> >
> > I added that line to PGI-Fortran.cmake and it seems to work.
>
> Great!
On 16 December 2016 at 17:18, Bill Hoffman wrote:
> On 12/16/2016 8:38 AM, Brad King wrote:
>
>> Great! I'll integrate that for CMake 3.8.
>>
> Daniel, do you think you could setup a dashboard so this stays working?
> https://cmake.org/testing/
>
> -Bill
>
Ok. I'll try. I need some help with th
On 15 December 2016 at 17:35, Brad King wrote:
>
> This is not a problem with Ninja or our branch of it, but rather with
> CMake's information about the PGI Fortran compiler not being updated
> to support the Ninja generator. One can see the value for a few other
> compilers (from commit 39ebfc7
On 4 April 2013 17:32, Matthew Woehlke wrote:
>
> cd ..
> rm -rf build
> mkdir build
> cd build
>
> ...? ;-)
>
> (If your build directories tend to be in the same place, you could easily
> write a shell function to do this, to save typing.)
Done.
I should have thought of that.
Cheers,
Daniel.
-
On 4 April 2013 12:41, Eric Noulard wrote:
> Yes I know.
> By suicidal I mean that the built tool will remove its own file
> (but not the CMakeLists.txt off course).
I see what you mean. The Makefile is killing itself. It is committing suicide.
Would it be a reasonable idea to delete CMakeCache.
On 4 April 2013 11:41, Eric Noulard wrote:
> You can perfectly add a custom target/command to do that,
> if you do out-of-source build then removing the build dir is ok.
Thanks. Yes, I am doing out of source builds.
> Now, this would be a one-shot suicidal target since this will
> basically eras
On 4 April 2013 11:40, Ansis Māliņš wrote:
> What would be the benefit of such a command besides syntax?
Only a small convenience, nothing big. I am used to typing "make
cleann" when I want to make sure that I am starting from a clean
slate. I also have my shell configured so that it warns me whe
Hi all,
Is it possible to ask CMake to make another "make clean" target that
clears *all* the CMake generated files including the cache? I am a bit
annoyed that the only way to clear everything is to basically run "rm
-rf *".
Cheers,
Daniel.
--
Lord of the rings calendar in your Linux/Unix/Mac te
Hi Johannes,
On 3 April 2013 17:44, Johannes Zarl wrote:
> Short answer: normally you don't and you shouldn't add statements to compile
> object files.
>
> CMake is a build system generator, not a build-system in itself. I.e. you only
> tell cmake "I want to build library A from source files a.cp
Hello,
Summary: How do I use CMake to compile object files? Or is this the
wrong question to ask? (i.e. *should* I be compiling object files?)
Details:
-
I am starting to learn CMake, so I am not even sure I am formulating
my questions the right way... I have a large Makefile that I want
OUBLE} CACHE STRING "Fortran double
> flags")
> endif()
>
> Here I also added "CACHE" so that this variable is stored for next runs
> of cmake. I think this is close to what you are asking for (and is the
> same behaviour you will have for FFLAGS and friends).
Hi everyone,
What is the difference between CMAKE_CXX_COMPILE_FLAGS and CMAKE_CXX_FLAGS?
The wiki only mentions CMAKE_CXX_FLAGS and CMAKE_C_FLAGS, and those
are clearly used for compiling. But if you Google for CMake examples
(e.g with MPI) you will quickly find CMake scripts that have
CMAKE_CXX_
ld have the effect you're seeking...
>
> HTH,
> David C.
>
>
> On Apr 1, 2013, at 3:54 AM, Daniel Carrera wrote:
>
>> Hi all,
>>
>> I am just getting started with CMake. Here is my question: Is there a
>> good way to have an external config file
Hi all,
I am just getting started with CMake. Here is my question: Is there a
good way to have an external config file that specifies both the
compiler an compile flags?
The program is compiled many times, and it makes sense to have the
compiler and flags in a config file rather than have them in
Hello all,
I am starting to learn about CMake. So far I have only written very
minimal CMakeLists.txt files. I am wondering how hard it would be to
make CMake read some configuration options for Fortran 95 from an
external file similar to this:
myprogram.conf
FC = mpif90
F77 = $(FC)
FFL
16 matches
Mail list logo
