From: Kwanghoon Son <k.son@samsung.com>
To: Jasper Surmont <surmontjasper@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Linux kernel environment setup in VSCode
Date: Mon, 25 Apr 2022 10:36:10 +0900 [thread overview]
Message-ID: <20220425013610.GA18461@kwang-host> (raw)
In-Reply-To: <5cc55f35-7513-731d-6e6f-dd6cbf0d6765@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On Mon, Apr 04, 2022 at 09:31:46PM +0300, Jasper Surmont wrote:
> Hey,
>
> I'm new to the Linux kernel development, and I wanted to set up a VSCode
> environment for navigating the code (I know, even though people tell me Vim
> is better but currently I'm really not comfortable with it yet).
> My main goal is just navigating and understanding. I've been able to make a
> lot work, and using the C/C++ extension from Microsoft I have good
> IntelliSense.
>
> However, some things are getting flagged by the extension as errors (which
> of course shouldn't, since I've been able to compile the kernel).
> These are things like: identifiers being undefined (for example, in
> kernel/sched/cpudeadline.c u64 is undefined) and errors like: function
> returning array is not allowed (for example, in drivers/md/dm-zero.c on the
> bottom).
vscode use clang and needs clangd.
you can generate from ./scripts/clang-tools/gen_compile_commands.py
which makes you navigate source code!
> I'm wondering if I'm forgetting things such that all these things get
> resolved. Any tips are appreciated.
>
>
> Thanks!
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-05-01 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220425013611epcas1p429b2ec55ce20472304e4ce28b32e4381@epcas1p4.samsung.com>
2022-04-04 18:31 ` Linux kernel environment setup in VSCode Jasper Surmont
2022-04-08 2:53 ` Minh Dang
2022-04-14 20:35 ` Pavel Skripkin
2022-04-25 1:36 ` Kwanghoon Son [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220425013610.GA18461@kwang-host \
--to=k.son@samsung.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=surmontjasper@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox