Hi all, (please Cc: me when replying. Thanks.)I'd like to warm up an old topic regarding creation of *.symbols files for shared libraries implemented in C++.
I have followed all links in [1] and esp. read Russ Alberries experiment results [2,3]. All writing are quite old and I wonder if something new has come up meanwhile (improved tool chains, etc).
Until now, I mostly avoided writing .symbols files for C++ shared libs.However, here comes the question: How do people handle .symbols files these days if they originate from C++ code? How do people make sure the .symbols files are correct for all supported architectures? What tool chains are used? Are there other good reads about the topic?
My current context: I want to fix various build failures of lib-cpp related packages relevant for upcoming Unity8.
Thanks + Greets, Mike [1] https://wiki.debian.org/UsingSymbolsFiles [2] https://www.eyrie.org/~eagle/journal/2012-01/008.html [3] https://www.eyrie.org/~eagle/journal/2012-02/001.html -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Attachment:
pgpdcE7eLQX8z.pgp
Description: Digitale PGP-Signatur