You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by "Thorsten Schöning (JIRA)" <lo...@logging.apache.org> on 2014/02/10 16:33:19 UTC

[jira] [Resolved] (LOGCXX-147) Windows CE support

     [ https://issues.apache.org/jira/browse/LOGCXX-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thorsten Schöning resolved LOGCXX-147.
--------------------------------------

    Resolution: Won't Fix

Windows CE can be considered dead and is not worth any effort anymore.

> Windows CE support
> ------------------
>
>                 Key: LOGCXX-147
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-147
>             Project: Log4cxx
>          Issue Type: Improvement
>    Affects Versions: 0.10.0
>            Reporter: Curt Arnold
>            Assignee: Curt Arnold
>            Priority: Minor
>
> Several changes are needed to log4cxx to enable compilation using Visual Studio 2005 targeting Windows CE devices.  The issues that have been encountered so far:
> 1. Preprocessor does not properly expand LOG4CXX_EXPORT
> This will manifest itself with error C2470 with a message like 'Locale' : looks like a function definition, but there is no parameter list; skipping apparent body.  For some reason, explicitly including log4cxx/logstring.h in the .cpp file will cause the compilation error to go away.
> 2. Event log not supportined in Windows CE so NTEventLogAppender needs to be suppressed
> 3. std::locale is not supported, so some of the localization tests need to be suppressed
> 4. ::getenv not supported, so migrated to apr_env_get.
> 5. Only wmain is supported as program entry point.
> 6. Command line builds are difficult or impossible.  Currently, building log4cxx has required manually constructing VC 2005 projects.
> Most of the changes necessary to get log4cxx to run under WinCE are changes to APR and APR-util which will be filed as bugs against them and may be patched into APR in later commits.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)