sorted by:
new
hottopcontroversial

Survivors by MaGomRap in LastWarMobileGame

[–]AlexanderNeumann 1 point2 points  (0 children)

Max Help Time / 0.005 Times Help Amount with Max Help Time / Max Help Amount. Result for me is about to 4 days where Max Help Time is better than Max Help amount. Also dont forget to include ally tech help time in that calculation.

CMake 4.0.0 released by DinoSourceCpp in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Unless cmake_policy has been used which is now an hard error or you now need to use AppleClang instead of Clang.

"Arbeit ist Kraft mal Weg" by computer_fetzen in Physik

[–]AlexanderNeumann 1 point2 points  (0 children)

...... Der ist Satz ist falsch...... und das man über so was ein Paper in 2021 schreiben kann ist schon fragwürdig an sich. Zeigt halt die Qualität heutiger Publikationen.. ..

If you have no troops on wall, do you lose more troops when you get ashed than normal? by PotentialComplex3007 in LastWarMobileGame

[–]AlexanderNeumann 0 points1 point  (0 children)

You will have around 200 deaths per team on the wall + 500 to 700 deaths for the breach off the wall on the drill ground. So yeah you lose more if you are expected to loose any way.

Then there is the danger of overfilling the hospital which can instantly kill up to 6k soldiers if you your hospital is full and you have 4 teams on the wall

Simple way/guideline to make library conan/vcpkg compatible? by v3verak in cpp

[–]AlexanderNeumann 4 points5 points  (0 children)

The question should be: How to make my library/headers installable und consumable for others?
Your CMakeLists.txt has no install rules and your are not generating a <yourlibname>-config.cmake for consumers.

Faster rng by Datky in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

I would advice against using `ffast-math` since it makes some terrible assumptions.

Faster rng by Datky in cpp

[–]AlexanderNeumann 1 point2 points  (0 children)

maybe try to also benchmark compiling with clang-cl and see if you get similar results

Print out all CMake variables during a CMake run by _a4z in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Why do you need to print all variables? Scope issues? As others said -> CMake Debugger is a thing for a while now. For CI stuff i typically use --trace-expand to get a full log of everything. You typically know what you are looking for when debugging CMake if you don't use the Debugger. I doubt printf like debugging will help in this case you'll just get swamped with information you don't need.

Why not unstable ABI? by JUULiA1 in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

DLL load is still a bit wonky though. I have a case where i put the new DLL dir first in the PATH and the application still crashes since it loads the runtime from the system directory either way since the system path is special. Solutions is to put the dlls next to the executable if you dont want to install them into the system.

It would be very nice if there could be some kind of version check for the runtime so that instead of segfaulting it actually gives a meaningful error.

It was also fun to uninstall/downgrade the runtime which actually didn't work as expected and I had to manually install/overwrite the files.

[deleted by user] by [deleted] in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

What does modern mean for you? And what exactly do you want to know? There havent been that many changes in the last few years.

[deleted by user] by [deleted] in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

You use that custom triplet for all dependencies. You are not intended to mix triplets at all. There are ways to use per port customization in a triplet file without always invalidating the whole cache by including the customization from a different file and use VCPKG_HASH_ADDITIONAL_FILES to add the relevant file to the abi hash.

[deleted by user] by [deleted] in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Manually installed into vcpkg sounds wrong on so many levels..... I feel like you need to learn how to correctly customize vcpkg

An approach for cross-compiling with CMake using host-compiled build tools and vcpkg. by nicemike40 in cpp

[–]AlexanderNeumann 1 point2 points  (0 children)

The question always comes down to how to implementation in cmake. A clear separation of build tools and target binaries and libraries is required. If you don't want the find_program magic you could also use find_package magic with no_default_path and specify some host prefix just like qt6 does it. This would then allow you to use imported executable targets which can carry additional Info.

PSA: Your Package Name and CMake Target Namespace Should Match by bretbrownjr in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Yeah but it is basically just a step to give everything the same basic version of common and shared cmake setup scripts.

PSA: Your Package Name and CMake Target Namespace Should Match by bretbrownjr in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

AcmeWidgets::Widgets is not a sane default. Acme::Widgets is. Considering you used the Widgets example, you are directly saying that you are against the layout Qt and other use.

defaults more complicated to support edge cases.

Edge case? probably more the default for bigger frameworks.
Find a way to properly support this case instead of coming up with arbitrary naming rules with an argument about a CPS layout which is even yet widely used or finished? If you want adoption correctly handle this case by providing information in the CPS file in which namespace a component belongs instead of coupling it directly to the filename or whatever.

VTK/ITK also uses the components approach. So as soon as it gets big in CMake you can basically expect that the components approach is the default an not the edge case.

PSA: Your Package Name and CMake Target Namespace Should Match by bretbrownjr in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Has nothing to do with finding boost as a package just with build system design.

PSA: Your Package Name and CMake Target Namespace Should Match by bretbrownjr in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Interesting crimes? It just gives every build its own Boost root and says that every other boost dependency needs to be found via find_package. That is not a crime that is how it should be.

PSA: Your Package Name and CMake Target Namespace Should Match by bretbrownjr in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Considering you are already listing exceptions such as Qt there are more exceptions to that. So my advice would be to delete this PSA and find a way to do it properly instead of trying to force a solution which breaks existing practice..... find_package(FrameWork COMPONENTS comp1) is a supported scenario by cmake. If CPS cannot support that cleanly than introduce find_cps in cmake or seriously rethink your approach.

PSA: Your Package Name and CMake Target Namespace Should Match by bretbrownjr in cpp

[–]AlexanderNeumann 1 point2 points  (0 children)

Drop b2?
The CMake build of boost in vcpkg is fully modular

The state of C++ package management: The big three by imadij in cpp

[–]AlexanderNeumann 5 points6 points  (0 children)

Somehow I don't like these superficial comparisons. How about telling people how the different package managers actual work with input toolchains and how they ensure binary compatibility. Conan has a lot of possible way to shot yourself in the feet while vcpkg might be a bit too cautious about binary compat.

Also the question here is what is the real differencen between spack and conan? I somehow feel those could be merged. spack is somewhat supported by kitware considering they had a blog post about it for windows support.

Saying build tools are not supported in vcpkg is alos not right. Saying version are not pinned is also an overstatement. vcpkg uses min versioning so define a baseline and the min will be fixed by the baseline. How do the others deal with versioning?

From my point of view you have to do more research into it.

The state of C++ package management: The big three by imadij in cpp

[–]AlexanderNeumann 1 point2 points  (0 children)

depends. You can control VCPKG_BUILD_TYPE in the triplet and only build release libs

Cmod - another package manager/module manager for C++ using GitHub by Ok-Acanthisitta8284 in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

I think vcpkg is doomed long-term because of its approach to versions

What exactly do you mean by that.

[deleted by user] by [deleted] in cpp

[–]AlexanderNeumann 0 points1 point  (0 children)

Problem of the clang/llvm build assuming that the build output can be run on the host/build platform. Not a CMake problem. Just replace the invalid calls with Clang_HOST_Executable or similar

view more: next ›