Re: building omniORBpy

Hi,

Am 22.04.19 um 00:35 schrieb Duncan Grisby:
> On Thu, 2019-04-18 at 17:26 +0200, Michael Teske via omniORB-list
> wrote:
> 
>> I tried to build omniORBpy 4.2.2 on windows. Following the
>> instructions in the readme
> 
> 4.2.3 is the latest release...

Yeah I know, but the differences are not that big, this ist for testing 
right now...

...
> There is also a GNUmakefile.in that is transformed into a replacement
> GNUmakefile by the configure script. It looks like this:
> 
> TOP=.
> CURRENT=.
> BASE_OMNI_TREE=@top_srcdir@
> VPATH=@srcdir@
> 
> include $(TOP)/mk/beforeauto.mk
> include @srcdir@/dir.mk
> include $(TOP)/mk/afterauto.mk
> 
> 
> You can see that the .in version refers to beforeauto.mk and
> afterauto.mk.
> 
> Did you perhaps run the configure script in cygwin?  You should not do
> that on Windows, because it will try to configure it to build with
> cygwin, not with Visual C++.

No, I did something similar stupid, the directory is nfs/samba mounted 
and I built it on linux before. I did do a make clean before building on 
windows, but obviously this isn't enough. Later, it did not occur to me 
that the original GNUmakefile could differ from the one genereated from 
GNUmakefile.in. Thanks and sorry for the confusion,
   Michael


> Duncan.
> 


_______________________________________________
omniORB-list mailing list
[email protected]
http://www.omniorb-support.com/mailman/listinfo/omniorb-list