View Single Post
  #1 (permalink)  
Old 12-02-2005
hgp hgp is offline
Registered User
 
 
Join Date: Dec 2005
Posts: 3
IceE1.0.0 on Visual C++ 2005

I have just tried to build IceE1.0.0 on Visual C++ 2005. It seems to work
(testsuite allTests.py returns a lot of oks). But I had to do some changes.
Maybe it is interesting for someone else what changes were
necessary.

1. In handle.h and proxyhandle.h the following blocks:
Code:
  #ifdef ___WIN32 // COMPILERBUG: Is VC++ or GNU C++ right here???
    template<>
    Handle(const Handle<T>& r)
  #else
    Handle(const Handle& r)  
  #endif
should be replaced by
Code:
    Handle(const Handle& r)
2. There is a conflict with the macro definitions __in and __out
from Microsoft in sal.h. A "quick an dirty" solution would be
the replacement of all __in and __out in the IceE code.
But most or even all of these statements could be found in
files dynamically generated from *.ice files.

I just started to work with the IceE-Code and to learn more about the
concepts of Ice. So the above means only: The build process was
succesfully and the libraries and executables passed the tests in allTests.py

For me it would be interesting to know:
  • Is there (it must) a better solution for the second point: Either replacing
    __in and __out before they are dynamically distributed (Where?) or
    avoid the including of sal.h?
  • Is a next release of IceE planned with support for Visual C++2005?

Thanks in advance for any advice
hgp
__________________
Hans-Georg Puls
Conergy AG [www.conergy.de]
Energy management

Last edited by hgp : 12-02-2005 at 10:16 AM.
Reply With Quote