jdev - 2025-02-24

blue: did you get it built with openssl and did it work?

You overestimate my abilities)

blue, I’m sure you’re able to run ./configure --help, then ./configure again with the relevant option to pick openssl, then make.

Not quite, I don't want to run sudo make install so, i either need to make it into arch package or embed it into my cmake project

blue, Does gloox exist on Conan? And/or could you Conanize Gloox?

blue, Answers: no, and yes of course if you wanted.

Conan is quite nice for C++, I find. And it manages to compile OpenSSL from scratch in an almost indecent amount of time.

Conan is a building system? Never heard of it before

It's a build system wrapper for source packaging. Kinda.

It's infuriating, and also quite good, and also infuriating, and also quite good.

Will C++ decide on a build system before being pushed into total irrelevance by Rust 🍿

moparisthebest: maybe when rust can be more portable than C/C++

Kev: have you used meson?

it has wrap files

> moparisthebest: maybe when rust can be more portable than C/C++ Cool so very soon then when gcc-rs is done 🎉 ↺

>done

hahahahahahaha

no it's an endless catch-up with the main rust implementation

anyway meson can also build cmake subprojects as dependencies without any work

moparisthebest: i like how the community is still having a fight over gcc-rs

whether gcc-rs is relevant because rustc already does the job

i believe that LLVM shouldn't have a monopoly if rust wants to progress

What fight? It seems to be progressing at lightning speed https://rust-gcc.github.io/2025/02/06/2025-01-monthly-report.html

https://lwn.net/Articles/991199/

the comments

Rule #1 of the internet is never read the comments

He says, in a comment

rust is unattractive to me because of the LLVM monopoly

And thus, my point is proven

i'd rather use C/C++ with a wide compiler ecosystem

than rust with..... just one

That's not even the case now, there is mrustc that complies to C, but gcc-rs will be here soon too

LLVM drops targets like they're hot, and porting it to a platform that isn't widely used... well good luck with that

moparisthebest: mrustc is meant to be a bootstrapper

it doesn't even have the full borrow checker

it's sloppy and only meant to compile rustc

there is only one usable compiler

> it doesn't even have the full borrow checker The goalposts, they be a movin' 🎶 enough side chatter from me about this for now ↺

> > it doesn't even have the full borrow checker > The goalposts, they be a movin' 🎶 > enough side chatter from me about this for now not goalposts moving because i'm clearly talking about usable compilers

that's like saying "well there's more than just one compiler for C, you can use the obfuscated tiny C compiler"

Borrow checker is not related at all to platform support

borrow checker is literally the most important part of rust

can you even use mrustc without that?

like, can you, in production, just use purely mrustc to make rust programs

i'll put in better terms, can you replace rustc with mrustc

and use it to make all your rust stuff

“16:58:26 blue> Not quite, I don't want to run sudo make install so, i either need to make it into arch package or embed it into my cmake project”, it already has a PKGBUILD, since it’s in ArchLinux: https://gitlab.archlinux.org/archlinux/packaging/packages/gloox

Every package you can install, you can also read their PKGBUILD, it’s all free software.

moparisthebest, Cynthia, for compilation, instead of gcc-rs, I recommend you to check out rustc_codegen_gcc. Where the former tries to reimplement all of the Rust language, the latter just replaces LLVM with libgccjit for codegen.

So it benefits from the entire existing compiler infrastructure, from the parser to the borrow checker, and just uses a different C++ project for the optimization passes and to emit the final assembly.

You also have rustc_codegen_cranelift, which is written in Rust instead of C++, and is way faster at emitting code than both LLVM and libgccjit, at the expense of the speed of the generated code of course (but it still does a bunch of optimizations).

“19:52:28 Cynthia> i'd rather use C/C++ with a wide compiler ecosystem”, err, have you used the other compilers? I’d rather stay with gcc and LLVM and never touch any of the proprietary garbage that exist besides them. v_v

And tcc, for the same reasons as cranelift (but that one only does C, not C++). ✏

Oh wow, I still had a mrustc version from five years ago installed on my laptop! o_o % mrustc --version rustc 1.29.100 (mrustc v0.9.0 master:fb2b1202) - Build time: Fri, 22 Nov 2019 00:56:03 +0000 - Commit: fb2b1202e916e2e3f406d03005237b1d2447269f (dirty tree)

And yes, even back then it could build a simple Rust program I had around, which is a given since it could compile rustc which is significantly more complex than that.

(Completely offtopic, but anyways) I was happy to have vbcc to support an architecture that has 16 bit bytes. Llvm won't do it and doing anything in gco seems complicated

I think LLVM now supports some 16-bit architectures.

Sorry for the offtopic, I thought I was in another room. :x