Conversation
Note that unicode is not currently supported in rapidjson::document
|
Have we checked in with the other teams that use DView if they're ok with picking up SSC as a dependency? I get why we'd want to do this for our workflow (having Wex as a dependency of SSC seems worse), but it might be worth developing an alternative build process so Wex & DView can be built without SSC. Would the RapidJSON path as an environment variable do the trick? Apologies if I missed a discussion about this during a meeting. |
The dependency is for rapid json only…in utility.cpp and uniform.cpp. alternatives are to place rapid json (one header file in wex, too - then no dependencies either way. If rapidjson was in wex only, then ssc would be dependent on wex…. |
| ##################################################################################################################### | ||
|
|
||
| # for rapidjson folder in ssc | ||
| include_directories($ENV{SSCDIR}) |
There was a problem hiding this comment.
Would an environment variable RAPIDJSONDIR work? For SAM developers, this could be set to the SSC directory. Developers without SSC could set it to some other directory with rapidjson. (this might be a good item for the meeting agenda tomorrow)
There was a problem hiding this comment.
Would an environment variable RAPIDJSONDIR work? For SAM developers, this could be set to the SSC directory. Developers without SSC could set it to some other directory with rapidjson. (this might be a good item for the meeting agenda tomorrow)
Updated and working in wex, SAM and SAM-private.
encoding and decoding of escape characters failing.
brtietz
left a comment
There was a problem hiding this comment.
This is great, thank you!
Associated pull requests in SAM and SAM-private