You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2022. It is now read-only.
The current Telegram (for Desktop) build directives instructs readers to build both Debug and Release configurations of the Opus library. I do not know if this is an oversight or not, but the Debug configuration does not build for multiple reasons:
// m.cpp
int a() {
// I'm pretty sure this goes against several cpp rules.
// This generates C4716
}
Upon adding a generic "return 0;", another error crops up: error LNK1561: entry point must be defined | Project: m
The release configuration builds fine, however, and the directives makes me believe that only Release is required.
The text was updated successfully, but these errors were encountered:
The current Telegram (for Desktop) build directives instructs readers to build both Debug and Release configurations of the Opus library. I do not know if this is an oversight or not, but the Debug configuration does not build for multiple reasons:
Upon adding a generic "return 0;", another error crops up:
error LNK1561: entry point must be defined | Project: m
The release configuration builds fine, however, and the directives makes me believe that only Release is required.
The text was updated successfully, but these errors were encountered: