Re: [Unicon-group] Spaces in the path to make.exe break the build process on Windows

[Don W. <do...@ca...>]

> On 5 Nov 2015, at 21:57, Jafar Al-Gharaibeh <to....@gm...> wrote:
> 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

I was building rev 3976 (so I could compare what I had built with my toolchain with the “official release” and hence validate my local build environment).  I don’t see how recent svn commits could have affected rev 3976, but I still need CPPFLAGS and CXX to build it.

> 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.

If you do switch you’ll have the usual bootstrapping problem when starting from scratch with a new build: you need uMake to be working in order to build itself.

> 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.

OK (and thanks for all your efforts).  BTW, when I tried building rev 4186, I got a stack of errors to do with rusage (which looks to have been implemented circa rev 4052). Is this also a known problem for Windows builds?

Don