034ff0a305
The normal usage is to include the src/ directory of google breakpad in your application and then include client/ARCH/handler/exception_handler.h where ARCH is windows, mac or linux. However, Linden Lab for some reason packaged the breakpad prebuilt with exception_handler.h installed in ../google_breakpad/exception_handler.h where "../google_breakpad" is the 'root' of the include tree comparable with 'src' in the source tree of google breakpad. Hence, instead of including 'src' one now must include '../include/google_breakpad' which was already done correctly for non-standable, but not for standalone (BREAKPAD_EXCEPTION_HANDLER_INCLUDE_DIR was set to '../include' with the 'google_breakpad' and is subsequently never used: instead BREAKPAD_INCLUDE_DIRECTORIES is used (which is set for non-standalone)). Therefore one much not include "google_breakpad/exception_handler.h", but just "exception_handler.h" or you rely on somehow the directory *below* BREAKPAD_INCLUDE_DIRECTORIES to be part of the include path as well. Finally LL packages the prebuilt if another duplicate minidump_descriptor.h in the include root. Also here including "minidump_descriptor.h" would be better correct, but following the instructions by Google this time we might as well include the original "client/linux/handler/minidump_descriptor.h". My repo (http://github.com/AlericInglewood/3p-google-breakpad) doesn't even put minidump_descriptor.h in the root anymore, only exception_handler.h. The rest is an exact copy of the 'src' tree with regard to the headers. Tested to compile both standalone and non-standalone.
00000000011111111112222222222333333333344444444445555555555666666666677777777778
12345678901234567890123456789012345678901234567890123456789012345678901234567890
______ ___ __ _ _____ _ _ ______ _____ ___ _____ _ _
|_____ | | \ | | ___ | | | |____| |____/ | | \_/
_____| _|_ | \_| |____| |____| |____ | | | \_ _|_ | |
_ _ _ ____ _ _ ____ ____
\/ | |=== |/\| |=== |--<
Sin-gu-la-ri-ty (noun) - a distinctive feature, a uniqueness; a point at which
continuity breaks up; a point in history at which machine becomes smarter than
humanity and/or fuses with it indivisively; or simply a cool sounding word with
the initials S.G. in it :)
Singularity Viewer is a SecondLife(tm) protocol compatible client application.
It can be used to access SecondLife services as well as a number of others such
as those based upon the OpenSim platform.
Singularity is maintained by a small group of volunteers who can be contacted
both, in-world (SingularityViewer group) as well as on IRC (#SingularityViewer
@ FreeNode). Bug requests and features requests can be submitted through our
Issue Tracker (http://code.google.com/p/singularity-viewer/issues/list or from
the viewer menu: Help --> Bug Reporting --> Singularity Issue Tracker...)
As this Readme grows out of date, please refer to
http://www.singularityviewer.org/about
00000000011111111112222222222333333333344444444445555555555666666666677777777778
12345678901234567890123456789012345678901234567890123456789012345678901234567890
History
The Singularity viewer was started by Siana Gearz in November 2010 by forking it
from the Ascent Viewer, by Balseraph Software Group, which in turn was based upon
source code modified from the snowglobe source code released by Linden Lab.