Am 24.06.2019 um 16:42 schrieb Christopher Webster:
On 6/24/19 8:03 AM, Volker Enderlein wrote:
Am 24.06.2019 um 15:39 schrieb Christopher Webster:
Hi Christopher,
did you followed the instructions from
https://bitbucket.org/Coin3D/coin/wiki/BuildWithCMake
and cloned the repo, e.g. ran hg
Am 24.06.2019 um 15:39 schrieb Christopher Webster:
Hi Christopher,
did you followed the instructions from
https://bitbucket.org/Coin3D/coin/wiki/BuildWithCMake
and cloned the repo, e.g. ran hg clone https://bitbucket.org/Coin3D/coin
coin ?
As coin uses subrepositories the Download the compr
Hi,
I encapsulate the literal **project** call in a **macro** that is adding
some general settings required for every project setup.
This worked flawlessly and without warnings in the last CMake versions
since 3.4.
Beginning with CMake Version 3.15.0-rc1 the following warning pops up:
No
ciated are interpreted as a C/CXX project. Once I remove this it is
interpreted correctly as a Fortran project.
Magne
Magne Rudshaug, Ph.D. | Principal Scientist | Computational Materials Processing
Institute for Energy Technology | www.ife.no |+47 481 77 495
-Original Message-
From: Volke
Hi,
how does the project command looks inside your CMakeLists.txt file?
project( LANGUAGES Fortran) should work
Cheers Volker
Am 15.11.2018 um 14:35 schrieb Magne Rudshaug:
Hi,
In some of my Fortran projects I have Windows resource files of type
.rc associated. Just listing this file along
Hi Michael,
I use the CMake generator toolset option "-T host=x64" when generating
the solutions to force the 64 bit compiler being used.
Cheers, Volker
Am 21.09.2018 um 16:13 schrieb Michael Jackson:
The easy answer is to use “ninja” from a VS tools X64 Native command
prompt. For those th
(build_script).
This is a starting point for you how to formulate your CMake call.
With the information within the before_build & build_script section;
how do I formulate the CMake call, as to compile ?
Thank You.
On 8/3/2018 2:48 AM, Volker Enderlein wrote:
If you go to https://githu
40 schrieb CrestChristopher:
Sorry, what is this information for; and how can it be used within the
`build_script` section in the appveyor.yml file ?
On 8/2/2018 9:30 AM, Volker Enderlein wrote:
Please have a look into the appveyor.yml file under section
build_script: you see the typical invocation of
/2018 5:20 PM, Volker Enderlein wrote:
Am 31.07.2018 um 06:17 schrieb CrestChristopher:
Hi, I'm a beginner to CMake and for weeks I've been trying to
compile a CMake file which I found on a github repository. All I
can say is I have a CMakeLists.txt file but I don't know how to
Am 31.07.2018 um 06:17 schrieb CrestChristopher:
Hi, I'm a beginner to CMake and for weeks I've been trying to compile a
CMake file which I found on a github repository. All I can say is I
have a CMakeLists.txt file but I don't know how to compile and I hope
someone can help ?
Christopher
Y
Hi David,
Boost changed its naming scheme starting from version 1.66. So its not
your fault but the FindBoost.cmake does not know how to handle the new
scheme. Try to use one of the 3.11.0-rc[1-3] versions that has the
proper naming scheme handling of 1.66 or use the 1.65.1 that is the last
v
set_target_properties(target PROPERTIES LINK_FLAGS "/OPT:NOREF") should
work.
Am 13/02/2018 um 14:38 schrieb ThePhD:
I have a project where I attempt to add linker flags to a Visual
Studio project using
target_link_libraries(lib_target PRIVATE /OPT:NOREF)
But it seems like the `/` syn
Am 25/10/2017 um 11:36 schrieb Carlton Banks:
Is there some literature that desbribes how cmakelist has to be defined a big
system, that involve multiple smaller modules within the big module.
It depends, but maybe Mathieu Roperts presentation from CPPCON 2017
gives you some insights.
https
tin Larcher
European Commission
Joint Research Centre, T.P. 480
Directorate for Space, Security and Migration
Safety and Security of Buildings
I-21027 Ispra (VA) Italy
Phone: +39-0332-789563
________
From: Volker Enderlein [volker.enderl...@ifm-chemnitz.de]
Sent: 24
Am 24/08/2017 um 14:03 schrieb Volker Enderlein:
Am 24/08/2017 um 08:42 schrieb martin.larc...@ec.europa.eu:
*/usr/bin/cmake -E cmake_copy_f90_mod source/d
source/CMakeFiles/epx.dir/d.mod.stamp Intel Fortran Compiler*
Error copying Fortran module "source/d". Tried "source/D.mo
Am 24/08/2017 um 08:42 schrieb martin.larc...@ec.europa.eu:
*/usr/bin/cmake -E cmake_copy_f90_mod source/d
source/CMakeFiles/epx.dir/d.mod.stamp Intel Fortran Compiler*
Error copying Fortran module "source/d". Tried "source/D.mod" and
"source/d.mod".
what CMakeLists.txt does issue this line? L
Hi,
our project contains lots of autogenerated Qt files and when reading the
3.9 Release notes I was very excited about the new AUTOGEN_BUILD_DIR
property to speed up the build times (for constantly bulding debug and
release versions in case nothing has changed).
But it seems I cannot get it
Hello,
according to https://sourceforge.net/p/predef/wiki/Compilers/ you could
check with
check_cxx_source_compiles("
#if defined (_MSC_VER) && (_MSC_VER == 1900) && (_MSC_FULL_VER ==
190024210)
#else
#error compiler is not MSVC Update3
#endif
int main() {
retur
th x86 and ARM platforms, so I would use 2 CMAKE_BINARY_DIR, each
configured using a different toolchain:
x86 would use "android.toolchain.x86.cmake"
ARM would use "android.toolchain.arm.cmake"
Something like that. Is this best practice? What other advice would you offer?
Thanks in
in a non-standard place.
https://cmake.org/cmake/help/git-master/module/CPackIFW.html#variable:CPACK_IFW_ROOT
This feature available in 'master' branch and will be released with CMake 3.9.0.
03.04.2017, 19:44, "Konstantin Podsvirov" :
Hello Volker!
03.04.2017, 18:50, "
Am 12/04/2017 um 13:28 schrieb Olumide:
set(Libraries
ContinuumTransfunctioner${CMAKE_DEBUG_POSTFIX}
Transmogrifier${CMAKE_DEBUG_POSTFIX}
)
Hi,
you could add the configuration for a single library dependency.
target_link_libraries(your_target
debug ContinuumTransfunctioner${CMAKE_DEBU
Am 04/04/2017 um 11:17 schrieb Magnus Therning:
Robert Schwarzelt writes:
Hi all,
I need to implement a code export function, that will only export code used
in a specific project configuration.
For this purpose I want to use unifdef (http://dotat.at/prog/unifdef/),
which is capable of removin
Am 03/04/2017 um 12:30 schrieb Volker Enderlein:
Hi,
I'm facing problems using the packaging with CPACK.
I try to build three different packages, a MSI (via WIX), an IFW, and
a ZIP package.
According to the documentation I set the following variables in my
CMakeLists.txt (and a few
Am 03/04/2017 um 12:54 schrieb Domen Vrankar:
2017-04-03 12:30 GMT+02:00 Volker Enderlein
<mailto:volker.enderl...@ifm-chemnitz.de>>:
But when I checked the CPack*Config.cmake files none of the
entries above are referenced. After running the `cmake -G "Visual
Studio
Hi,
I'm facing problems using the packaging with CPACK.
I try to build three different packages, a MSI (via WIX), an IFW, and a
ZIP package.
According to the documentation I set the following variables in my
CMakeLists.txt (and a few more which are required):
set(CPACK_WIX_ROOT "C:/Temp/W
25 matches
Mail list logo