1. Forum
  2. FidoNet
  3. TUB

  • Compiling ``slib'' w/Watcom

    From Serguei Trouchelle@2:550/4077.101 to All on Saturday, November 15, 2003 01:12:39
    Used:
    OpenWatcom 1.1
    UnxUtils (w/GNU Make version 3.78.1)
    Windows 2000 SP4

    First problem is unability to correctly execute sh ./configure, it has nested sh executions, based on #! method, which doesn't work under WinNT environments. So, I have to write own vars_windowsnt.mk
    Using ./configuration-test/make.sh with 3.78.1 cause some problems too, it can understand only 3.##

    By the way, using uname to determinte target platform is wrong. For example, Watcom can successfully compile OS/2 target under WinNT environment and vice versa. So I think original Lanius methods with $(COMP), $(MODE) etc was a good idea.

    Second problem is vars.mk file. It is very unportable. I think all variables, specific for GCC or UNIX have to be tranferred to vars_gcc.mk or stuff.

    For example, see line

    CPPFLAGS = -DUNIX $(EXTRA_CPPFLAGS) $(INCLUDES) $(EXTRA_INCLUDES)
    ^^^^^^

    I don't think it is a good idea to write this in main module :)

    Next. ./slib/Makefile

    It has hard-coded ``gcc'' lines. I think it is a very bad idea...

    Compiling smserial.c must be used only for OS/2 and UNIX, no need to compile it
    for DOS/D386/NT platforms.

    [to be continued...]

    Serguei Trouchelle
    --- timEd/386 1.10.y2k+
    * Origin: Send more complaints! (2:550/4077.101)
  • From Bo Simonsen@2:236/100 to Serguei Trouchelle on Sunday, November 16, 2003 00:17:39
    Hello Serguei!

    Nov 15 01:12 03, Serguei Trouchelle wrote to All:

    Used:
    OpenWatcom 1.1
    UnxUtils (w/GNU Make version 3.78.1)
    Windows 2000 SP4

    Nice to see interest from non-unix-guys ;)

    First problem is unability to correctly execute sh ./configure, it
    has nested sh executions, based on #! method, which doesn't work
    under WinNT environments.
    So, I have to write own vars_windowsnt.mk
    Using ./configuration-test/make.sh with 3.78.1 cause some problems
    too, it can understand only 3.##

    Good, maybe scott did leave some makefiles for NT?

    ...

    Next. ./slib/Makefile

    It has hard-coded ``gcc'' lines. I think it is a very bad idea...

    It might not be useable for NT, maybe a Makefile.NT might do it? ;)

    Compiling smserial.c must be used only for OS/2 and UNIX, no need to compile it for DOS/D386/NT platforms.

    Yes.

    Regards,
    Bo

    --- Msged/LNX 6.1.2 (Linux/2.4.18-bf2.4 (i586))
    * Origin: The Night Express, Roennede Dk (2:236/100)
  • From Serguei Trouchelle@2:550/4077.101 to Bo Simonsen on Sunday, November 16, 2003 20:21:11
    Using ./configuration-test/make.sh with 3.78.1 cause some problems
    too, it can understand only 3.##

    Good, maybe scott did leave some makefiles for NT?

    Yes, there's a lot of makefile.mk`s in original sources. I think it can be used
    instead and beside gnu makefiles.

    Next. ./slib/Makefile
    It has hard-coded ``gcc'' lines. I think it is a very bad idea...

    It might not be useable for NT, maybe a Makefile.NT might do it? ;)

    Agreed. Maybe there's sense to rename this files to Makefile.gcc, and use generic makefiles, something like this:

    -- cut --
    include makefile.$(COMPILER)
    -- cut --

    Compiling smserial.c must be used only for OS/2 and UNIX, no need to compile it for DOS/D386/NT platforms.

    Yes.

    Ok, I'll check out new version tomorrow at work (sadly, I compiled it here at home on machine with GSM-mobile connection to Inet, so only fido mail can be transferred well, CVS is incredibly slow :((( )

    Serguei Trouchelle
    --- timEd/386 1.10.y2k+
    * Origin: Send more complaints! (2:550/4077.101)