BigfootDev/flatbuffers
1
0
Fork 1
mirror of https://github.com/google/flatbuffers.git synced 2026-06-29 16:42:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document FlatCC support for Windows

Browse Source
This commit is contained in:
Mikkel Fahnøe Jørgensen
2016-04-03 21:37:57 +02:00
parent 7d9779fc67
commit 5b38134431
2 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/source/CUsage.md
View File

@@ -7,7 +7,7 @@ The `flatcc` C schema compiler can generate code offline as well as
online via a C library. It can also generate buffer verifiers and fast online via a C library. It can also generate buffer verifiers and fast
JSON parsers, printers. JSON parsers, printers.
Great effort has been made to ensure compatibily with the main `flatc` Great care has been taken to ensure compatibily with the main `flatc`
project. project.
@@ -21,13 +21,16 @@ project.
## Supported Platforms ## Supported Platforms
Ubuntu and OS-X are regularly tested during releases. Centos 7.1 Not all platforms are tested regularly but the following platforms have
has also been tested. Cross compilation to little-endian ARM has been all successfully built and passed all tests:
reported to work with warnings.
Windows has not been tested. The `include/flatcc/portable` library is - 64-bit Ubuntu 14.04, gcc, CMake with Ninja Build or GNU Make
intended to abstract platform differences, including Windows. User - 64-bit OS-X 10.11, Apple Clang, CMake with Ninja Build or GNU Make
feedback and patches are welcome. - 64-bit Centos 7.1, CMake with GNU Make
- 32-bit Windows 10, CMake with MSVC 14 2015
ARM cross compilation from Linux has been reported to work to some
extend.
Big endian platforms have not been tested and may contain bugs, but care Big endian platforms have not been tested and may contain bugs, but care
has been taken to provide support for it. has been taken to provide support for it.
@@ -167,7 +170,7 @@ point.
The `FLATBUFFERS_WRAP_NAMESPACE` approach used in the tutorial is convenient The `FLATBUFFERS_WRAP_NAMESPACE` approach used in the tutorial is convenient
when each function has a very long namespace prefix. But it isn't always when each function has a very long namespace prefix. But it isn't always
we the best approach. If the namespace is absent, or very simple and the best approach. If the namespace is absent, or simple and
informative, we might as well use the prefix directly. The informative, we might as well use the prefix directly. The
[reflection example](https://github.com/dvidelabs/flatcc/blob/master/samples/reflection/bfbs2json.c) [reflection example](https://github.com/dvidelabs/flatcc/blob/master/samples/reflection/bfbs2json.c)
mentioned above uses this approach. mentioned above uses this approach.
@@ -202,7 +205,7 @@ points in time.
// or alternatively // or alternatively
ns(Monster_equipped_Weapon_add(B, axe); ns(Monster_equipped_Weapon_add(B, axe);
// or alternatively // or alternatively
ns(Monster_equipped_type_add(B, ns(Equipment_Weapon)); ns(Monster_equipped_add_type(B, ns(Equipment_Weapon));
ns(Monster_equipped_add_member(B, axe)); ns(Monster_equipped_add_member(B, axe));
~~~ ~~~
</div> </div>

2
docs/source/Support.md
View File

@@ -28,7 +28,7 @@ Buffer verifier | Yes | No | No | No | No | No
Testing: basic | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ? | ? Testing: basic | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ? | ?
Testing: fuzz | Yes | No | No | Yes | Yes | No | No | ? | ? Testing: fuzz | Yes | No | No | Yes | Yes | No | No | ? | ?
Performance: | Superb | Great | Great | Great | Ok | ? |Superb| ? | ? Performance: | Superb | Great | Great | Great | Ok | ? |Superb| ? | ?
Platform: Windows | VS2010 | Yes | Yes | ? | ? | ? | ? | ? | ? Platform: Windows | VS2010 | Yes | Yes | ? | ? | ? | Yes | ? | ?
Platform: Linux | GCC282 | Yes | ? | Yes | Yes | ? | Yes | ? | ? Platform: Linux | GCC282 | Yes | ? | Yes | Yes | ? | Yes | ? | ?
Platform: OS X | Xcode4 | ? | ? | ? | Yes | ? | Yes | ? | ? Platform: OS X | Xcode4 | ? | ? | ? | Yes | ? | Yes | ? | ?
Platform: Android | NDK10d | Yes | ? | ? | ? | ? | ? | ? | ? Platform: Android | NDK10d | Yes | ? | ? | ? | ? | ? | ? | ?