Tech
So far, Visual Studio has let me, and by extension everyone else on my team, define a library
* as a reference (Common Properties->References)
* as a library (Linker->Input)
* in a directory (Linker->General)
* by inclusion in stdafx.h
* by inclusion in #pragma comment
* by inclusion in a precompiled header package.
* as a property file.
There may be more than one right way to do things, but "more than one way" is the wrong way.
Tech
@literorrery in an nmake file calling cl.exe with the dll option skipping the horrifying GUI altogether
Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.
While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.
Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!
Tech
@Fuego In a ps1 file in the build scripts that nobody's yet informed me exists.
As part of the standard image for the server that's stubbed during build and and linked dynamically at runtime....
I mean, if we're talking about horror shows, I can think of even more ways to make this worse. :)