Relintai/osxcross
1
0
Fork 0
mirror of https://github.com/Relintai/osxcross.git synced 2025-02-03 22:45:56 +01:00
Code Issues Packages Projects Releases Wiki Activity

remove the 'weak debug info' notes from the README

Browse Source 
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.
This commit is contained in:
Thomas Pöchtrager 2014-01-02 00:19:20 +01:00
parent 241d9df6bc
commit afef99a299
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -15,11 +15,6 @@ If you want, then you can build an up-to-date vanilla GCC as well.
### WHAT IS NOT WORKING (YET)? ### ### 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), * GCC itself [doesn't build with GCC](https://github.com/tpoechtrager/osxcross/commit/12f5dcdde4bc1000180d25ffda229f0a13cf723d),
but builds fine when clang is used to build GCC. but builds fine when clang is used to build GCC.