Mechanism to allow jlog to **not** log anything to console on release builds. #11

Closed
opened 2024-07-02 12:19:58 -04:00 by josh · 3 comments
Owner

Justification is that on Windows, any call to console log opens a CMD process if one is not already attached to the window. This is generally undesirable for release builds of game applications.

Enabled by default, but users of the library can toggle it easily.

Justification is that on Windows, any call to console log opens a CMD process if one is not **already** attached to the window. This is generally undesirable for release builds of game applications. Enabled by default, but users of the library can toggle it easily.
josh self-assigned this 2024-07-02 12:20:04 -04:00
maxine was assigned by josh 2024-07-02 12:20:04 -04:00
josh added the
Kind/Enhancement
Priority
Medium
labels 2024-07-02 12:20:09 -04:00
Collaborator

We can probably use an ifdef where if a macro called DEBUG is set then log to both file and console otherwise log only to file

We can probably use an ifdef where if a macro called DEBUG is set then log to both file and console otherwise log only to file
Collaborator

I'm banging out some issues today. This is the first one.

I'm banging out some issues today. This is the first one.
Collaborator

Done. Just a simple macro and global variable.

f7ee1a347e

Done. Just a simple macro and global variable. https://git.redacted.cc/josh/jlog/commit/f7ee1a347e03ea6436dac7b2f216ac93d270d6ef
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: josh/jlog#11
No description provided.