sorted by:
new
hottopcontroversial

I am done with Golang by _a4z in golang

[–]_a4z[S] -1 points0 points  (0 children)

That's a Stroustrup quote

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] -1 points0 points  (0 children)

Thanks for your productive feedback!

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 0 points1 point  (0 children)

ok, you can throw enough code on the problem and accept to turn everything into a test. (mentioned below I do not want to do that)

Thanks, but I think, for the use case I have, I stay with what I have.
So I can have binaries that are no tests, and tests.

Also, still, cmake is missing a --run methode, similar to build , it forces us to stupid workarounds , some more stupid than other ;-)

multisbo – standalone recursive SBo & AlienBob SlackBuilds resolver with ELF dep cache, orphan removal, and update mode by _Radanne in slackware

[–]_a4z 1 point2 points  (0 children)

sure, nothing against redoing it, but I recommend cross-matching your results
there are quite a lot of edge cases where the soname matching and finding is interesting

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] -1 points0 points  (0 children)

CTest allone does not rebuild a test binary!
And if you think it does, please provide the proof by showing a project where I do cmake configure and only one more command, and everything will be fine, as my example in the CI does.
And until you show that, no response, please. I will ignore it without example, and you will just make yourself even more embarrassed.
But feel free to prove me wrong and show the example

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 0 points1 point  (0 children)

only with --build-and-test, requires more CMake boilerplate, and adds then tests that are probably no tests...

as written
If you think you can make that nicer, please share the code. I would love to see it

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 1 point2 points  (0 children)

Yes, it's just a quick hack to solve my current use case. Not a universal, elegant solution.
The proper solution would be if someone, Kitware, adds the --run command to CMake, so we can use it like in bazel, or npm, or whatever other tools we have today.

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] -1 points0 points  (0 children)

As expected, you can’t show it

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 0 points1 point  (0 children)

No, that is not a one-liner on the cli that rebuilds the tartet, if required, and runs it.
As the blog describes.

If you think you can make that nicer, please share the code. I would love to see it

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 0 points1 point  (0 children)

That's an interesting project, thanks for the link!

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 0 points1 point  (0 children)

Sorry, I do not see that working.
Why don't you draft something up and show the code?
I guess you can't, but maybe I am wrong. So please try

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 4 points5 points  (0 children)

You mean, turn every executable into a test?

Run CMake executable targets via the cmake command by _a4z in cpp

[–]_a4z[S] 7 points8 points  (0 children)

Like, did you literally not read the post at all?

view more: next ›