[omniORB] win64 question

Matthew Bettencourt matt at mail.bettencourt.info
Mon Oct 23 12:44:25 BST 2006


That fixed the first problem. I am now having problems with omniidl in a 
different way.  I had to set pythonpath
PYTHONPATH=C:\Python25;C:\Python25\Lib;C:\Python25\DLLs
and that let omniidl run w/o getting an import os error.

make[2]: Entering directory `/cygdrive/c/Documents and 
Settings/hpctest/Desktop/
MCEL Complete/omniORB-4.0.7/src/lib/omniORB'
../../../bin/x86_win32/oidlwrapper.exe -gnuwin32 -T -bcxx -Wbh=.hh 
-Wbs=SK.cc -W ba -p../../../src/lib/omniORB -Wbdebug -v -ComniORB4 
../../../idl/Naming.idl
PYTHONPATH=C:\Python25;C:\Python25\Lib;C:\Python25\DLLs;
c:\Documents and Settings\hpctest\Desktop\MCEL 
Complete\omniORB-4.0.7\bin\x86_wi n32\omniidl -T -bcxx -Wbh=.hh 
-Wbs=SK.cc -Wba -p..\..\..\src\lib\omniORB -Wbdebu g -v -ComniORB4 
..\..\..\idl\Naming.idl
omniidl: Warning: No back-ends specified; checking IDL for validity
omniidl: 'and' does not exist
make[2]: *** [omniORB4/Naming.hh] Error 1
make[2]: Leaving directory `/cygdrive/c/Documents and 
Settings/hpctest/Desktop/M CEL Complete/omniORB-4.0.7/src/lib/omniORB'
make[1]: *** [export] Error 1
make[1]: Leaving directory `/cygdrive/c/Documents and 
Settings/hpctest/Desktop/MCEL Complete/omniORB-4.0.7/src/lib'
make: *** [export] Error 1

I searched the lists and didn't see anything refering to this.
Thanks
Matt

Peter Klotz wrote:
> Matthew Bettencourt wrote:
>> Oddity and more info
>> When the binary is in the src/tool/omniidl/cxx dir it runs.  I found 
>> out about depends.exe under windows and it says it is getting the 
>> following dll.
>> c:\windows\winsxs\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_3fea50ad\MSVCR80.DLL 
>>
>> however, if i copy it to the bin dir, it doesn't run and depends 
>> doesn't find the msvcr80.dll  (I have taken all out of my path BTW).  
>> If i copy the one listed above into the bin/x86_win32 dir, it dies w/ 
>> the invalid attempt to load the dll file.
>>
>> I have more info and more confusion at this point, ideas?
> 
> You need the compiler generated manifest files in order to compile 
> omniORB 4.0.7 with VS2005.
> 
> See here for a short explanation:
> 
> http://www.omniorb-support.com/pipermail/omniorb-list/2006-April/027643.html 
> 
> 
> Best regards, Peter.
> 




More information about the omniORB-list mailing list