From: Luca Boccassi <luca.boccassi@gmail.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org
Subject: Re: [fsverity-utils PATCH v4 2/2] Allow to build and run sign/digest on Windows
Date: Mon, 21 Dec 2020 22:23:06 +0000 [thread overview]
Message-ID: <CAMw=ZnQmyCbdwfROSmZB-hZjzz=n_rH-fvykyU0vnVp4CGA=mA@mail.gmail.com> (raw)
In-Reply-To: <X+EWW4QIOtXtJpEU@sol.localdomain>
On Mon, 21 Dec 2020 at 21:40, Eric Biggers <ebiggers@kernel.org> wrote:
>
> On Thu, Dec 17, 2020 at 07:25:16PM +0000, luca.boccassi@gmail.com wrote:
> > From: Luca Boccassi <luca.boccassi@microsoft.com>
> >
> > Add some minimal compat type defs, and stub out the enable/measure
> > sources. Also add a way to handle the fact that mingw adds a
> > .exe extension automatically in the Makefile install rules, and
> > that there is not pkg-config and the libcrypto linker flag is
> > different.
> >
> > Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
>
> This commit message is outdated; can you update it?
Fixed in v5.
> > diff --git a/Makefile b/Makefile
> > index bfe83c4..a5aa900 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -35,6 +35,11 @@
> > cc-option = $(shell if $(CC) $(1) -c -x c /dev/null -o /dev/null > /dev/null 2>&1; \
> > then echo $(1); fi)
> >
> > +# Support building with MinGW for minimal Windows fsverity.exe
> > +ifneq ($(findstring -mingw,$(shell $(CC) -dumpmachine 2>/dev/null)),)
> > +MINGW = 1
> > +endif
> > +
> > CFLAGS ?= -O2
> >
> > override CFLAGS := -Wall -Wundef \
> > @@ -47,7 +52,7 @@ override CFLAGS := -Wall -Wundef \
> > $(call cc-option,-Wvla) \
> > $(CFLAGS)
> >
> > -override CPPFLAGS := -Iinclude -D_FILE_OFFSET_BITS=64 $(CPPFLAGS)
> > +override CPPFLAGS := -Iinclude -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE $(CPPFLAGS)
> >
> > ifneq ($(V),1)
> > QUIET_CC = @echo ' CC ' $@;
> > @@ -62,7 +67,12 @@ BINDIR ?= $(PREFIX)/bin
> > INCDIR ?= $(PREFIX)/include
> > LIBDIR ?= $(PREFIX)/lib
> > DESTDIR ?=
> > +ifneq ($(MINGW),1)
> > PKGCONF ?= pkg-config
> > +else
> > +PKGCONF := false
> > +EXEEXT := .exe
> > +endif
> >
> > # Rebuild if a user-specified setting that affects the build changed.
> > .build-config: FORCE
> > @@ -87,9 +97,9 @@ CFLAGS += $(shell "$(PKGCONF)" libcrypto --cflags 2>/dev/null || echo)
> > # If we are dynamically linking, when running tests we need to override
> > # LD_LIBRARY_PATH as no RPATH is set
> > ifdef USE_SHARED_LIB
> > -RUN_FSVERITY = LD_LIBRARY_PATH=./ ./fsverity
> > +RUN_FSVERITY = LD_LIBRARY_PATH=./ ./fsverity$(EXEEXT)
> > else
> > -RUN_FSVERITY = ./fsverity
> > +RUN_FSVERITY = ./fsverity$(EXEEXT)
> > endif
> >
> > ##############################################################################
> > @@ -99,6 +109,9 @@ endif
> > SOVERSION := 0
> > LIB_CFLAGS := $(CFLAGS) -fvisibility=hidden
> > LIB_SRC := $(wildcard lib/*.c)
> > +ifeq ($(MINGW),1)
> > +LIB_SRC := $(filter-out lib/enable.c,${LIB_SRC})
> > +endif
> > LIB_HEADERS := $(wildcard lib/*.h) $(COMMON_HEADERS)
> > STATIC_LIB_OBJ := $(LIB_SRC:.c=.o)
> > SHARED_LIB_OBJ := $(LIB_SRC:.c=.shlib.o)
> > @@ -141,10 +154,13 @@ PROG_COMMON_SRC := programs/utils.c
> > PROG_COMMON_OBJ := $(PROG_COMMON_SRC:.c=.o)
> > FSVERITY_PROG_OBJ := $(PROG_COMMON_OBJ) \
> > programs/cmd_digest.o \
> > - programs/cmd_enable.o \
> > - programs/cmd_measure.o \
> > programs/cmd_sign.o \
> > programs/fsverity.o
> > +ifneq ($(MINGW),1)
> > +FSVERITY_PROG_OBJ += \
> > + programs/cmd_enable.o \
> > + programs/cmd_measure.o
> > +endif
> > TEST_PROG_SRC := $(wildcard programs/test_*.c)
> > TEST_PROGRAMS := $(TEST_PROG_SRC:programs/%.c=%)
> >
>
> The Makefile target to build the binary is still "fsverity", but for Windows it
> actually builds "fsverity.exe". I think that when the .exe extension is added,
> the name of the Makefile target should change too. Makefile targets should be
> either a filename target *or* a special target, not conditionally either one.
Ok, updated in v5.
> > @@ -186,7 +202,7 @@ test_programs:$(TEST_PROGRAMS)
> > # want to run the full tests.
> > check:fsverity test_programs
> > for prog in $(TEST_PROGRAMS); do \
> > - $(TEST_WRAPPER_PROG) ./$$prog || exit 1; \
> > + $(TEST_WRAPPER_PROG) ./$$prog$(EXEEXT) || exit 1; \
> > done
>
> The .exe extension isn't being added to the test programs when they are built.
> Did you intend for building the test programs for Windows (and running them on
> Windows) to be supported?
Yes it probably should. Made further updates, and at least with
mingw/wine make check works.
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2020-12-21 22:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 14:47 [fsverity-utils PATCH v2 1/2] Remove unneeded includes luca.boccassi
2020-12-17 14:47 ` [fsverity-utils PATCH v2 2/2] Allow to build and run sign/digest on Windows luca.boccassi
2020-12-17 18:32 ` Eric Biggers
2020-12-17 18:44 ` Luca Boccassi
2020-12-17 19:05 ` Eric Biggers
2020-12-17 19:12 ` Luca Boccassi
2020-12-17 19:20 ` Eric Biggers
2020-12-17 19:26 ` Luca Boccassi
2020-12-17 19:16 ` [fsverity-utils PATCH v3 1/2] Remove unneeded includes luca.boccassi
2020-12-17 19:16 ` [fsverity-utils PATCH v3 2/2] Allow to build and run sign/digest on Windows luca.boccassi
2020-12-17 19:25 ` [fsverity-utils PATCH v4 1/2] Remove unneeded includes luca.boccassi
2020-12-17 19:25 ` [fsverity-utils PATCH v4 2/2] Allow to build and run sign/digest on Windows luca.boccassi
2020-12-21 21:40 ` Eric Biggers
2020-12-21 22:23 ` Luca Boccassi [this message]
2020-12-21 22:19 ` [PATCH v5] " Luca Boccassi
2020-12-21 23:03 ` Eric Biggers
2020-12-21 23:26 ` Luca Boccassi
2020-12-21 23:24 ` [PATCH v6 1/3] Move -D_GNU_SOURCE to CPPFLAGS Luca Boccassi
2020-12-21 23:24 ` [PATCH v6 2/3] Wrap ./fsverity in TEST_WRAPPER_PROG too Luca Boccassi
2020-12-21 23:24 ` [PATCH v6 3/3] Allow to build and run sign/digest on Windows Luca Boccassi
2020-12-21 23:53 ` Eric Biggers
2020-12-21 23:57 ` Luca Boccassi
2020-12-22 0:03 ` Eric Biggers
2020-12-22 0:11 ` Luca Boccassi
2020-12-22 0:00 ` [PATCH v6 1/3] Move -D_GNU_SOURCE to CPPFLAGS Eric Biggers
2020-12-22 0:12 ` Luca Boccassi
2020-12-22 0:10 ` [PATCH v7 " Luca Boccassi
2020-12-22 0:10 ` [PATCH v7 2/3] Wrap ./fsverity in TEST_WRAPPER_PROG too Luca Boccassi
2020-12-22 18:41 ` Eric Biggers
2020-12-22 0:10 ` [PATCH v7 3/3] Allow to build and run sign/digest on Windows Luca Boccassi
2020-12-22 18:40 ` Eric Biggers
2020-12-22 8:21 ` [PATCH v7 1/3] Move -D_GNU_SOURCE to CPPFLAGS Eric Biggers
2020-12-22 18:40 ` Eric Biggers
2020-12-21 21:32 ` [fsverity-utils PATCH v4 1/2] Remove unneeded includes Eric Biggers
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='CAMw=ZnQmyCbdwfROSmZB-hZjzz=n_rH-fvykyU0vnVp4CGA=mA@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
/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 NNTP newsgroup(s).