On Thu, Nov 5, 2015 at 3:09 PM, Don Ward <[email protected]> wrote: > > Well, If you “grep -R "--include=[Mm]akefile" "\bmake\b" * | grep -v “?” > you will see a number of places where “make” appears to be hard coded. >
I will fix those. > > It is possible to use a different name for make *if you also have a > make.exe in your path* (I’ve just tried it) but, even in a directory that > has previously worked, If I remove make.exe from my path, leaving just > mingw32-make.exe then it fails like this > > $ mingw32-make wUnicon32 > CPPFLAGS='-IC:/Users/Don/UniconBuild/unicon-3976/src/gdbm > -IC:/Users/Don/UniconBuild/unicon-3976/src/libtp' CXX='gcc' > > ============================================= > Running configuration and setup scripts NT 32 > ============================================= > > cd config/win32/gcc && sh config.sh > > cd config/win32/gcc && sh nt-config.sh > > Configuring for console build... > > cd config/win32/gcc && sh config32.sh > > Running 32-bit build configuration... > > > Done! > > > ========================= > Building NT Unicon 32-bit > ========================= > > make Unicon > makefile:24: recipe for target 'wUnicon32' failed > process_begin: CreateProcess(NULL, make Unicon, ...) failed. > make (e=2): The system cannot find the file specified. > mingw32-make: *** [wUnicon32] Error 2 > > > > The reason for the CPPFLAGS= and the CXX= are that I copied my previously > successful build command (and I couldn’t get it to build without CPPFLAGS > and CXX).. > > Just in case something weird was happening with a combination of different > executions in the same build directory I tried it, starting from scratch > with a new copy of an unconfigured system: the build fails for the same > reason. Here is a console log. > > Don@Win10-VM MSYS /c/Users/Don/UniconBuild/unicon-3976-test > $ mingw32-make WUnicon > Reloading the Makefile from config/win32/gcc/makefile.top > cp config/win32/gcc/makefile.top Makefile > Done. > > Ready to build Windows Unicon > Make sure the Unicon bin directory is in your path before continuing, then > run: > > - "make WUnicon32" for a 32-bit build, or > - "make WUnicon64" for a 64-bit build - requires MinGW64. > > > Don@Win10-VM MSYS /c/Users/Don/UniconBuild/unicon-3976-test > $ mingw32-make WUnicon32 > > ============================================= > Running configuration and setup scripts NT 32 > ============================================= > > cd config/win32/gcc && sh config.sh > > cd config/win32/gcc && sh nt-config.sh > > Configuring for console build... > > cd config/win32/gcc && sh config32.sh > > Running 32-bit build configuration... > > > Done! > > > ========================= > Building NT Unicon 32-bit > ========================= > > make Unicon > makefile:24: recipe for target 'WUnicon32' failed > process_begin: CreateProcess(NULL, make Unicon, ...) failed. > make (e=2): The system cannot find the file specified. > mingw32-make: *** [WUnicon32] Error 2 > > Don@Win10-VM MSYS /c/Users/Don/UniconBuild/unicon-3976-test > > > The only way I’ve got it to work is if I have “make.exe’ available > somewhere in my PATH. I also had to have the CPPFLAGS and CXX arguments. Do > you build successfully without them? > For me, without CXX I get g++ (which doesn’t go very well) and without the > CPPFLAGS it can’t find ndbm.h (when compiling rttparse.c) and tp.h (when > compiling libtp). > Usually no, I don't need this, but the last time a tried to build on Windows a couple of weeks ago I had similar issues. There has been a stream of commits to svn lately that shuffled few things around. We will fix that. Part of the "make" problem -aside from the hardcoded calls to make- is that different "make" programs behave differently. Add differences between different Windows releases/updates and you get a very unpredictable behavior. Last year, Clint took on a quest to build our own make (lives in unicon/uni/umake.icn) to avoid some of this mess. Not sure if we are going to switch to that at some point if it is mature enough. I will rebuild from scratch on Windows in the next couple of days and fix these new issues. I will let you know when I get that done. > > Cheers > > Don > > PS. I think that the “not for the faint of heart” comment in FAQ 16 in > http://unicon.org/faq.html is a bit harsh these days. It wasn’t *that* > difficult to get it work. > When I first start using Unicon building on Windows was Unicon's "Everest Challenge". I think the comment was not updated from those days. The build is a lot easier now. If there are issues you can blame me! I have been maintaining the Windows builds for the last few years. ;) Cheers, Jafar
------------------------------------------------------------------------------
_______________________________________________ Unicon-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unicon-group
