Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates Makefile to properly build lcpchecker #1

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
build/

# Binaries for programs and plugins
*.exe
*.exe~
Expand Down
4 changes: 2 additions & 2 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ BUILD_DIR=$(ROOT_DIR)/build
UNAME_S= $(shell uname -s)
ARCH=amd64

lcpchecker=cmd/lcpchecker.go
lcpchecker=cmd/lcpchecker/lcpchecker.go

#LDFLAGS=-ldflags '-linkmode external -w -extldflags "-static"'
LDFLAGS=
Expand All @@ -23,4 +23,4 @@ clean:
$(rm) $(BUILD_DIR)

$(lcpchecker):
GOPATH=$(BUILD_DIR) GOARCH=$(ARCH) $(CC) ./$@
GOPATH=$(BUILD_DIR) GOARCH=$(ARCH) $(CC) ./$@
5 changes: 4 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,9 @@ A lightweight content management server will also be released, named `pubstore`,

Before these tools are available, the current Encryption Tool and Test Frontend Server will be usable with this new lcp-server (their API will be adapted to do so).

`lcpchecker`:
* Simply run `make` in the root of this repository; The binary will be output to `build/bin/lcpchecker` by default.

## Configuration

The configuration is similar to the v1 config, but simplified.
Expand Down Expand Up @@ -289,4 +292,4 @@ Gorm officially supports the following databases: SQLite, MySQL, PostgreSQL, SQL

Note: The proper driver must be included in the codebase and the codebase recompiled for a given database to be usable. See: [https://gorm.io/docs/connecting_to_the_database.html](https://gorm.io/docs/connecting_to_the_database.html) 

The open-source codebase is provided with an **sqlite** driver. It is up to integrators to replace it by the driver of their choice if sqlite does not fit their needs.
The open-source codebase is provided with an **sqlite** driver. It is up to integrators to replace it by the driver of their choice if sqlite does not fit their needs.