Generate compile_commands.json #26
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#27 generate compile commands
kevintl1998/yapp-clangd.nvim
Reference
kevintl1998/yapp-clangd.nvim#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Required for background indexing to work which enables jumping to symbols in files which have not been opened.
Library includes in non-standard locations require the addition of a '-L[path/to/library]' flag to tell the compiler where the library is located. In the compile command, the -L flags should be placed after the library -l (lowercase L) includes and the library -l includes should be placed after the -I (uppercase i) file includes. Basically, libraries and files which reference other files/libraries should be placed after the files/libraries they are referencing.
-L tells the linker where to find library files at compile time. An alternate flag -R is available on some systems to specify library paths at runtime. Paths included with -R will be inserted into the resulting binary.
https://stackoverflow.com/questions/31455979/how-to-specify-libraries-paths-in-gcc
Need to improve my current method for determining the correct python executable. On windows, 'where python3' prints out the path that python3 would be installed if it was installed through the windows store.