-
Notifications
You must be signed in to change notification settings - Fork 50
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 C++ versions before C++17 with boost::filesystem
#177
Support C++ versions before C++17 with boost::filesystem
#177
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]>
Please close #169 ( I hope that works ) For the moment, we have only support for BOOST_FILESYSTEM_VERSION 3. We make use of an SDK, which is in the moment not subject of change (HW support issues with later SDKs). I understand the point, as adding this change into mainline path, affects, many files and includes the start of having #defines inside the code and the CMakefile modification. Without the pull request, the files have to be changed, after each release update to make use of libocpp with our SDK. Summary: I have no real good argument, only that it is simpler to be follow libocpp updates with our SDK, without hand patching to many files. Modification: The #ifndef switches good be placed into a header file, and this header file being included, to increase the readability. |
That would be really nice to avoid a lot of duplication. I suggest to name the file Perhaps we might move this to a common repo soon. See related |
I think you should be able to do it as well (as PR-creator). At least only you can delete the branch in your fork. |
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
boost::filesystem
`cmake` failed with CMake Error at lib/CMakeLists.txt:94 (target_link_libraries): Target "ocpp" links to: Boost::filesystem but the target was not found. Possible reasons include: * There is a typo in the target name. * A find_package call is missing for an IMPORTED target. * An ALIAS target is missing. Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
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.
LGTM
@bWF0dGhpYXMK Can you check if it's still working on your side, please?
@hikinggrass Please review.
Thank you, i recompiled and worked here using boost::filesystem. |
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Matthias Suess <[email protected]>
Signed-off-by: Dominik K <[email protected]>
Signed-off-by: Dominik K <[email protected]>
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.
LGTM
boost::filesystem
boost::filesystem
Supporting C++-versions older than C++17. See comment below for background.