[
https://issues.apache.org/jira/browse/LOGCXX-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009461#comment-17009461
]
Thorsten Schöning commented on LOGCXX-494:
------------------------------------------
{quote}Is anybody available to include this in the log4cxx repository?{quote}
As can be read in the PR, it's unclear if to include that build additionally at
all. The project already contains multiple different build systems to maintain,
Autotools, Maven, Ant, which made a lot of trouble on the various different
platforms in the past and adding another one to maintain doesn't sound like a
good idea. Additionally, the project can't drop all other build systems as well
easily, because e.g. Maven is necessary for generating the homepage, Ant to
generate project files for various IDEs, docs need to be rewritten heavily,
users might depend especially on Autotools being available etc.
> Provide a windows build environment for the project
> ---------------------------------------------------
>
> Key: LOGCXX-494
> URL: https://issues.apache.org/jira/browse/LOGCXX-494
> Project: Log4cxx
> Issue Type: Improvement
> Components: Build
> Affects Versions: 0.10.0
> Environment: Windows, any flavor
> Reporter: James E. King III
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In version 0.10.0 all windows project files were removed from the repository.
> The apr project which log4cxx depends on provides both a static project file
> (which I would discourage) as well as a cmake build environment for windows
> (which can generate a solution for any version of Visual Studio).
> The improvement request is to provide a cmake build environment for log4cxx.
> I believe it would be acceptable to tie this to the apr-2 project, given that
> apr-util folded into apr about 5 years ago... when will apr-2 be released?
> The web site documentation for building on Visual Studio is ancient (10+
> years old):
> https://logging.apache.org/log4cxx/latest_stable/building/vstudio.html
> This should also be updated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
