Use native WebRTC library with Windows VisualStudio/Visual C++ 2017
up vote
0
down vote
favorite
I am new to WebRTC, and I started with installing the ready-to-use library package available at Sourcey.
Using VS2017 I created a simple "hello world" console application which includes one of the webrtc native API headers.
I added the additional include path (Project config > C++ > general > add. include) and link path (Project config > Linker > add. library path).
But I got a lot of compile errors: from them I dreived that the Windows platform was not recognised, and it tried to include Unix* Headers like instead. So first fix was to add WEBRTC_WIN to the preprocessor symbols.
Still I got many (1076) other errors, mostly dubious, e.g. complaining about '::' in std::numeric_limits<int>::max() .
Second fix: I added #define NOMINMAX in my source file. It seems that Windows usually defines macros min() and max() which corrupt the c++ code.
So now 2 errors, complaining about _vsnwprintf() function maybe being not safe. As it recommended I set _CRT_SECURE_NO_WARNINGS but had to do this in the project configuration, it was not enough to set it in the source file including!
Lack of documentation on these problems with the native WebRTC libs is really annoying! Also not in the forum Google discuss webrtc. More user experiences? Tipps?
Edit: I found a nice tutorial which discourages directly using Native API and instead recommends using QT Wrapper: Tutorial
c++ windows visual-studio webrtc native
asked Nov 21 at 16:29
karsten
33716
add a comment |
up vote
0
down vote
favorite
I am new to WebRTC, and I started with installing the ready-to-use library package available at Sourcey.
Using VS2017 I created a simple "hello world" console application which includes one of the webrtc native API headers.
I added the additional include path (Project config > C++ > general > add. include) and link path (Project config > Linker > add. library path).
But I got a lot of compile errors: from them I dreived that the Windows platform was not recognised, and it tried to include Unix* Headers like instead. So first fix was to add WEBRTC_WIN to the preprocessor symbols.
Still I got many (1076) other errors, mostly dubious, e.g. complaining about '::' in std::numeric_limits<int>::max() .
Second fix: I added #define NOMINMAX in my source file. It seems that Windows usually defines macros min() and max() which corrupt the c++ code.
So now 2 errors, complaining about _vsnwprintf() function maybe being not safe. As it recommended I set _CRT_SECURE_NO_WARNINGS but had to do this in the project configuration, it was not enough to set it in the source file including!
Lack of documentation on these problems with the native WebRTC libs is really annoying! Also not in the forum Google discuss webrtc. More user experiences? Tipps?
Edit: I found a nice tutorial which discourages directly using Native API and instead recommends using QT Wrapper: Tutorial
c++ windows visual-studio webrtc native
asked Nov 21 at 16:29
karsten
33716
1
It would be helpful to see the exact error messages.
– drescherjm
Nov 21 at 16:55
@drescherjm: I added more info. I removed asking for documentation.
– karsten
Nov 22 at 10:55
I found some more information: current state link Cmake installer link. Cmake description link
– karsten
Nov 23 at 20:00
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am new to WebRTC, and I started with installing the ready-to-use library package available at Sourcey.
Using VS2017 I created a simple "hello world" console application which includes one of the webrtc native API headers.
I added the additional include path (Project config > C++ > general > add. include) and link path (Project config > Linker > add. library path).
But I got a lot of compile errors: from them I dreived that the Windows platform was not recognised, and it tried to include Unix* Headers like instead. So first fix was to add WEBRTC_WIN to the preprocessor symbols.
Still I got many (1076) other errors, mostly dubious, e.g. complaining about '::' in std::numeric_limits<int>::max() .
Second fix: I added #define NOMINMAX in my source file. It seems that Windows usually defines macros min() and max() which corrupt the c++ code.
So now 2 errors, complaining about _vsnwprintf() function maybe being not safe. As it recommended I set _CRT_SECURE_NO_WARNINGS but had to do this in the project configuration, it was not enough to set it in the source file including!
Lack of documentation on these problems with the native WebRTC libs is really annoying! Also not in the forum Google discuss webrtc. More user experiences? Tipps?
Edit: I found a nice tutorial which discourages directly using Native API and instead recommends using QT Wrapper: Tutorial
c++ windows visual-studio webrtc native
asked Nov 21 at 16:29
karsten
33716
I am new to WebRTC, and I started with installing the ready-to-use library package available at Sourcey.
Using VS2017 I created a simple "hello world" console application which includes one of the webrtc native API headers.
I added the additional include path (Project config > C++ > general > add. include) and link path (Project config > Linker > add. library path).
But I got a lot of compile errors: from them I dreived that the Windows platform was not recognised, and it tried to include Unix* Headers like instead. So first fix was to add WEBRTC_WIN to the preprocessor symbols.
Still I got many (1076) other errors, mostly dubious, e.g. complaining about '::' in std::numeric_limits<int>::max() .
Second fix: I added #define NOMINMAX in my source file. It seems that Windows usually defines macros min() and max() which corrupt the c++ code.
So now 2 errors, complaining about _vsnwprintf() function maybe being not safe. As it recommended I set _CRT_SECURE_NO_WARNINGS but had to do this in the project configuration, it was not enough to set it in the source file including!
Lack of documentation on these problems with the native WebRTC libs is really annoying! Also not in the forum Google discuss webrtc. More user experiences? Tipps?
Edit: I found a nice tutorial which discourages directly using Native API and instead recommends using QT Wrapper: Tutorial
c++ windows visual-studio webrtc native
c++ windows visual-studio webrtc native
asked Nov 21 at 16:29
karsten
33716
asked Nov 21 at 16:29
karsten
33716
edited Nov 22 at 11:27
asked Nov 21 at 16:29
karsten
33716
asked Nov 21 at 16:29
karsten
33716
asked Nov 21 at 16:29
karsten
33716
33716
1
It would be helpful to see the exact error messages.
– drescherjm
Nov 21 at 16:55
@drescherjm: I added more info. I removed asking for documentation.
– karsten
Nov 22 at 10:55
I found some more information: current state link Cmake installer link. Cmake description link
– karsten
Nov 23 at 20:00
add a comment |
1
It would be helpful to see the exact error messages.
– drescherjm
Nov 21 at 16:55
@drescherjm: I added more info. I removed asking for documentation.
– karsten
Nov 22 at 10:55
I found some more information: current state link Cmake installer link. Cmake description link
– karsten
Nov 23 at 20:00
1
1
It would be helpful to see the exact error messages.
– drescherjm
Nov 21 at 16:55
It would be helpful to see the exact error messages.
– drescherjm
Nov 21 at 16:55
@drescherjm: I added more info. I removed asking for documentation.
– karsten
Nov 22 at 10:55
@drescherjm: I added more info. I removed asking for documentation.
– karsten
Nov 22 at 10:55
I found some more information: current state link Cmake installer link. Cmake description link
– karsten
Nov 23 at 20:00
I found some more information: current state link Cmake installer link. Cmake description link
– karsten
Nov 23 at 20:00
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53416549%2fuse-native-webrtc-library-with-windows-visualstudio-visual-c-2017%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
It would be helpful to see the exact error messages.
– drescherjm
Nov 21 at 16:55
@drescherjm: I added more info. I removed asking for documentation.
– karsten
Nov 22 at 10:55
I found some more information: current state link Cmake installer link. Cmake description link
– karsten
Nov 23 at 20:00