-
Notifications
You must be signed in to change notification settings - Fork 1
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
build_type Release/RelWithDebInfo #15
Comments
I've stuffed the server
It doesn't even respond to |
I wonder if we need debug symbols at all for most of the libraries. pdf2htmlex makes sense if we think we can fix bugs there. But for the dependencies of it I wonder if we should just rather use Release I cleaned the backups out should have space again |
I don't think it's up again, mate ☠️ |
I've did a few rebuilds and on Android the size doesn't really change between RelWithDebInfo and Release. Gradle removes a lot when it strips symbols, so there's no need to worry about this on Android. I'm more concerned about Linux binaries, because there's no gradle that strips binaries. Do we even make any use of debug symbols on Linux? |
Should be back up
Right this is what I expected. I guess the question is more if we really need the debug infos of our dependencies. I would argue that we are only interested in debug symbols of code we maintain and we have under control. To me this is odr.core and maybe pdf2htmlex. But the dependencies of those we don't really control so if there is an exception / signal coming from there it is a problem we would fix on our side because we use the library in the wrong way or we update the dependency.
For linux we do not need the debug symbols at all at the moment. They are safe to be removed completely. |
I've looked at this a bit more, yes, the full build tree doesn't differ that much, but final binaries do differ a lot.
Linux x86_64 odr.core build with pdf2htmlEX.
RelWithDebInfo:
Release:
We do need debug info for Android builds, do we make actual use of that in other platforms?
The text was updated successfully, but these errors were encountered: