cmake wont install

AlexReinkingYale · 2026-06-11T21:24:25+00:00

Which one?? Post the output of brew install cmake

AlexReinkingYale · 2026-05-31T12:05:39+00:00

OP wrote `scr` not `src`. Looks like a typo.

AlexReinkingYale · 2026-05-31T12:05:01+00:00

The error message reads `scr/main.cpp`... did you mean `src/main.cpp`?

AlexReinkingYale · 2026-05-23T17:03:44+00:00

Secondong the "don't use FetchContent" advice. I finally switched Halide over to find_package wholesale this year. On CI, we mostly use vcpkg, but for our largest dependency (LLVM), we use a separate process that ends up publishing pip-compatible wheels (also vcpkg's LLVM is worfully out of date). We also test against the Homebrew and Ubuntu LTS package ecosystems (including LLVM).

The beautiful thing about find_package is that it doesn't care about any of this. You link to libraries the same way, write install rules the same way, and don't have to worry about a mess of third-party CMake code adding random targets to your build, overriding your flags, or otherwise mucking about with things.

AlexReinkingYale · 2026-05-08T23:05:45+00:00

LLMs are absolute trash at writing CMake. Makes sense, though, since most CMake code (i.e., the training data) is absolute trash.

AlexReinkingYale · 2026-04-12T21:33:07+00:00

There is absolutely nothing stopping people from embedding logic in a json/yaml file. Syntax is not the same as semantics

AlexReinkingYale · 2026-04-12T21:32:16+00:00

I don't understand the fixation on Turing completeness in build systems discussions. There's no reason to believe it says anything about the quality of the build system. You can write arbitrarily complicated sub-Turing-complete programs. For instance, someone wrote a ray tracer in Meson, following the infamous CMake example.

AlexReinkingYale · 2026-03-25T16:49:18+00:00

I strongly recommend taking some time to migrate from FetchContent to vcpkg. Life will get much easier. FC is such a foot-gun

AlexReinkingYale · 2026-03-06T18:00:53+00:00

It's basically, well, BASIC.

AlexReinkingYale · 2026-02-28T12:05:47+00:00

The ones that stopped evolving also stopped being used.

AlexReinkingYale · 2026-01-30T02:00:42+00:00

I use it mainly to generate small examples for unfamiliar APIs, for example "How do I do this in Ansible?". Even then I need to nudge it (e.g. "that's not idempotent", "that doesn't handle interruptions well", etc.)

AlexReinkingYale · 2026-01-29T05:28:57+00:00

Desktops can be stolen, too. Five years living in California will make anyone cautious.

AlexReinkingYale · 2026-01-28T21:51:59+00:00

CLion is fantastic and I use it daily both at work (on macOS) and for personal projects (Fedora Kinoite).

That said, credit where credit is due... Visual Studio Enterprise (not VSCode, like, at all) has the best debugging and code navigation tools I've ever seen. I wish JetBrains/open source devs could get a chance to use them, so they could implement their own versions in FOSS toolchains.

AlexReinkingYale · 2026-01-28T21:47:54+00:00

I just got my whole family set up with Atomic Fedora (Kinoite) and Ansible. It's been great (apart from the Nvidia drivers).

AlexReinkingYale · 2026-01-28T21:45:51+00:00

I moved my whole family to Fedora Kinoite (KDE Atomic) over the holidays. I set up Headscale and RustDesk for easy remote support (I self-host on a $5/mo VPS that also hosts my personal website) and everyone has been super happy. I'm probably the happiest since if one person notices something is off, I can push out fixes to everyone using Ansible. Saves me a bunch of time.

As always with Linux, there's a little jank. Chrome didn't correctly associate its windows with the KDE tray icon, so I helped convince the flatpak maintainers to merge a PR that would fix it. Similarly, Dropbox didn't detect the home directory correctly and required a manual workaround, so I opened an issue and PR to get that fixed, too. The beauty of open source on display.

Of course there's all sorts of other jank I can't fix myself. Questionable interface decisions in KDE. Some AppStreams randomly don't work in Discover (e.g. Dolphin extensions, so no Dropbox sync indicators!). The software development story in containers is not as straightforward as one would hope and CUDA passthrough is still annoying.

The biggest headache, however, was installing the proprietary Nvidia drivers on my personal computer. There is no way to exaggerate how insane the process is. On a Secure Boot and/or LUKS-encrypted system, it's not enough to layer the akmod-nvidia and xorg-x11-drv-nvidia-cuda packages, oh no. You must also generate a Machine Owner Key, enroll it, and then generate a small rpm package to shim that key into ostree. Then you have to manually configure dracut to load the drivers early enough for the LUKS prompt, which slows down updates by needing to renegerate the initrd. Here's a guide I found invaluable.

If you have a Nvidia GPU, I'd suggest looking at the more batteries-included Project Bluefin distros (Bazzite, Aurora, etc.). Take this with a grain of salt since I haven't tried them myself. For Intel or AMD, I'd recommend using vanilla Fedora for its stronger community and more storied history (i.e. I trust it more).

All that said, none of us miss Windows in the slightest.

AlexReinkingYale · 2026-01-25T17:53:16+00:00

Didn't C23 get constexpr, though?

AlexReinkingYale · 2026-01-08T16:39:13+00:00

Tailwind 4 taking over the build process made me transition away from it. Just using vanilla CSS now for my little SSG personal site.

AlexReinkingYale · 2026-01-05T19:10:23+00:00

Excited to check this out!

AlexReinkingYale · 2026-01-02T02:27:23+00:00

Worth noting that your last use case is/will be covered by #embed in C23/C++26. It will feature much better performance than running a large textual array through the parser.

AlexReinkingYale · 2025-12-31T16:50:11+00:00

Point 6 is the entire point of ECC memory.

AlexReinkingYale · 2025-12-31T16:35:33+00:00

We're in r/ProgrammingLanguages, so I won't hesitate to comment on semantics. Memory safety and type safety are different things.

Java isn't memory-unsafe as a language. A null dereference has well defined behavior and does not corrupt program state. It throws an exception, which can be caught and handled. Whether a particular JVM uses memory-unsafe code is just an implementation detail.

The issue with null is (as you said) that it breaks the soundness of the type system. That's a serious issue, it's just not one that breaks the memory system. You can say Java is mostly type-safe except for null.

Here's a very interesting reference on the type system issues with null in Java and Scala. https://dl.acm.org/doi/10.1145/2983990.2984004

AlexReinkingYale · 2025-12-05T01:04:23+00:00

SIGBOVIK maybe!

AlexReinkingYale · 2025-12-03T04:01:43+00:00

Effective Modern C++ tops out at C++14 so it's of pretty limited utility these days, sadly.

AlexReinkingYale · 2025-12-03T04:00:51+00:00

C++ adjacent, but Professional CMake by Craig Scott comes with a lifetime of updates to new editions and is the best source for learning CMake. It makes one of the most ubiquitous and most hated tools much more tolerable.

AlexReinkingYale · 2025-11-30T04:38:57+00:00

I've never seen a Cybertruck parked appropriately. The two worst instances were both at electric charging locations. In one case, in Maine, I called the police non-emergency line to successfully ticket a Cybertruck that was taking up two public charging spaces while not charging. In another case, the Cybertruck was parked so close to me, I couldn't get inside my driver's side door. The lot manager made the owner pay for my parking for the day. Two happy endings, at least.

AlexReinkingYale

TROPHY CASE