** Description changed: This is not a requirement but it will make it easier to navigate the code using language servers. Kernel has a script to generate this file. But it takes time because kernel needs to be compiled first. Since we already compile the kernels, we can simply run this script after compilation. + + What is different from other source code tagging tools (gtags etc)? This will + search within only the compiled source files & macros (part of sources which + are disabled for the current build will not be included in search space). This + makes it very useful for static analysis when there is a regression on certain + architecture.
** Description changed: This is not a requirement but it will make it easier to navigate the code using language servers. Kernel has a script to generate this file. But it takes time because kernel needs to be compiled first. Since we already compile the kernels, we can simply run this script after compilation. - What is different from other source code tagging tools (gtags etc)? This will - search within only the compiled source files & macros (part of sources which - are disabled for the current build will not be included in search space). This - makes it very useful for static analysis when there is a regression on certain - architecture. + What is different from other source code tagging tools (gtags etc)? This + will search within only the compiled source files & macros (part of + sources which are disabled for the current build will not be included in + search space). This makes it very useful for static analysis when there + is a regression on certain architecture. ** Description changed: + Here is a patch nobody asked for. + This is not a requirement but it will make it easier to navigate the code using language servers. Kernel has a script to generate this file. But it takes time because kernel needs to be compiled first. Since we already compile the kernels, we can simply run this script after compilation. What is different from other source code tagging tools (gtags etc)? This will search within only the compiled source files & macros (part of sources which are disabled for the current build will not be included in search space). This makes it very useful for static analysis when there is a regression on certain architecture. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2119438 Title: Include compile_commands.json in build info for language servers Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: New Status in linux source package in Plucky: New Status in linux source package in Questing: New Bug description: Here is a patch nobody asked for. This is not a requirement but it will make it easier to navigate the code using language servers. Kernel has a script to generate this file. But it takes time because kernel needs to be compiled first. Since we already compile the kernels, we can simply run this script after compilation. What is different from other source code tagging tools (gtags etc)? This will search within only the compiled source files & macros (part of sources which are disabled for the current build will not be included in search space). This makes it very useful for static analysis when there is a regression on certain architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2119438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
