Bug 3397 - New Package: cryptsetup
Summary: New Package: cryptsetup
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 enhancement
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
: 3385 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-03-07 16:06 UTC by Daniele Salvatore Albano
Modified: 2013-08-29 07:32 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Patch to add cryptsetup support (3.05 KB, application/octet-stream)
2011-03-07 16:06 UTC, Daniele Salvatore Albano 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniele Salvatore Albano 2011-03-07 16:06:13 UTC 
Created attachment 3085 [details]
Patch to add cryptsetup support

This package adds cryptsetup support to buildroot.

NOTE:
i've seen that there is an opened bug (#3385) that add a cryptsetup package but mine handle more stuff (disable selinux, copy only needed stuff, check for udev and has libgpg-error in deps) so i've opened a new bug
Comment 1 Martin Hicks 2011-03-07 16:14:03 UTC 
Looks good to me.
Comment 2 Martin Hicks 2011-03-07 16:15:14 UTC 
*** Bug 3385 has been marked as a duplicate of this bug. ***
Comment 3 Matthew Pirretti 2011-05-27 00:34:49 UTC 
Shouldn't it be:
ifneq ($(BR2_PACKAGE_UDEV),y)
	CRYPTSETUP_CONF_OPT += --disable-udev
endif

instead of:
ifneq ($(BR2_PACKAGE_UDEV),y)
	CRYPTSETUP_CONF_OPT = --disable-udev
endif

Otherwise if BR2_PACKAGE_UDEV=n, then --with-libgcrypt-prefix will not be defined and it won't build.
Comment 4 Thomas Petazzoni 2013-08-29 07:32:57 UTC 
A cryptsetup package has been committed as of http://git.buildroot.net/buildroot/commit/?h=next&id=21028166a5a9d09063eec916e4ad60c964cff27d. At the time of this writing, this commit is part of the 'next' branch, which will be merged into the 'master' branch after the 2013.08 release is done.

If you want to use it today, test the 'next' branch, or wait a few more days for the 2013.08 release to happen, at which point you'll find the package in the normal 'master' branch. If you only use stable releases of Buildroot, you'll have to wait until the 2013.11 release, which will incorporate this new package.