[omniORB] Can't build omniORB 4.2.2 with Visual Studio 2017

Marcin Cieslak saper at saper.info
Tue Mar 13 09:32:13 GMT 2018


On Tue, 13 Mar 2018, Dalecki, Janusz via omniORB-list wrote:

> Hi,
> I am having trouble to generate OmniORB dlls and libs.
> I am running it on Windows 7 Dell Laptop platform 64bit version with Visual Studio 2017 community edition.
> I have downloaded omniORB 4.2.2, Cygwin64 and Python 36_32
> After following instructions from README.win32.txt:
> 
> *        setting platform = x86_win32_vs_15 in config.mk,
> 
> *        PYTHON = /cygdrive/c/Python/Python36-32 in x86_win32_vs_15.mk
> 
> *        set path=%path%;c:\cygwin64\bin;C:\Python\Python36-32"
> ... this is an output from the Visual Studio 2017 console after following above steps. I am not sure whether the final error "error C2006: '#include': expected a filename, found 'identifier'" is caused by an earlier "Command not found" error or they are independent. I can't find anything useful on Internet:
> 
> make[3]: /cygdrive/c/Python/Python36-32: Command not found

You might want to check the following advice posted earlier to this mailing list:

http://www.omniorb-support.com/pipermail/omniorb-list/2018-January/031961.html

Marcin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3663 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20180313/4db2ea83/attachment.p7s>


More information about the omniORB-list mailing list