Part of the problem of building our own toolchain using Unicon is
bootstrapping; we need a working Unicon to build the toolchain to build
Unicon, which we said could be done via a minimalist build at first, which
in itself going to be a pain.
Now that I think of it, since we have been having stable Windows Unicon
binaries for the last few years, we can just say: install Unicon from
binaries, build the toolchain, uninstall the binaries, and then build
Unicon from sources using the newly built toolchain. We can also provide
different version of the toolchain binaries to be used with various Windows
versions. I know that you have been working on our own "make", so we might
get there someday! :-)
Cheers,
Jafar
On Mon, Feb 10, 2014 at 3:24 AM, Jeffery, Clint (jeffe...@uidaho.edu) <
jeffe...@uidaho.edu> wrote:
> Sergey,
>
>
> I am sure Jafar will have more intelligent things to say, but I will try
> to make a couple small observations. Windows XP is liable to give you
> troubles in building Unicon. It will probably run Unicon binaries just
> fine, but building Unicon from source is harder. Did the binaries not work
> for you for some reason, or do you just prefer to build from source?
>
>
> It may be possible to walk you through the configuration failure points
> manually, but I suspect that the current build/configure toolchain requires
> Windows 7 or newer. We are continually trying to figure out how to make the
> build rules on Windows as stable and portable as on UNIX, but Microsoft
> keeps changing things such that our configure+build toolchain keeps
> breaking. Old MSYS would not run properly on newer Windows. New MSYS might
> not run properly on old Windows; it is a mess.
>
>
> I want to rewrite all our build toolchain in Unicon so that we can
> control what's going on, but Jafar thinks I am crazy, and his word is law
> on the Windows Unicon builds, pretty much. :-)
>
>
> Cheers,
>
> Clint
>
>
> ------------------------------
> *From:* Sergey Logichev <slogic...@yandex.ru>
> *Sent:* Monday, February 10, 2014 1:05 AM
> *To:* unicon-group@lists.sourceforge.net
> *Subject:* [Unicon-group] build Unicon under Windows (XP SP3)
>
> Hello,
>
> As Clinton Jeffery asked I switched my question about Unicon build to
> here. Suppose, Jafar will answer me.
>
> I have downloaded Unicon's source code from SVN repositary and tried to
> build it on Windows with help of MinGW (configured as MinGW base+MSYS
> base). But I failed. Below is decription of my troubles:
>
> To run make command I created a tiny script "make-unicon.bat":
>
> *setlocal*
> *set path=c:\utils\mingw\bin;c:\utils\mingw\msys\1.0\bin;%path%*
> *make NT-Configure-GCC*
> *make Unicon*
> *endlocal*
>
> Below is its output:
>
> C:\work\unicon>set path=c:\work\unicon\bin;c:\utils\mingw\msys\1.0\bin;
>
> C:\work\unicon>make NT-Configure-GCC
> cd config/win32/gcc && sh config.sh
>
> Now remember to add unicon/bin to your path
> Then run make Unicon to build
>
> C:\work\unicon>make Unicon
> cd src/rtt && make
> make[1]: Entering directory `/c/work/unicon/src/rtt'
> makefile:1: ../../makedefs: No such file or directory
> make[1]: *** No rule to make target `../../makedefs'. Stop.
> make[1]: Leaving directory `/c/work/unicon/src/rtt'
> make: *** [Icon-icont] Error 2
>
> C:\work\unicon>
>
> OK, I have seen message *Now remember to add unicon/bin to your path* and
> slightly changed my make-unicon.bat
>
> *setlocal*
> *set path=c:\utils\mingw\bin;c:\utils\mingw\msys\1.0\bin;%path%*
> *make NT-Configure-GCC*
> *set path=c:\work\unicon\bin;%path%*
> *make Unicon*
> *endlocal*
>
> Below its output:
>
> C:\work\unicon>set path=c:\work\unicon\bin;c:\utils\mingw\msys\1.0\bin;
>
> C:\work\unicon>make NT-Configure-GCC
> 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!
>
> echo Run "make Unicon" to build
> Run make Unicon to build
>
> C:\work\unicon>set
> path=c:\work\unicon\bin;c:\utils\mingw\bin;c:\utils\mingw\msys\1.0\bin;
>
> C:\work\unicon>make Unicon
> cd src/rtt && make
> make[1]: Entering directory `/c/work/unicon/src/rtt'
> gcc -m32 -O2 -D_X86_ -I../gdbm -I../libtp -DRttx -DRTT
> -DTokDotH=\"../rtt/ltoken.h\" -DNTConsole -c -o rttparse.o rttparse
> c
> In file included from ../preproc/../h/gsupport.h:16:0,
> from ../preproc/preproc.h:1,
> from rtt1.h:1,
> from rttgram.y:7:
> ../preproc/../h/../h/sys.h:211:21: fatal error: pthread.h: No such file or
> directory
> #include <pthread.h>
> ^
> compilation terminated.
> make[1]: *** [rttparse.o] Error 1
> make[1]: Leaving directory `/c/work/unicon/src/rtt'
> make: *** [Icon-icont] Error 2
>
> As I understood file */mingw/include/pthread.h* is missed. Why? And where
> I will get it?
>
> Best regards,
> Sergey Logichev
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> Unicon-group mailing list
> Unicon-group@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
>
------------------------------------------------------------------------------
Android™ apps run on BlackBerry®10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
