diff options
author | Aki <please@ignore.pl> | 2024-03-09 23:02:17 +0100 |
---|---|---|
committer | Aki <please@ignore.pl> | 2024-03-09 23:02:17 +0100 |
commit | e1606f9bbc45e7ba57c461dc1ca4d4a86c5d76dd (patch) | |
tree | d13c968b28d8f9a076b7fed0d6f098fc448ce87c /FoundationEx/include | |
parent | eced12a69603e23d6869f92a2d5302f4605354ba (diff) | |
download | starshatter-e1606f9bbc45e7ba57c461dc1ca4d4a86c5d76dd.zip starshatter-e1606f9bbc45e7ba57c461dc1ca4d4a86c5d76dd.tar.gz starshatter-e1606f9bbc45e7ba57c461dc1ca4d4a86c5d76dd.tar.bz2 |
Replaced MachineInfo with stripped cross-platform solution
It could easily handle more, but is there really need for it? Having
some information about the machine in logs is nice, but with the
current state of affairs most of errors are coming from bad pointer
uses than anything else...
InfoEx is STATIC, because it seems FoundationEx can cause multiple
definitions in scenarios like this.
Diffstat (limited to 'FoundationEx/include')
0 files changed, 0 insertions, 0 deletions