anulax
/
bakasable
1
0
Fork 0
Code Issues Pull Requests Packages project_board Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and dots ('.'), can be up to 35 characters long. Letters must be lowercase.
30 Commits
2 Branches
0 Tags
49 MiB
 
 
 
Tag: Branch: Tree: main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from "main"
${ noResults }
bakasable/bin/vendor/export-compile-commands
anulax1225 cf4f218675
Added compile commands module to premake for lsp intergration 		ago%!(EXTRA string=7 months)
..
README.md Added compile commands module to premake for lsp intergration ago%!(EXTRA string=7 months)
_manifest.lua Added compile commands module to premake for lsp intergration ago%!(EXTRA string=7 months)
_preload.lua Added compile commands module to premake for lsp intergration ago%!(EXTRA string=7 months)
export-compile-commands.lua Added compile commands module to premake for lsp intergration ago%!(EXTRA string=7 months)

README.md

Generate compile_commands.json for premake projects

This module implements JSON Compilation Database Format Specification for premake projects.

Install this module somewhere premake can find it, for example:

git clone https://github.com/tarruda/premake-export-compile-commands export-compile-commands

Then put this at the top of your system script(eg: ~/.premake/premake-system.lua):

require "export-compile-commands"

Note that while possible, it is not recommended to put the require line in project-specific premake configuration because the "export-compile-commands" module will need to be installed everywhere your project is built.

After the above steps, the "export-compile-commands" action will be available for your projects:

premake5 export-compile-commands

The export-compile-commands action will generate one json file per config/platform combination in each workspace, all under the compile_commands subdirectory. For example, say you have defined debug and release configurations with x32 and x64 platforms, the output will be something like:

Generated WORKSPACE_BUILD_DIR/compile_commands/debug_x32.json...
Generated WORKSPACE_BUILD_DIR/compile_commands/debug_x64.json...
Generated WORKSPACE_BUILD_DIR/compile_commands/release_x32.json...
Generated WORKSPACE_BUILD_DIR/compile_commands/release_x64.json...

where each file contain the compilation commands for the corresponding config/platform combo.