Rusmin,
please forget 2.3.8 and give a try to 2.3.12 release. It is tested with
VC++ 2003 and should also work for you. If you have any issue with it,
please post description here.
Cheers,
Karel
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
---
Need experienced, fast, reliable technical MICO support?
---> http://www.objectsecurity.com/mico_commsup_referral.html <---
---
On Tue, 21 Feb 2006, Rusmin Susanto wrote:
Hi. I build Mico (V 2.3.8) using Visual C++ .NET 2003. I always get Mico
Crash if I do a certain thing. I suspect that it has something to do
with
Microsoft's bug. In the README-WIN32, I found this:
Sometimes a MICO application will crash inside mico.dll. As far as we
can tell this is
related to a bug in the Microsoft Linker when dealing with global
constructors. If this happens to you, try to link typecode.obj and
util.obj statically with your application (a copy of these object files
can be found in win32-bin\lib). This usually resolved our
problems... sigh...
Normally no need to link any additional files. The util.obj is only
needed when passing std::map objects between
application and a dll(necessary in idl.exe). The problem with
typecode.obj should be fixed too(knock on wood).
I think the above suggestion could be the solution.
My question is:
- What does this ("try to link typecode.obj and util.obj statically with
your application") mean?
Does it mean that in the additional dependency I should specify
typecode.obj and util.obj instead of mico*.lib?
Could someone give me more specific / clearer hints please?
Thanks
Rusmin
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel
