Development

For Windows, see the README_WIN.md - oh yeah, its not so simple

The following is for various flavors of linux.

Building

Building and test of the module is simple. The make targets to use when updating code and testing are: * blddev * testdev

There are build targets for Centos 6 and 7 as well. It may be useful when trying to repeat a customer issue. * blddevc7 * blddevc6 * blddevc6-32

There is also a build target for 32bit on centos6. There is one customer who uses that package. Hopefully nothing else has to be done there specifically for it.

Testing

The tests are not fast however. They are setup to to try different configurations with automated checks for the results in associated output logs. For that reason, each test will have created its own output logs named with the test number. For example, test 29 will have produced error.log_29_ubu1604

There will be an associated agent.log with which to manually verify results as well.

There are targets in the Makefile for testing, see: * testdev : depends on module built with target blddev * testdevc7 : depends on module built with target blddevc7 * testdevc6 : depends on module built with target blddevc6 * testdevc6-32 : depends on module built with target blddevc6-32

Versioning

Update the following files when making a release: * VERSION * sigsciversion.h * CHANGELOG.md * nfpm.yaml