[
https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185170#comment-17185170
]
Robert Middleton commented on LOGCXX-510:
-----------------------------------------
I figured it out(on my side at least). Basically, the issue comes down to the
fact that the PATH in Windows is semicolon-separated, and lists in CMake are
really just strings with semicolons in them, so you need to do the correct
amount of escaping.
Some details:
[https://stackoverflow.com/questions/59862894/how-do-i-make-a-list-in-cmake-with-the-semicolon-value]
branch with fixes and more explanation:
[https://github.com/apache/logging-log4cxx/tree/logcxx_510_rm_vs2019]
Note that $<SHELL_PATH:$<TARGET_FILE_DIR:log4cxx>> doesn't get resolved until
later in the CMake build process; if you're printing it out doing something
like message( $<SHELL_PATH:$<TARGET_FILE_DIR:log4cxx>> ) it will print out
"$<SHELL_PATH:$<TARGET_FILE_DIR:log4cxx>>".
> Build problems using CMAKE and Visual Studio 2019 Community
> -----------------------------------------------------------
>
> Key: LOGCXX-510
> URL: https://issues.apache.org/jira/browse/LOGCXX-510
> Project: Log4cxx
> Issue Type: Bug
> Components: Build
> Affects Versions: 0.11.0
> Reporter: Thorsten Schöning
> Assignee: Thorsten Schöning
> Priority: Major
> Attachments: CMP00079.png, CMakeSettings.json,
> cmake_settings_using_vs_gui.zip, missing_log4cxx_rc.png,
> set_target_properties.png
>
>
> I just tested building log4cxx using CMAKE and Visual Studio 2019 Community.
> Things failed and I want to use this bug to document everything that I've
> found, because for some things I'm not sure how to handle them properly. Will
> create a new branch to maintain the fixes I came along, so that those can at
> best be later reviewed by others. The branch of interest is currently named
> "logcxx_510_cmake_vs2019_compat".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
