From afef99a2991c61ffc07ff7751d35e8c2fed0e5ea Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20P=C3=B6chtrager?= Date: Thu, 2 Jan 2014 00:19:20 +0100 Subject: [PATCH] remove the 'weak debug info' notes from the README Debug symbols work anyway as long you *don't* build the binary in a single step: o32-clang++ test.cpp -g3 # causes dsymutil invocation o32-clang++ test.cpp -g3 -c # causes *no* dsymutil invocation o32-clang++ -g3 test.o -o test # causes *no* dsymutil invocation same with gcc. Getting line numbers may require you to copy the object files (*.o) onto the system you are debugging on. --- README.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/README.md b/README.md index 9fc987a..9ef1192 100644 --- a/README.md +++ b/README.md @@ -15,11 +15,6 @@ If you want, then you can build an up-to-date vanilla GCC as well. ### WHAT IS NOT WORKING (YET)? ### -* Debug info is weak because of the [missing](https://github.com/tpoechtrager/osxcross/blob/master/oclang/dsymutil) - [`dsymutil`](http://www.manpagez.com/man/1/dsymutil) (debugger shows only function names). - The source code of dsymutil is not publicly available, so it can't be ported to other platforms. - But you probably don't want debug symbols anyway if you build on a non OS X system. - * GCC itself [doesn't build with GCC](https://github.com/tpoechtrager/osxcross/commit/12f5dcdde4bc1000180d25ffda229f0a13cf723d), but builds fine when clang is used to build GCC.