Re: building omniORBpy
Duncan Grisby via omniORB-list <[email protected]> Sun, 21 Apr 2019 23:35:44 +0100
| Newsgroups | gmane.comp.corba.omniorb.user |
|---|---|
| Message-ID | <[email protected]> |
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... [...] > make[1]: Entering directory > '/cygdrive/d/Buildslocal/thirdparty/trader/omniORB/src/lib/omniORBpy' > GNUmakefile:8: mk/afterauto.mk: No such file or directory > make[1]: *** No rule to make target 'mk/afterauto.mk'. Stop. Something has become confused. afterauto.mk is only used by the autoconf build, but here you are meant to not be using it. When you unpack omniORBpy, you should have a file in each directory called GNUmakefile. The top-level omniORBpy directory's one contains this: TOP=../../.. CURRENT=src/lib/omniORBpy include $(TOP)/config/config.mk 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++. Duncan. -- -- Duncan Grisby -- -- [email protected] -- -- http://www.grisby.org -- _______________________________________________ omniORB-list mailing list [email protected] http://www.omniorb-support.com/mailman/listinfo/omniorb-list