ASF subversion and git services commented on PROTON-596:

Commit 1600924 from c...@apache.org in branch 'proton/trunk'
[ https://svn.apache.org/r1600924 ]

PROTON-596: Add cmake configure_file to customize config.bat for windows builds.

1. Cmake on windows produces all four cmake configurations (debug, 
relwithdebinfo, ...) on one pass. Producing N config.bat files, one for each 
configuration, seems like overkill. The build produces just one config.bat that 
that is set up for RelWithDebInfo.

2. The prototype bash file config.sh does several conditional tests for sensing 
the build and changing the environment accordingly. The windows version 
flattens these tests out and forces the settings every time. It's easier to 
understand this way and requires a lot less testing for proof. Only the Python 
binding has been exercised; Ruby, Perl, and PHP not so much.

3. A typical 32-bit VS2010 run:
  > mkdir build
  > mkdir install
  > cd build
  > call "%VS100COMNTOOLS%..\..\VC\vcvarsall.bat" x86
  > cmake -G "Visual Studio 10" -DCMAKE_INSTALL_PREFIX=../install ..
  > devenv proton.sln /build "RelWithDebInfo|Win32" /project INSTALL
  > devenv proton.sln /build "Debug|Win32" /project INSTALL
  > call config.bat
  > ctest -VV

There is one python test that fails regularly (out of 282).

> There is no equivalent to 'config.sh' for windows
> -------------------------------------------------
>                 Key: PROTON-596
>                 URL: https://issues.apache.org/jira/browse/PROTON-596
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.7
>         Environment: Proton on windows
>            Reporter: Chuck Rolke
> ctest fails to find compiled C tests. Some environment settings are needed in 
> addition to those supplied by cmake/ctest.
> Linux users have the luxury of config.sh to steer their environment correctly 
> for tests built in proton/build. Windows users need the same.

This message was sent by Atlassian JIRA

Reply via email to