Archived
This forum has been archived. Please start a new discussion on GitHub.
IceE1.0.0 on Visual C++ 2005
in Help Center
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:
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:
Thanks in advance for any advice
hgp
(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:
#ifdef ___WIN32 // COMPILERBUG: Is VC++ or GNU C++ right here??? template<> Handle(const Handle<T>& r) #else Handle(const Handle& r) #endifshould be replaced by
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
0
Comments
-
Hi,
Please see [thread=1697]this thread[/thread] regarding our support policy on the forums.
Thanks,
Brent0 -
Hi,
sorry, haven't known that. Now my posting includes a signature.
Georg0 -
Hi Hans-George,
Yes, the next version of Ice-E will support Visual Studio 2005. The current Ice-E was released a few months ago and requires a few changes.
If you're just experimenting with Ice and Visual Studio 2005, I'd recommend to use Ice 3.0 and not Ice-E, since we support Ice 3.0 built with VS2005: see this post.
Best regards,
Bernard0