Has anyone gotten XCode auto completion to work with Qt6? Files like QMainWindow simply don't exist on my installation of Qt for some raisin...
Post
Replies
Boosts
Views
Activity
Right now I am having a very difficult time trying to get CMake+LLVM (clang) working proper on macos. Microsoft Visual Studio doesn't seem to support C++ development on macos, XCode seems to want to completely ignore the ~/bin and /usr/bin folders when executing custom build commands (I wrote a script to call cmake and make in the proper directories), and VSCode just SKIPS all my breakpoints (and it appears LLVM is completely ignoring the -g and excluding debug symbols)...
Has anyone been able to get a platform-independent toolset running on macos??? If so how have you been able to do this and what toolset + IDE are you using? If you were able to get XCode of VSCode to work how did you do it?
maybe I'm doing somthing wrong.
Here is my cmakelists.txt: (https://pastebin.com/RymrmUfk)
Here is my build command: (https://pastebin.com/wbdpccZ6)
I am trying to locate the documentation for the MacOS API. I know where all the C++/C libraries are -- I was able to locate them using xcode in the terminal.... but it would be nicer to have actual documentation to use instead of having to comb through a mountain of code for specific functionality.
I've tried digging around developer.apple.com but all I can find is nonsense about swift and frameworks. I'm more interested in system calls.
A quick google search for opcode documentation and all I could find were some opcodes for true type font and nothing else.
Does apple still maintain the C libraries MacOS inherited from Unix and if so where can I find the documentation on it? If not, is there a way to find documentation on system calls outside of loosing sand-sifter on the dam thing and engineering my own?
Also -- Where the hell is the opcode documentation for the M1 processor?