On sexta-feira, 8 de julho de 2016 15:02:58 PDT ???(Uze Choi) wrote:
> Hi Trevor,
> 
> More than half cases, windows build Still error happen in master also.

Master contains Windows code. Therefore, master should be built on Windows.

> 02:11:04
> c:\j\workspace\verify-iotivity-windows-vs2015\resource\csdk\connectivity\sr
> c\ip_adapter\windows\caipnwmonitor.c(21): fatal error C1083: Cannot open
> include file: 'caipinterface.h': No such file or directory
> 
> It will be better to wait it until stable stage, please apply windows build
> into windows-port branch only. By merging master into windows-port, windows
> build can be verified.

There's no windows-port branch anymore. The porting work is done and the 
branch is closed. It can be deleted.

> Furthermore, lots of pending patches on the development branch yet, let do
> not mix the windows related update into current development activity.
> Excluding windows build looks very rationale until settle-down.

All the feature branches need to merge the master branch frequently and 
pending patches need to rebase if they encounter a build error that has been 
fixed. That is not a new thing, it has always been the case. It isn't a 
frequent thing, but it happens.

It's happening now.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Reply via email to