Thanks for the update Sergey. Up to my knowledge, you are probably the first to try building Unicon from sources on Windows 8.1. It is good to hear that it worked.If you want threads in Unicon on those machines I can send you the pthread library files that I use at my end. Just let me know. I'm still puzzled about pthread absence from MinGW. It's been available there for a couple of years at least. I don't know if you are using an older version.
Cheers,
JafarOn Feb 11, 2014 11:31 PM, "Sergey Logichev" <slogic...@yandex.ru> wrote:Jafar,for Windows 8.1 build steps and modifications were the same as for XP and succeded too. Suppose, that adding lpthread to Windows build is some tricky process. At least this code is missed in Unicon source.Sergey11.02.2014, 19:03, "Jafar Al-Gharaibeh" <to.ja...@gmail.com>:Sergey,Great to see successful attempts to build Unicon from sources on Windows! Excellent!libpthread-2.dll is required because the binaries are built with concurrency support. The dll file should be present somewhere on your path for Unicon programs to work as you found out.--JafarOn Tue, Feb 11, 2014 at 7:49 AM, Sergey Logichev <slogic...@yandex.ru> wrote:Hello Jafar,When I commented at unicon/config/win32/gcc/define32.h the following lines:/*#define HAVE_LIBPTHREAD 1#define Concurrent 1*/and changed definitions at unicon/config/win32/gcc/makedefs32.topOPTLIBS= --staticNTOPTLIBS=build was successful for XP (without pthreads). Binary distribution of Unicon for win32 includes library libpthread-2.dll without which programs builded as unicon -B won't work. So, now I will dig farther and explore all diamonds of Unicon!Sergey10.02.2014, 23:12, "Jafar Al-Gharaibeh" <to.ja...@gmail.com>:Sergey,pthreads library (including pthread.h) has been available with the MinGW for the last couple of years at least? Are you using an older MinGW?If you don't want concurrent threads you can simply comment out:#define Concurrent 1 // in unicon/config/win32/gcc/define.hand also comment out -lpthread from makedefs32.top in the same directory.If you want threads and can't find the pthread library in mingw I will ship you the necessary files from my machine.--JafarOn Mon, Feb 10, 2014 at 3:39 AM, Sergey Logichev <slogic...@yandex.ru> wrote:Hi Clint!Yes, I know what XP is not a good platform. At home I have Windows 8.1 but now I am not at home.As I found after investigations in the jungle of Unicon sources *.h files pthread.h is called from unicon\src\h\sys.h (line #212):#ifdef HAVE_LIBPTHREAD#if !UNIX || !defined(Audio)#include <pthread.h>#endif /* PthreadCoswitch & ! Audio */#include <semaphore.h>#endif /* HAVE_LIBPTHREAD */At the evening I will try to repeat at Windows 8.1, it's interesting what will be the results?Of course, I have installed Unicon without any troubles from binary setup. But it was interested for me to make it from sources. It's for hackers, sometimes I want to be such person :-)))Problem of compatibility is very complex and I agree with Jafar that it's a very unrealistic to automatically solve it. Things are changed all the time! And as practice shows, it will be even speeded up in the future. I would say that modern programming is an ordered chaos. Such a lot of different codes linked in an inconceivable mess. How it works after all! Nowbody knows!Thank you!Sergey10.02.2014, 13:24, "Jeffery, Clint (jeffe...@uidaho.edu)" <jeffe...@uidaho.edu>: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":setlocalset path=c:\utils\mingw\bin;c:\utils\mingw\msys\1.0\bin;%path%make NT-Configure-GCCmake UniconendlocalBelow 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-GCCcd config/win32/gcc && sh config.shNow remember to add unicon/bin to your pathThen run make Unicon to buildC:\work\unicon>make Uniconcd src/rtt && makemake[1]: Entering directory `/c/work/unicon/src/rtt'makefile:1: ../../makedefs: No such file or directorymake[1]: *** No rule to make target `../../makedefs'. Stop.make[1]: Leaving directory `/c/work/unicon/src/rtt'make: *** [Icon-icont] Error 2C:\work\unicon>OK, I have seen message Now remember to add unicon/bin to your path and slightly changed my make-unicon.batsetlocalset path=c:\utils\mingw\bin;c:\utils\mingw\msys\1.0\bin;%path%make NT-Configure-GCCset path=c:\work\unicon\bin;%path%make UniconendlocalBelow its output:C:\work\unicon>set path=c:\work\unicon\bin;c:\utils\mingw\msys\1.0\bin;C:\work\unicon>make NT-Configure-GCCcd config/win32/gcc && sh config.shcd config/win32/gcc && sh nt-config.shConfiguring for console build...cd config/win32/gcc && sh config32.shRunning 32-bit build configuration...Done!echo Run "make Unicon" to buildRun make Unicon to buildC:\work\unicon>set path=c:\work\unicon\bin;c:\utils\mingw\bin;c:\utils\mingw\msys\1.0\bin;C:\work\unicon>make Uniconcd src/rtt && makemake[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 rttparsecIn 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 1make[1]: Leaving directory `/c/work/unicon/src/rtt'make: *** [Icon-icont] Error 2As 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