Lines Matching +full:getting +full:- +full:started
1 ---
5 grand_parent: Getting started
7 permalink: /getting-started/new-project-guide/go-lang/
8 ---
13 - TOC
15 ---
17 The process of integrating a project written in Go with OSS-Fuzz is very similar
19 [Setting up a new project]({{ site.baseurl }}/getting-started/new-project-guide/)
22 ## Go-fuzz support
24 OSS-Fuzz supports **go-fuzz** in the
25 [libFuzzer compatible mode](https://github.com/mdempsky/go114-fuzz-build)
28 libFuzzer command line interface as non-Go fuzz targets.
37 The structure of the project directory in OSS-Fuzz repository doesn't differ for
51 [Example](https://github.com/google/oss-fuzz/blob/356f2b947670b7eb33a1f535c71bc5c87a60b0d1/projects…
55 - libfuzzer
57 - address
62 The Dockerfile should start by `FROM gcr.io/oss-fuzz-base/base-builder-go`
64 The OSS-Fuzz builder image has the latest stable release of Golang installed. In
67 [Example](https://github.com/google/oss-fuzz/blob/356f2b947670b7eb33a1f535c71bc5c87a60b0d1/projects…
71 RUN git clone --depth 1 https://github.com/ianlancetaylor/demangle
74 go-fuzz will then automatically download the dependencies based on the go.mod file
78 In order to build a Go fuzz target, you need to call `go-fuzz`
85 A usage example from go-dns project is