[omniORB] omniorb and cygwin 1.7

[Arne Pajunen]

Hi,

I haven't found any clean fix, but I managed to compile omniORB with 
cygwin 1.7 by manually adding some registry keys to the locations 
clwrapper & friends expect:

DISCLAIMER: don't go modifying the registry unless you know what you're 
doing, this is at best an ugly workaround :)

[HKEY_CURRENT_USER\Software\Wow6432Node\Cygnus Solutions\Cygwin\mounts v2]
@="/"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygnus Solutions\Cygwin\mounts v2]
@="C:/cygwin"
"/usr/bin"="C:/cygwin/bin"
"/usr/lib"="C:/cygwin/lib"

The first one (in HKEY_CURRENT_USER) needs to correspond to where you've 
set your cygdrive prefix. Mine is "/" but the default is "/cygdrive". 
The second branch is for the install location (mine's at the default 
location).

Best regards,

Arne Pajunen

On 2/1/2010 3:04 PM, Christian Hoffmann wrote:
> Hi all,
>
> The latest release of cygwin (1.7) doesn't create registry entries any more
> for mapping drives to mountpoints. The omniORB tools to compile on win32
> (e.g. src/tool/win32/clwrapper.c) are using those entries. Another issue is
> that cygwin 1.7 doesn't provide gnu make 3.80 anymore and later versions
> have problems compiling omniorbpy. Has anyone found/created a
> solution/patch to this isses?
>
> Kind regards,
>
> Chris
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list