| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
closes #545
|
| |
|
|
| |
closes #526
|
| | |
|
| |
|
|
|
|
| |
Apple LLVM version 7.0.2 (clang-700.1.81)
Close #386
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Building with -tags libsqlite3 used the sqlite3.h from the system but the go
compiler will compile all *.{c,h} files in the same direcory:
"When the Go tool sees that one or more Go files use the special import
"C", it will look for other non-Go files in the directory and compile
them as part of the Go package. Any .c, .s, or .S files will be compiled
with the C compiler." (https://golang.org/cmd/cgo/)
So if users actually want to link against the system sqlite3 we should make
sqlite3-binding.* a noop.
Signed-off-by: Christian Brauner <christian.brauner@canonical.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The purpose is to ease the use of vendoring files like godep.
The C sqlite3 files have been added a go compilation conditional flag
Fix #293
|
| |
|
|
| |
$ go build -tags "libsqlite3 windows"
|
|
|
This fixes the problem where when building with gccgo, sqlite3.c is
overwritten, leading to a build failure.
An alternative would have been to move sqlite3*.{c,h} to a subdirectory,
but that seems to confuse the linker a fair bit and would just swap one
implementation-dependent issue for another.
Closes #20
Signed-off-by: Stéphane Graber <stgraber@ubuntu.com>
|