|author||Yasuhiro Matsumoto <firstname.lastname@example.org>||Tue Feb 26 10:12:26 2019|
|committer||Yasuhiro Matsumoto <email@example.com>||Tue Feb 26 10:12:26 2019|
Fix module name
Go bindings for Windows COM using shared libraries instead of cgo.
By Yasuhiro Matsumoto.
To experiment with go-ole, you can just compile and run the example program:
go get github.com/go-ole/go-ole cd /path/to/go-ole/ go test cd /path/to/go-ole/example/excel go run excel.go
Continuous integration configuration has been added for both Travis-CI and AppVeyor. You will have to add these to your own account for your fork in order for it to run.
Travis-CI was added to check builds on Linux to ensure that
go get works when cross building. Currently, Travis-CI is not used to test cross-building, but this may be changed in the future. It is also not currently possible to test the library on Linux, since COM API is specific to Windows and it is not currently possible to run a COM server on Linux or even connect to a remote COM server.
AppVeyor is used to build on Windows using the (in-development) test COM server. It is currently only used to test the build and ensure that the code works on Windows. It will be used to register a COM server and then run the test cases based on the test COM server.
The tests currently do run and do pass and this should be maintained with commits.
Go OLE uses semantic versioning for version numbers, which is similar to the version contract of the Go language. Which means that the major version will always maintain backwards compatibility with minor versions. Minor versions will only add new additions and changes. Fixes will always be in patch.
This contract should allow you to upgrade to new minor and patch versions without breakage or modifications to your existing code. Leave a ticket, if there is breakage, so that it could be fixed.
Under the MIT License: http://mattn.mit-license.org/2013