From: Milan Broz <gmazyland@gmail.com>
To: Surmont Jasper <jasper.surmont@aalto.fi>,
cryptsetup development <cryptsetup@lists.linux.dev>
Subject: Re: Development environment preparation
Date: Mon, 4 Apr 2022 08:53:05 +0200 [thread overview]
Message-ID: <3a31492f-c942-2e8e-107e-99ab0de3814b@gmail.com> (raw)
In-Reply-To: <PR3P192MB1087A708C36CD34F77AC517CF1E59@PR3P192MB1087.EURP192.PROD.OUTLOOK.COM>
On 04/04/2022 08:31, Surmont Jasper wrote:
> Hey!
>
> I'm trying to analyze the code of the cryptsetup project. In general I prefer to browse and analyze the code in VSCode. However, after setting everything up and including all the header files, there are certain macro's that are, according to vscode, not defined.
> These are Macro's like: DEFAULT_VERITY_HASH, DEFAULT_LOOPAES_KEYBITS, PACKAGE_NAME etc.
>
> Is there something I did wrong? Or should I make something first? I can't really find an answer on the docs / issues on gitlab. Thanks!
These comes from generated file config.h according to configure settings.
So you did not run autoconf.
If you use git, first you need to prepare autogen.sh, then run configure.
If you use released tarball, configure is already generated there, so just run it.
It is always good to start with README, as it configure --help is also mentioned there.
But I guess we lost some info about build from old INSTALL file, though. That should be fixed.
Milan
prev parent reply other threads:[~2022-04-04 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 6:31 Development environment preparation Surmont Jasper
2022-04-04 6:53 ` Milan Broz [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=3a31492f-c942-2e8e-107e-99ab0de3814b@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
--cc=jasper.surmont@aalto.fi \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).