-
Notifications
You must be signed in to change notification settings - Fork 37
/
openfst.user.props
77 lines (60 loc) · 2.94 KB
/
openfst.user.props
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!--
User settings, to simplify setup. The names and values of make variables
used by MsBuild scripts are not obvious, so I thought it would be easier
if the list of user choices in available in a single file.
All settings are disabled by default. Enable any of them by removing the
'Condition="false"' part, or change 'false' to 'true'.
You can instead specify these values in MSBuild command line. For example,
you can put the following command into a build.cmd file:
msbuild openfst.sln -v:m -m -t:Build ^
-p:Platform=x64 ^
-p:Configuration=Release ^
-p:PlatformToolset=v141 ^
-p:WindowsTargetPlatformVersion=10.0.16299.0 ^
-p:EnableFeatures="far;mpdt;pdt" ^
-p:EnableEnhancedInstructionSet=AdvancedVectorExtensions
-->
<PropertyGroup>
<!--
Optional features (after ./configure -enable-FEATURE, except without the
"-fst" suffix present on some of them). All features are compiled
together, into the same libfst and libfstscript libraries, and produce
their corresponding binaries if you compile the 'bin' project.
Supported optional features:
far enable FAR extensions
NOT yet supported:
const enable ConstFst extensions
compact enable CompactFst extensions
compress enable compression extension
linear enable LinearTagger/ClassifierFst extensions
lookahead enable LookAheadFst extensions
mpdt enable MPDT extensions
ngram enable NGramFst extension
pdt enable PDT extensions
special enable special-matcher extensions
Separate features with the semicolon, for example:
<EnableFeatures>const;far</EnableFeatures>
Note: 'configure -enable-grm' enables "far;mpdt;pdt".
-->
<EnableFeatures>far</EnableFeatures>
<!--
Toolset (default is v141 if not specified).
-->
<!-- v140 = 14.0, comes with VS14 aka VS 2015 -->
<PlatformToolset Condition="false" >v140</PlatformToolset>
<!-- v141 = 14.1, comes with VS15 aka VS 2017. This is the default. -->
<PlatformToolset Condition="false" >v141</PlatformToolset>
<!--
Enhanced instruction set (default SSE2, I believe).
NOTE: In kkm's experience, AVX helps the performance a little
(few % at most), AVX2 does not improve performance further. YMMV:
Maybe it's our FST structure that does not benefit from optimization.
Currently, there is no MS c2 codegen for AVX512 instructions.
Note: cl 32-bit compiler likely does not support AVX/AVX2. -->
<!-- AVX -->
<EnableEnhancedInstructionSet Condition="false" >AdvancedVectorExtensions</EnableEnhancedInstructionSet>
<!-- AVX2 -->
<EnableEnhancedInstructionSet Condition="false" >AdvancedVectorExtensions2</EnableEnhancedInstructionSet>
</PropertyGroup>
</Project>