-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of security profile for example charge_point #246
Support of security profile for example charge_point #246
Conversation
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
@@ -100,8 +100,42 @@ int main(int argc, char* argv[]) { | |||
fs::create_directories(cso_path); | |||
} | |||
|
|||
const fs::path csms_path = "/tmp/client/csms"; | |||
if (!fs::exists(csms_path)) { | |||
fs::create_directories(csms_path); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't you explicitly include ocpp/common/support_older_cpp_versions.hpp
for the fs
namespace? It seems it is implicitly included via some other #include
. (I don't know about EVerest's code policy on this, feel free to clarify).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your comments; yes, it is included over the charge_point.hpp, i have no clear opinion on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
implicitly included via some other #include
I'm in favour to explicitly include them. Just found the IWYU (https://include-what-you-use.org/) tool which checks this (at least it should, don't have own experience with it, yet).
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Kai-Uwe Hermann <[email protected]>
No description provided.