Date: Tue, 30 Jul 2024 01:22:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 280497] [NEW PORT] emulators/ares: Multi System Emulator Message-ID: <bug-280497-7788-C2s4R8Lhtz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280497-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-280497-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280497 --- Comment #4 from Stefan Schlosser <bsdcode@disroot.org> --- (In reply to Vladimir Druzenko from comment #3) > Oh, your patch for util/timer.cpp is same as I suggested. :-D Soulmate detected :-D The PR upstream for this patch is open, but if/when it gets merged, it will propagate to ares eventually (Granite -> parallel-rdp -> ares (ares bundles parallel-rdp)). > Your port look more complex and functional. It definitely looks a little bit unwieldy. I exposed almost every build opt= ion ares has to offer. But this aside I think it's actually quite straight forw= ard. I want it to be as functional and complete as I can get it. I only have thr= ee things left to do: - patch out the hardcoded -Ox optimization flags from the project's Makef= ile - add QT5 option aside GTK3 - Flavorize GTK3 and QT5 (- waiting for librashader to be committed) > If it didn't use rust, I would have committed it - I'm not ready to test = ports with rust. :-( Thanks regardless. Well, it was actually my first time with rust/cargo. It took me quite some = time to tame that stupid build script. Of course it would probably have been eas= y if I had experience with cargo.... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280497-7788-C2s4R8Lhtz>