/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 www.yosoygames.com.ar
November 18, 2022 - Yosoygames
| | www.wgdd.de
[erfahrungen, meinungen, halluzinationen]: N54L LCD-Mod with U204FR-A3 (LCDModkit) and lcdproc *pic*
7.5 parsecs away

Travel
| | A private blog about Debian GNU/Linux, my work and life as a Debian user and as Debian developer.
| | erikmcclure.com
Most Bizarre Error Ever
12.2 parsecs away

Travel
| | Ok probably not the most bizarre error ever but it's definitely the weirdest for me. My graphics engine has a Debug, a Release, and a special Release STD version that's compatible with CLI function requirements and other dependencies. These are organized as 3 separate configurations in my solution for compiling. Pretty normal stuff. My example applications are all set to be dependent on the graphics engine project, which means visual studio automatically compiles the proper lib file into the project.
| | videogameartistry.wordpress.com
No Post 12/30/16! - Video Game Artistry
6.5 parsecs away

Travel
| | I'm going to be busy spending the holidays with family, but there will be a post the week succeeding that, promise. Thank you for your understanding!!
| | jmmv.dev
Picking glibc versions at runtime - Julio Merino (jmmv.dev)
35.6 parsecs away

Travel
| In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?...