valitydev/thrift
14
0
Fork 0
mirror of https://github.com/valitydev/thrift.git synced 2024-11-07 18:58:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
3f2e710152
thrift/lib/d
History
Jens Geyer e84c582531 THRIFT-2916 Add default toHash method to 'class' and 'struct' to meet D's associative arrays requirement. 
Client: D
Patch: Phongphan Phuttha <phongphan@acm.org>

This closes #503
2015-05-19 01:33:23 +02:00
..
src/thrift THRIFT-2916 Add default toHash method to 'class' and 'struct' to meet D's associative arrays requirement. 2015-05-19 01:33:23 +02:00
test THRIFT-2886 Integrate binary type in standard Thrift cross test 2015-01-03 17:37:54 +01:00
coding_standards.md THRIFT-3148 Markdown links to coding_standards are dead 2015-05-13 21:40:26 +02:00
Makefile.am THRIFT-2781: D compiler stuck at idlgen due to compiler bug 2014-10-10 19:30:58 +02:00
README.md THRIFT-2407 use markdown (rename README => README.md) 2014-03-19 06:47:47 +01:00

README.md

Thrift D Software Library

License

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Testing

D support in Thrift is covered by two sets of tests: first, the unit test blocks contained in the D source files, and second, the more extensive testing applications in the test/ subdirectory, which also make use of the Thrift compiler. Both are built when running "make check", but only the unit tests are immediately run, however – the separate test cases typically run longer or require manual intervention. It might also be prudent to run the independent tests, which typically consist of a server and a client part, against the other language implementations.

To build the unit tests on Windows, the easiest way might be to manually create a file containing an empty main() and invoke the compiler by running the following in the src/ directory (PowerShell syntax):

dmd -ofunittest -unittest -w $(dir -r -filter '*.d' -name)

If you want to run the test clients/servers in OpenSSL mode, you have to provide »server-private-key.pem« and »server-certificate.pem« files in the directory the server executable resides in, and a »trusted-ca-certificate.pem« file for the client. The easiest way is to generate a new self signed certificate using the provided config file (openssl.test.cnf):

openssl req -new -x509 -nodes -config openssl.test.cnf
-out server-certificate.pem cat server-certificate.pem > trusted-ca-certificate.pem

This steps are also performed automatically by the Autotools build system if the files are not present.