[jira] [Commented] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[
https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146047#comment-17146047
]
Thorsten Schöning commented on LOGCXX-510:
--
{quote}Hmm, I'm able to compile perfectly fine using VS2019(after compiling
APR, APR-util, and expat of course).{quote}
I just opened VS, said to just want to open some folder to work on the
containing code and VS did things automatically when opening the CMAKE-files
afterwards. I didn't care about APR etc. yet, but the printed errors didn't
seem to be related anyway at first. When I'm doing the same right now, I get
APR-related errors:
{quote}1> [CMake] CMake Error at C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164
(message):
1> [CMake] APR_INCLUDE_DIR (missing: APR_LIBRARIES)
1> [CMake] Call Stack (most recent call first):
1> [CMake] C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:445
(_FPHSA_FAILURE_MESSAGE)
1> [CMake] src/cmake/FindAPR.cmake:57 (find_package_handle_standard_args)
1> [CMake] CMakeLists.txt:16 (find_package)
1> [CMake] -- Configuring incomplete, errors occurred!
{quote}
So maybe the order of execution of whatever really has an influence of what is
considered an error when. I love the fun build tools regularly introduce into
work... :-/
{quote}Are you running the non-bundled version of CMake? Do you have
cygwin/mingw on your PATH?{quote}
No, issuing "cmake" on the shell fails as well and VS prints the following in
the console output:
{quote}1> Befehlszeile: "cmd.exe" /c ""C:\PROGRAM FILES (X86)\MICROSOFT VISUAL
STUDIO\2019\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe"
-G "Ninja"
-DCMAKE_INSTALL_PREFIX:PATH="C:\Users\tschoening\Documents\Svn\Src\Libs\trunk\C++\Logging\log4cxx\0.11.0-SNAPSHOT\src\out\install\x64-Debug
(Standard)" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files (x86)/Microsoft
Visual Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/HostX64/x64/cl.exe"
-DCMAKE_BUILD_TYPE="Debug" -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES
(X86)\MICROSOFT VISUAL
STUDIO\2019\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe"
"C:\Users\tschoening\Documents\Svn\Src\Libs\trunk\C++\Logging\log4cxx\0.11.0-SNAPSHOT\src"
2>&1"{quote}
{quote}Alternatively, could your path be too deep? Windows can act funny if
you have too many characters in the path. I'm not sure if you're there yet,
but that path does look very long.{quote}
I's just ~120 chars, that shouldn't be a problem yet. And to my surprise it
seems that CMAKE properly supports long Unicode paths on Windows anyway:
{quote}[...]It also mentions the \\?\ UNC prefix for accessing paths beyond the
limit with no special settings. CMake internally uses that extended path
syntax when accessing Windows filesystem APIs, and CMake itself has no problem
using long paths.{quote}
https://gitlab.kitware.com/cmake/cmake/-/issues/19675#note_621318
> 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, 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)
[jira] [Commented] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[ https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145906#comment-17145906 ] Robert Middleton commented on LOGCXX-510: - Hmm, I'm able to compile perfectly fine using VS2019(after compiling APR, APR-util, and expat of course). Are you running the non-bundled version of CMake? Do you have cygwin/mingw on your PATH? I'm wondering if one of those is messing up the tools that Visual Studio is trying to use. The quotes around the VERSION/SOVERSION should be fine, although I'm very confused as to why I don't have any errors at all. Alternatively, could your path be too deep? Windows can act funny if you have too many characters in the path. I'm not sure if you're there yet, but that path does look very long. > 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, 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)
[jira] [Commented] (LOGCXX-511) C# - Log4Net Log not logging properly Asynchronous method
[ https://issues.apache.org/jira/browse/LOGCXX-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145771#comment-17145771 ] Matt Sicker commented on LOGCXX-511: https://logging.apache.org/mailing-lists.html See the dev list section. > C# - Log4Net Log not logging properly Asynchronous method > -- > > Key: LOGCXX-511 > URL: https://issues.apache.org/jira/browse/LOGCXX-511 > Project: Log4cxx > Issue Type: Bug >Reporter: Rajesh >Priority: Critical > Attachments: Log4NetAsynchronous.zip > > > We are using log4net in our application. The real problem is the log messages > not properly logged in Asynchronous method. > We have two applications First one is Console Application and another one is > a .Net Web API. > We use Asynchronous logic in Console application. We are calling API service > in that Console application through Asynchronous method. Log4net implemented > in that API application also. > We have logged all the requests in that API service, but sometimes the log > was not properly logged or skipped in the log file. > Ex: The Console application calling 1000 times in that API service. But the > API service not writing all the requests, skipped 10 or 20 requests. > Any one please do the help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LOGCXX-511) C# - Log4Net Log not logging properly Asynchronous method
[ https://issues.apache.org/jira/browse/LOGCXX-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145741#comment-17145741 ] Rajesh commented on LOGCXX-511: --- Yes I'm interested. Kindly help on this. How to join developer mailing list. > C# - Log4Net Log not logging properly Asynchronous method > -- > > Key: LOGCXX-511 > URL: https://issues.apache.org/jira/browse/LOGCXX-511 > Project: Log4cxx > Issue Type: Bug >Reporter: Rajesh >Priority: Critical > Attachments: Log4NetAsynchronous.zip > > > We are using log4net in our application. The real problem is the log messages > not properly logged in Asynchronous method. > We have two applications First one is Console Application and another one is > a .Net Web API. > We use Asynchronous logic in Console application. We are calling API service > in that Console application through Asynchronous method. Log4net implemented > in that API application also. > We have logged all the requests in that API service, but sometimes the log > was not properly logged or skipped in the log file. > Ex: The Console application calling 1000 times in that API service. But the > API service not writing all the requests, skipped 10 or 20 requests. > Any one please do the help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LOGCXX-511) C# - Log4Net Log not logging properly Asynchronous method
[ https://issues.apache.org/jira/browse/LOGCXX-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145723#comment-17145723 ] Matt Sicker commented on LOGCXX-511: Log4net is currently dormant. You can join the developer mailing list to perhaps aid in the efforts to get the project active and releasing again if you're interested. Otherwise, there isn't anywhere to report the bugs to. > C# - Log4Net Log not logging properly Asynchronous method > -- > > Key: LOGCXX-511 > URL: https://issues.apache.org/jira/browse/LOGCXX-511 > Project: Log4cxx > Issue Type: Bug >Reporter: Rajesh >Priority: Critical > Attachments: Log4NetAsynchronous.zip > > > We are using log4net in our application. The real problem is the log messages > not properly logged in Asynchronous method. > We have two applications First one is Console Application and another one is > a .Net Web API. > We use Asynchronous logic in Console application. We are calling API service > in that Console application through Asynchronous method. Log4net implemented > in that API application also. > We have logged all the requests in that API service, but sometimes the log > was not properly logged or skipped in the log file. > Ex: The Console application calling 1000 times in that API service. But the > API service not writing all the requests, skipped 10 or 20 requests. > Any one please do the help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LOGCXX-511) C# - Log4Net Log not logging properly Asynchronous method
[ https://issues.apache.org/jira/browse/LOGCXX-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145695#comment-17145695 ] Rajesh commented on LOGCXX-511: --- Thank you so much for quick response. I can't create the bug under the Log4Net. Kindly help on this. Or Kindly move this bug to under the Log4Net and share me the ref number. > C# - Log4Net Log not logging properly Asynchronous method > -- > > Key: LOGCXX-511 > URL: https://issues.apache.org/jira/browse/LOGCXX-511 > Project: Log4cxx > Issue Type: Bug >Reporter: Rajesh >Priority: Critical > Attachments: Log4NetAsynchronous.zip > > > We are using log4net in our application. The real problem is the log messages > not properly logged in Asynchronous method. > We have two applications First one is Console Application and another one is > a .Net Web API. > We use Asynchronous logic in Console application. We are calling API service > in that Console application through Asynchronous method. Log4net implemented > in that API application also. > We have logged all the requests in that API service, but sometimes the log > was not properly logged or skipped in the log file. > Ex: The Console application calling 1000 times in that API service. But the > API service not writing all the requests, skipped 10 or 20 requests. > Any one please do the help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (LOGCXX-511) C# - Log4Net Log not logging properly Asynchronous method
[ https://issues.apache.org/jira/browse/LOGCXX-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning closed LOGCXX-511. Resolution: Invalid You have created this issue in the wrong project, log4cxx instead of log4net, so I'm closing it. Feel free to create it in the correct project. OTOH, it might be a better idea to ask on the mailing list for support first. https://logging.apache.org/log4net/ https://issues.apache.org/jira/projects/LOG4NET > C# - Log4Net Log not logging properly Asynchronous method > -- > > Key: LOGCXX-511 > URL: https://issues.apache.org/jira/browse/LOGCXX-511 > Project: Log4cxx > Issue Type: Bug >Reporter: Rajesh >Priority: Critical > Attachments: Log4NetAsynchronous.zip > > > We are using log4net in our application. The real problem is the log messages > not properly logged in Asynchronous method. > We have two applications First one is Console Application and another one is > a .Net Web API. > We use Asynchronous logic in Console application. We are calling API service > in that Console application through Asynchronous method. Log4net implemented > in that API application also. > We have logged all the requests in that API service, but sometimes the log > was not properly logged or skipped in the log file. > Ex: The Console application calling 1000 times in that API service. But the > API service not writing all the requests, skipped 10 or 20 requests. > Any one please do the help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (LOGCXX-511) C# - Log4Net Log not logging properly Asynchronous method
[ https://issues.apache.org/jira/browse/LOGCXX-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh updated LOGCXX-511: -- Attachment: Log4NetAsynchronous.zip > C# - Log4Net Log not logging properly Asynchronous method > -- > > Key: LOGCXX-511 > URL: https://issues.apache.org/jira/browse/LOGCXX-511 > Project: Log4cxx > Issue Type: Bug >Reporter: Rajesh >Priority: Critical > Attachments: Log4NetAsynchronous.zip > > > We are using log4net in our application. The real problem is the log messages > not properly logged in Asynchronous method. > We have two applications First one is Console Application and another one is > a .Net Web API. > We use Asynchronous logic in Console application. We are calling API service > in that Console application through Asynchronous method. Log4net implemented > in that API application also. > We have logged all the requests in that API service, but sometimes the log > was not properly logged or skipped in the log file. > Ex: The Console application calling 1000 times in that API service. But the > API service not writing all the requests, skipped 10 or 20 requests. > Any one please do the help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LOGCXX-511) C# - Log4Net Log not logging properly Asynchronous method
Rajesh created LOGCXX-511: - Summary: C# - Log4Net Log not logging properly Asynchronous method Key: LOGCXX-511 URL: https://issues.apache.org/jira/browse/LOGCXX-511 Project: Log4cxx Issue Type: Bug Reporter: Rajesh We are using log4net in our application. The real problem is the log messages not properly logged in Asynchronous method. We have two applications First one is Console Application and another one is a .Net Web API. We use Asynchronous logic in Console application. We are calling API service in that Console application through Asynchronous method. Log4net implemented in that API application also. We have logged all the requests in that API service, but sometimes the log was not properly logged or skipped in the log file. Ex: The Console application calling 1000 times in that API service. But the API service not writing all the requests, skipped 10 or 20 requests. Any one please do the help. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [logging-log4cxx] ams-tschoening commented on pull request #28: reorder find_package to build SO correctly
ams-tschoening commented on pull request #28: URL: https://github.com/apache/logging-log4cxx/pull/28#issuecomment-649309850 As I'm still [unable](issues.apache.org/jira/browse/LOGCXX-510) to build using CMAKE myself, I'll simply continue to trust that those changes make sense. Thanks for fixing. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4cxx] ams-tschoening merged pull request #28: reorder find_package to build SO correctly
ams-tschoening merged pull request #28: URL: https://github.com/apache/logging-log4cxx/pull/28 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[ https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning reassigned LOGCXX-510: Assignee: Thorsten Schöning > 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, 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)
[jira] [Updated] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[ https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning updated LOGCXX-510: - Attachment: missing_log4cxx_rc.png > 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 >Priority: Major > Attachments: CMP00079.png, 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)
[jira] [Commented] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[
https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144712#comment-17144712
]
Thorsten Schöning commented on LOGCXX-510:
--
{quote}
CMake Error at main/cpp/CMakeLists.txt:6 (add_library):
Cannot find source file:
log4cxx.rc
Tried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm
.hpp .hxx .in .txx
C:\Users\tschoening\Documents\Svn\Src\Libs\trunk\C++\Logging\log4cxx\0.11.0-SNAPSHOT\src\src\main/cpp/CMakeLists.txt
6
{quote}
So where should that file com from by default? :-)
> 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
>Priority: Major
> Attachments: CMP00079.png, 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)
[jira] [Commented] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[
https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144708#comment-17144708
]
Thorsten Schöning commented on LOGCXX-510:
--
{quote}CMake Error at main/cpp/CMakeLists.txt:167 (set_target_properties):
set_target_properties called with incorrect number of arguments.
C:\Users\tschoening\Documents\Svn\Src\Libs\trunk\C++\Logging\log4cxx\0.11.0-SNAPSHOT\src\src\main/cpp/CMakeLists.txt
167
{quote}
https://cmake.org/cmake/help/latest/command/set_target_properties.html
Things work after applying quotes:
{quote} VERSION
"${log4cxx_VERSION_MAJOR}.${log4cxx_VERSION_MINOR}.${log4cxx_VERSION_PATCH}"
SOVERSION "${log4cxx_VERSION_MAJOR}"{quote}
But is that the correct approach or is the underlying problem missing values
for referenced variables?
> 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
>Priority: Major
> Attachments: CMP00079.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)
[jira] [Updated] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[ https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning updated LOGCXX-510: - Attachment: set_target_properties.png > 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 >Priority: Major > Attachments: CMP00079.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)
[jira] [Updated] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[ https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning updated LOGCXX-510: - Description: 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". (was: 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.) > 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 >Priority: Major > Attachments: CMP00079.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)
[jira] [Commented] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[
https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144702#comment-17144702
]
Thorsten Schöning commented on LOGCXX-510:
--
{quote}CMake Error at
C:\Users\tschoening\Documents\Svn\Src\Libs\trunk\C++\Logging\log4cxx\0.11.0-SNAPSHOT\src\src\CMakeLists.txt:7
(target_link_libraries):
Attempt to add link library "odbc32.lib" to target "log4cxx" which is not
built in this directory.
This is allowed only when policy CMP0079 is set to NEW.
C:\Users\tschoening\Documents\Svn\Src\Libs\trunk\C++\Logging\log4cxx\0.11.0-SNAPSHOT\src\src\CMakeLists.txt
7
{quote}
https://cmake.org/cmake/help/v3.13/command/cmake_policy.html#command:cmake_policy
This can easily be fixed by adding the following line for Windows only, but I'm
not sure if that is the correct approach.
bq. cmake_policy(SET CMP0079 NEW)
> 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
>Priority: Major
> Attachments: CMP00079.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)
[jira] [Updated] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
[ https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning updated LOGCXX-510: - Attachment: CMP00079.png > 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 >Priority: Major > Attachments: CMP00079.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. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LOGCXX-510) Build problems using CMAKE and Visual Studio 2019 Community
Thorsten Schöning created LOGCXX-510: Summary: 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 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. -- This message was sent by Atlassian Jira (v8.3.4#803005)
