Robert,
Thank you for the advice.
As I want to take account of compiler version, I overrided the
`Fujitsu-DetermineCompiler.cmake` file by copy-pasting and editing it in the
folder of `CMAKE_MODULE_PATH`. However, the installation
`Fujitsu-DetermineCompiler.cmake` file is always used instead.
On Wed, 2019-05-08 at 00:52 +0300, Maris Razvan wrote:
I apologize for the spelling error in the subject of this thread.
I was told that this sentence actually states that lines inside a
(single) command argument cannot end in a line comment.
I initially thought that "Command Arguments" in this s
I apologize for the spelling error in the subject of this thread.
I was told that this sentence actually states that lines inside a
(single) command argument cannot end in a line comment.
I initially thought that "Command Arguments" in this sentence means
the "section" that contains all the argume
hello,
I am using the following command to add a git submodule to an existing
repository:
add_custom_command(OUTPUT fetch
COMMAND git submodule add https://github.com/user/repo.git
)
add_custom_target(new DEPENDS fetch)
This is working as intended. Adding an already existing submodule
In the latest CMake documentation, the "language" section, the "Source
Files" paragraph there is the following sentence:
"Note that any source file line not inside Command Arguments or a
Bracket Comment can end in a Line Comment."
I think that source file lines inside "Command Arguments" can
On Tue, 7 May 2019 at 20:38, Angel Campoverde
wrote:
> Next time please ask what computer I am using.
CMake results are intrinsically compiler-specific.
Your issue is compiler-specific.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
p.s. Please, stop it.
--
Powered by www.kitware
Next time please ask what computer I am using.
On Tue, May 7, 2019 at 1:04 PM Mateusz Loskot wrote:
> On Tue, 7 May 2019 at 18:24, Angel Campoverde
> wrote:
> >
> > No, It does not work, I told Cmake to use c++ 20, but it still goes back
> to c++17. You can see what I get here:
> >
> > https://
On Tue, 7 May 2019 at 18:24, Angel Campoverde
wrote:
>
> No, It does not work, I told Cmake to use c++ 20, but it still goes back to
> c++17. You can see what I get here:
>
> https://pastebin.com/5ub18cMU
Next time, please specify what compiler you are using.
Best regards,
--
Mateusz Loskot, h
CMake hasn't been updated to be aware that XCode 10 added support for
C++20 (via -std=c++2a). I have opened a MR to correct this which you
can track at: https://gitlab.kitware.com/cmake/cmake/merge_requests/3294
On Tue, May 7, 2019 at 12:24 PM Angel Campoverde
wrote:
>
> Hi,
>
> No, It does not w
Hi,
No, It does not work, I told Cmake to use c++ 20, but it still goes back to
c++17. You can see what I get here:
https://pastebin.com/5ub18cMU
my CMakeLists.txt is here:
https://pastebin.com/3bwMKrWB
do you know what could be the problem?
Cheers.
On Tue, May 7, 2019 at 2:33 AM Mateusz Los
I was on vacation last week, so testing resumed Monday. All of the seven
machines running CTests say they are reporting their results to the
CDash server, and on the CDash machine I can see results like:
33 minutes ago: 1 test failed on Machine 3
1 hour ago: 23 tests failed on Machine 7,
etc.
On Tue, 7 May 2019 at 01:15, Angel Campoverde
wrote:
>
> I am looking at:
>
> https://cmake.org/cmake/help/v3.14/prop_tgt/CXX_STANDARD.html
>
> and I see that I can pass 20, for c++20. However I do not have that in my
> compiler,
> I only have c++2a and gnu++2a, this means that CMake goes back to
12 matches
Mail list logo
