-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building WebRTC native-code library #124
Comments
Exactly the same issue here. Just for reference. This is the code that is causing it, but I cannot make out anything from the description. Also googling it yields no results at all... BTW sorry for the screenshots. I cannot seem to be able to copy text from the VM. Something wrong with the integration... |
Change is_official_build=false is_debug=true in the args.gn file and the recompile will be successful. |
There are some issues with WebRTC native code package building. It seems to be an issue mostly related to code optimization.And It seems that it may take more time for it to stabilize. This issue will be deleted later when WebRTC native code is built with this option and the problem goes away. In addition to this issue, it has not been confirmed whether there is a problem with neon-related optimization or gcc issue in the recent WebRTC native code and libyuv, but I think it will be fixed after a little time. To compile the latest WebRTC native code, you need to modify the following part in the args.gn file as well.
|
After updating the five items, I am able to run
Any idea? |
I already talked about what needs to be fixed in the args.gn file in the posting right above. FYI, when RWS uses the latest WebRTC native code, compilation errors (API changes related to Platform Thread in WebRTC, and header files related to H264 profile are changed) occur. The fix will be included in the next commit. For changes to the WebRTC native code commit location that is compiled with RWS, please refer to 3.4 moving to specific commit position |
Thanks for the info, but I included those variables you listed in args.gn. Maybe I don't fully understand what you're saying. Anyway, yes, seems I have misunderstood that 3.4 section and I am sorry for that. Will try again. |
OK, I have been able to successfully build everything based on the commit contained in the rws repo commit message. Great. One more question though... Upon running the streamer and connecting to the URL I get the following error:
I have already enabled the camera in raspi-config before which I was getting another error, but that went away with enabling the camera. But I can't seem to figure out how get rid of this one. |
OK, seems it's trying to save the still capture to My guess is that this folder can be configured in one of the config files, right? Only I cannot find where... |
Just for the record... Creating the directory helps, but you still need to run It seems to me that is has to be configurable somewhere, but I just cannot figure out where. //Edit: One more thing. If you're running without the |
I'm getting a build error step 3.2 when building the native WebRTC library for arm6.
|
Hi. Instead of duplicating my post which I have done on another closed post (not sure if closed means the notification stops working); I have the same problem with different error messages. Yes, I also followed @kclyu and @allen123456allen posts on args.gn on neon and also using debug flags but I still have problems that I am not sure how to resolve. The link is #98 (comment) and also worth mentioning is I have managed to build v0.74 so far. Only the latter commits, I have issues and tried many things and not sure what to try. |
The following error occurred when I ran the "gn gen out/arm_build" command:
RROR at //build/config/compiler/BUILD.gn:644:5: Assertion failed.
Assert (USE_LLD, "LTO is only supported with LLD ")
^ -- -- -- -- --
LTO is only supported with lld
See //build/config/BUILDCONFIG.gn:318:3: which caused the file to be included.
"/ / build/config/compiler: afdo",
^ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -
Can you take a look at it for me?Thank you very much!
The text was updated successfully, but these errors were encountered: