On Fri, 31 Oct 2008, David Arturo Macias Corona wrote: Hi David,
> You are correct, at least in OS/2-gcc335 it does not raise these warnings > It should be cleaned in OS/2 in particular or all platforms ? I still do > not know if these warnings happen in Linux/gcc43x It also rises these type of warnings - it depends on GCC version. But in this case the code is local to OS2 and only on this platform warnings can appear and it's the reason why we cannot easy catch and clean them. Cross build environment can resolve such problems. > Yes I am "interested in creating OpenWatcom OS2 Harbour port" > I have heard about OpenWatcom on OS/2 long time ago and collected some > packages, trying to test cross-platform builds for Harbour > In middle August 2008 I installed (for Harbour 1.0): > Open Watcom C/C++ Version 1.7 > and surprisely is a great package: > IDE, SourceBrowse, Profiler, Debugger, ... > in 164 Mbytes directory > But I do not know how to use it :-) copy config/w32/owatcom.cf to config/os2/owatcom.cf and update it for OS2 builds. At least these lines should be changed: [19]: CPPFLAGS = -w2 -d1 -zq -bt=NT [56]: echo @%watcom%/binnt/wlink.lnk >> __link__.tmp [57]: echo LIB kernel32.lib, user32.lib, wsock32.lib, winspool.lib, oleaut32.lib, uuid.lib, comctl32.lib, mapi32.lib >> __link__.tmp [62]: LDFLAGS = debug all OP osn=NT OP stack=65536 OP CASEEXACT for OS2 builds. You will have to update -bt=NT and osn=NT, directory with wlink.lnk (or maybe you can remove this line) and library list. I suggest to start with removing lines 56 and 57 and then try to add libraries if linker will report unresolved dependencies. But 1-st Harbour will have to be updated for clean compilation. I expect that you will see some errors. Please report them. To compile Harbour set: rem update this path to real OpenWatcom location set WATCOM=C:\LNG\WATCOM rem In OS2 probably BINW and BINNT have different name, please check set PATH=%WATCOM%\BINW;%PATH% set INCLUDE=%WATCOM%\H;%WATCOM%\H\OS2 set HB_ARCHITECTURE=OS2 set HB_COMPILER=owatcom and then use GNU make to build harbour just like for GCC builds. > - Just remain warnings of type "differ in signedness" > Below are results included I'll pacify them, please test when I'll commit. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
