- Website: http://www.quickfixgo.org
- Mailing list: Google Groups
Open Source FIX Protocol library implemented in Go
To install QuickFIX/Go, use go get
:
$ go get github.com/quickfixgo/quickfix
To update QuickFIX/Go to the latest version, use go get -u github.com/quickfixgo/quickfix
.
See examples for some simple examples of using QuickFIX/Go.
QuickFIX/Go includes fields, enums, messages, and message components generated from the FIX 4.0 - FIX5.0SP2 specs. For most FIX applications, these generated resources are sufficient. Custom FIX applications may generate source specific to the FIX spec of that application using the generate-fix
tool included with QuickFIX/Go.
Following installation, generate-fix
is installed to $GOPATH/bin/generate-fix
. Run $GOPATH/bin/generate-fix --help
for usage instructions.
If you wish to work on QuickFIX/Go itself, you will first need Go installed on your machine (version 1.6+ is required).
For local dev first make sure Go is properly installed, including setting up a GOPATH.
Next, using Git, clone this repository into $GOPATH/src/github.com/quickfixgo/quickfix
.
QuickFIX/Go uses govendor to manage the vendored dependencies. Install govendor with go get
:
$ go get github.com/kardianos/govendor
Run govendor sync
to install the correct versioned dependencies into `vendor/, which Go 1.6+ automatically recognizes and loads.
$ $GOPATH/bin/govendor sync
Note: No vendored dependencies are included in the QuickFIX/Go source.
The default make target runs go vet and unit tests.
$ make
If this exits with exit status 0, then everything is working!
QuickFIX/Go has a comprehensive acceptance test suite covering the FIX protocol. These are the same tests used across all QuickFIX implementations.
QuickFIX/Go acceptance tests depend on ruby in path.
To run acceptance tests,
# build acceptance test rig
make build_accept
# run acceptance tests
make accept
For convenience, generated code from the FIX40-FIX50SP2 specs are included in the QuickFIX/Go repo. The source specifications for this generated code is located in spec/
. Generated code can be identified by the .generated.go
suffix. Any changes to generated code must be captured by changes to source in cmd/generate-fix
. After making changes to the code generator source, run the following to re-generate the source
$ make generate
If you are making changes to the generated code, you will need to include the generated source in the same Pull Request as the changes made to the code generator. You should do this in a separate commit from your code, as this makes PR review easier and Git history simpler to read in the future.
If you are developing QuickFIX/Go, there are a few tasks you might need to perform related to dependencies.
If you are adding a dependency, you will need update the govendor manifest in the same Pull Request as the code that depends on it. You should do this in a separate commit from your code, as this makes PR review easier and Git history simpler to read in the future.
To add a dependency:
Assuming your work is on a branch called my-feature-branch
, the steps look like this:
-
Add the new package to your GOPATH:
go get github.com/quickfixgo/my-project
-
Add the new package to your vendor/ directory:
govendor add github.com/quickfixgo/my-project
-
Review the changes in git and commit them.
To update a dependency:
-
Fetch the dependency:
govendor fetch github.com/quickfixgo/my-project
-
Review the changes in git and commit them.
This software is available under the QuickFIX Software License. Please see the LICENSE.txt for the terms specified by the QuickFIX Software License.