Re: [Freedos-devel] compiling dflat+
Hi, 2008/9/7 Michael Reichenbach <[EMAIL PROTECTED]>: > Aitor Santamaría schrieb: >> Martin, >> >> Of course I tried under Open Watcom. >> >> Try these lines: >> >> wcc -ml -i=c:\\WATCOM\h -i=c:\freedos\source\INC hworld.c >> wlink @owlink.wcl >> >> where owlink.wcl is: >> === >> system dos >> option map >> option stack=8192 >> name hworld.exe >> file hworld >> libpath c:\freedos\source\lib >> libpath c:\watcom\lib286 >> libpath c:\watcom\lib286\dos >> library dflatplo.lib >> library dtool2lo.lib >> === >> >> And it works for me. > > Works also for me. :) Good! > Exchanging wcc with wpp and hworld.c with hworld.cpp doesn't work. This > is normal? And this can not be fixed easily? There's nothing to fix: the code is C, not C++. Thus you have to use wcc, and not wpp. Aitor - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] compiling dflat+
Aitor Santamaría schrieb: > Martin, > > Of course I tried under Open Watcom. > > Try these lines: > > wcc -ml -i=c:\\WATCOM\h -i=c:\freedos\source\INC hworld.c > wlink @owlink.wcl > > where owlink.wcl is: > === > system dos > option map > option stack=8192 > name hworld.exe > file hworld > libpath c:\freedos\source\lib > libpath c:\watcom\lib286 > libpath c:\watcom\lib286\dos > library dflatplo.lib > library dtool2lo.lib > === > > And it works for me. Works also for me. :) Exchanging wcc with wpp and hworld.c with hworld.cpp doesn't work. This is normal? And this can not be fixed easily? -mr - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] compiling dflat+
Hello all,
I am bringing the conversation to private, as it seems mostly a OWC
configuration problem. If anyone is interested in following, let us
know.
Aitor
2008/9/6 Michael Reichenbach <[EMAIL PROTECTED]>:
> Michael Reichenbach schrieb:
>> Aitor Santamaría schrieb:
>>> No, that I didn't bother to adjust the final makefile to OW.
>>
>> And did you test to build the example with dflat+ 1.0 and OW 1.6 yourself?
>>
>> > OpenWatcom comes with the wcl utility (compile and link). Why don't
>>> you try that instead of WMAKE?
>>
>> Don't know but I will try.
>>
>>> I guess it'll be easier, and you can
>>> create HWORLD.EXE in a single line.
>>
>> Yes.
>>
>>> Check out the wcl options, you just have to tell it the source files,
>>> the headers and the libraries, and it should easily create the EXE
>>> file.
>>
>> I have the OpenWatcom Tools.pdf
>>
>> m{f,s,m,c,l,h} memory model — mf=flat ms=small mm=medium mc=compact ml=large
>> mh=huge (default is "ms" for 16-bit and Netware, "mf" for 32-bit)
>>
>> On the command line, you can list source
>> file names as well as object file names. Source files are either
>> compiled or assembled based
>> on file extension; object files and libraries are simply included in the
>> link phase. Options can
>> be passed on to both the compiler and linker.
>>
>> i= add directory to list of include directories
>>
>>> Then you can put it inside a BAT
>>> files.
>>
>> This is what I currently have:
>>
>> wcl dtest.cpp C:\devel\dflatP\SOURCE\LIB\DTOOL0LB.LIB
>> C:\devel\dflatP\SOURCE\LIB\DFLATPLO.LIB /i=C:\devel\dflatP\SOURCE\INC
>> /i=C:\devel\dflatP\SOURCE\LIB /ml
>>
>> I also tested to put everything from INC and LIB folder to one folder
>> (C:\devel\dtest) plus including dtest.cpp. (dtest.cpp is the example
>> from DFP100.HTM) And then:
>>
>> wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
>>
>> Error message:
>> wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
>> Open Watcom C/C++16 Compile and Link Utility Version 1.6
>> Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved.
>> Source code is available under the Sybase Open Watcom Public License.
>> See http://www.openwatcom.org/ for details.
>>wpp DTEST.CPP
>> Open Watcom C++16 Optimizing Compiler Version 1.6
>> Portions Copyright (c) 1989-2002 Sybase, Inc. All Rights Reserved.
>> Source code is available under the Sybase Open Watcom Public License.
>> See http://www.openwatcom.org/ for details.
>> dfpcore.h(183): Warning! W146: col(2) unexpected storage class specifier
>> found
>> dfpcore.h(183): Note! N393: col(2) included from dflatp.h(30)
>> dfpcore.h(183): Note! N393: col(2) included from DTEST.CPP(8)
>> DTEST.CPP: 63 lines, included 4652, 1 warning, no errors
>>wlink @__wcl__.lnk
>> Open Watcom Linker Version 1.6
>> Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
>> Source code is available under the Sybase Open Watcom Public License.
>> See http://www.openwatcom.org/ for details.
>> loading object files
>> searching libraries
>> Error! E2028: __STK is an undefined reference
>> Error! E2028: window near * near CreateWindow( window_class, char const
>> near *, int, int, int, int, void near *, window near *, int (near *)(),
>> int ) is an undefined reference
>> Error! E2028: void near ProcessMessages() is an undefined reference
>> Error! E2028: classdefs near classdefs[] is an undefined reference
>> Error! E2028: int near MessageBoxProc( window near *, int unsigned,
>> long, long ) is an undefined reference
>> Error! E2028: __anonymous_enum near GenericMessage( window near *, char
>> near *, char near *, int, int (near *)(), char near *, char near *, int,
>> int, int ) is an undefined reference
>> Error! E2028: void near PostMessage( window near *, int unsigned, long,
>> long ) is an undefined reference
>> Error! E2028: _small_code_ is an undefined reference
>> Warning! W1014: stack segment not found
>> Warning! W1023: no starting address found, using :
>> creating a DOS executable
>> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol __STK
>> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol window near *
>> near CreateWindow( window_class, char const near *, int, int, int, int,
>> void near *, window near *, int (near *)(), int )
>> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
>> ProcessMessages()
>> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol classdefs
>> near classdefs[]
>> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol int near
>> MessageBoxProc( window near *, int unsigned, long, long )
>> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol
>> __anonymous_enum near GenericMessage( window near *, char near *, char
>> near *, int, int (near *)(), char near *, char near *, int, int, int )
>> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
>> PostMessage( window near *, int unsigned, long, long )
>> Error: Linker returned a bad status
>>
>> -mr
>
> -appendix-
>
> By changing the name dtes
Re: [Freedos-devel] compiling dflat+
Martin,
Of course I tried under Open Watcom.
Try these lines:
wcc -ml -i=c:\\WATCOM\h -i=c:\freedos\source\INC hworld.c
wlink @owlink.wcl
where owlink.wcl is:
===
system dos
option map
option stack=8192
name hworld.exe
file hworld
libpath c:\freedos\source\lib
libpath c:\watcom\lib286
libpath c:\watcom\lib286\dos
library dflatplo.lib
library dtool2lo.lib
===
And it works for me.
Aitor
2008/9/6 Michael Reichenbach <[EMAIL PROTECTED]>:
> Aitor Santamaría schrieb:
>> No, that I didn't bother to adjust the final makefile to OW.
>
> And did you test to build the example with dflat+ 1.0 and OW 1.6 yourself?
>
>> Check out the wcl options, you just have to tell it the source files,
>> the headers and the libraries, and it should easily create the EXE
>> file.
>
> I have the OpenWatcom Tools.pdf
>
> m{f,s,m,c,l,h} memory model — mf=flat ms=small mm=medium mc=compact ml=large
> mh=huge (default is "ms" for 16-bit and Netware, "mf" for 32-bit)
>
> On the command line, you can list source
> file names as well as object file names. Source files are either
> compiled or assembled based
> on file extension; object files and libraries are simply included in the
> link phase. Options can
> be passed on to both the compiler and linker.
>
> i= add directory to list of include directories
>
>> Then you can put it inside a BAT
>> files.
>
> This is what I currently have:
>
> wcl dtest.cpp C:\devel\dflatP\SOURCE\LIB\DTOOL0LB.LIB
> C:\devel\dflatP\SOURCE\LIB\DFLATPLO.LIB /i=C:\devel\dflatP\SOURCE\INC
> /i=C:\devel\dflatP\SOURCE\LIB /ml
>
> I also tested to put everything from INC and LIB folder to one folder
> (C:\devel\dtest) plus including dtest.cpp. (dtest.cpp is the example
> from DFP100.HTM) And then:
>
> wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
>
> Error message:
> wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
> Open Watcom C/C++16 Compile and Link Utility Version 1.6
> Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved.
> Source code is available under the Sybase Open Watcom Public License.
> See http://www.openwatcom.org/ for details.
> wpp DTEST.CPP
> Open Watcom C++16 Optimizing Compiler Version 1.6
> Portions Copyright (c) 1989-2002 Sybase, Inc. All Rights Reserved.
> Source code is available under the Sybase Open Watcom Public License.
> See http://www.openwatcom.org/ for details.
> dfpcore.h(183): Warning! W146: col(2) unexpected storage class specifier
> found
> dfpcore.h(183): Note! N393: col(2) included from dflatp.h(30)
> dfpcore.h(183): Note! N393: col(2) included from DTEST.CPP(8)
> DTEST.CPP: 63 lines, included 4652, 1 warning, no errors
> wlink @__wcl__.lnk
> Open Watcom Linker Version 1.6
> Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
> Source code is available under the Sybase Open Watcom Public License.
> See http://www.openwatcom.org/ for details.
> loading object files
> searching libraries
> Error! E2028: __STK is an undefined reference
> Error! E2028: window near * near CreateWindow( window_class, char const
> near *, int, int, int, int, void near *, window near *, int (near *)(),
> int ) is an undefined reference
> Error! E2028: void near ProcessMessages() is an undefined reference
> Error! E2028: classdefs near classdefs[] is an undefined reference
> Error! E2028: int near MessageBoxProc( window near *, int unsigned,
> long, long ) is an undefined reference
> Error! E2028: __anonymous_enum near GenericMessage( window near *, char
> near *, char near *, int, int (near *)(), char near *, char near *, int,
> int, int ) is an undefined reference
> Error! E2028: void near PostMessage( window near *, int unsigned, long,
> long ) is an undefined reference
> Error! E2028: _small_code_ is an undefined reference
> Warning! W1014: stack segment not found
> Warning! W1023: no starting address found, using :
> creating a DOS executable
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol __STK
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol window near *
> near CreateWindow( window_class, char const near *, int, int, int, int,
> void near *, window near *, int (near *)(), int )
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
> ProcessMessages()
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol classdefs
> near classdefs[]
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol int near
> MessageBoxProc( window near *, int unsigned, long, long )
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol
> __anonymous_enum near GenericMessage( window near *, char near *, char
> near *, int, int (near *)(), char near *, char near *, int, int, int )
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
> PostMessage( window near *, int unsigned, long, long )
> Error: Linker returned a bad status
>
> -mr
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>
Re: [Freedos-devel] compiling dflat+
Michael Reichenbach schrieb:
> Aitor Santamaría schrieb:
>> No, that I didn't bother to adjust the final makefile to OW.
>
> And did you test to build the example with dflat+ 1.0 and OW 1.6 yourself?
>
> > OpenWatcom comes with the wcl utility (compile and link). Why don't
>> you try that instead of WMAKE?
>
> Don't know but I will try.
>
>> I guess it'll be easier, and you can
>> create HWORLD.EXE in a single line.
>
> Yes.
>
>> Check out the wcl options, you just have to tell it the source files,
>> the headers and the libraries, and it should easily create the EXE
>> file.
>
> I have the OpenWatcom Tools.pdf
>
> m{f,s,m,c,l,h} memory model — mf=flat ms=small mm=medium mc=compact ml=large
> mh=huge (default is "ms" for 16-bit and Netware, "mf" for 32-bit)
>
> On the command line, you can list source
> file names as well as object file names. Source files are either
> compiled or assembled based
> on file extension; object files and libraries are simply included in the
> link phase. Options can
> be passed on to both the compiler and linker.
>
> i= add directory to list of include directories
>
>> Then you can put it inside a BAT
>> files.
>
> This is what I currently have:
>
> wcl dtest.cpp C:\devel\dflatP\SOURCE\LIB\DTOOL0LB.LIB
> C:\devel\dflatP\SOURCE\LIB\DFLATPLO.LIB /i=C:\devel\dflatP\SOURCE\INC
> /i=C:\devel\dflatP\SOURCE\LIB /ml
>
> I also tested to put everything from INC and LIB folder to one folder
> (C:\devel\dtest) plus including dtest.cpp. (dtest.cpp is the example
> from DFP100.HTM) And then:
>
> wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
>
> Error message:
> wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
> Open Watcom C/C++16 Compile and Link Utility Version 1.6
> Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved.
> Source code is available under the Sybase Open Watcom Public License.
> See http://www.openwatcom.org/ for details.
>wpp DTEST.CPP
> Open Watcom C++16 Optimizing Compiler Version 1.6
> Portions Copyright (c) 1989-2002 Sybase, Inc. All Rights Reserved.
> Source code is available under the Sybase Open Watcom Public License.
> See http://www.openwatcom.org/ for details.
> dfpcore.h(183): Warning! W146: col(2) unexpected storage class specifier
> found
> dfpcore.h(183): Note! N393: col(2) included from dflatp.h(30)
> dfpcore.h(183): Note! N393: col(2) included from DTEST.CPP(8)
> DTEST.CPP: 63 lines, included 4652, 1 warning, no errors
>wlink @__wcl__.lnk
> Open Watcom Linker Version 1.6
> Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
> Source code is available under the Sybase Open Watcom Public License.
> See http://www.openwatcom.org/ for details.
> loading object files
> searching libraries
> Error! E2028: __STK is an undefined reference
> Error! E2028: window near * near CreateWindow( window_class, char const
> near *, int, int, int, int, void near *, window near *, int (near *)(),
> int ) is an undefined reference
> Error! E2028: void near ProcessMessages() is an undefined reference
> Error! E2028: classdefs near classdefs[] is an undefined reference
> Error! E2028: int near MessageBoxProc( window near *, int unsigned,
> long, long ) is an undefined reference
> Error! E2028: __anonymous_enum near GenericMessage( window near *, char
> near *, char near *, int, int (near *)(), char near *, char near *, int,
> int, int ) is an undefined reference
> Error! E2028: void near PostMessage( window near *, int unsigned, long,
> long ) is an undefined reference
> Error! E2028: _small_code_ is an undefined reference
> Warning! W1014: stack segment not found
> Warning! W1023: no starting address found, using :
> creating a DOS executable
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol __STK
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol window near *
> near CreateWindow( window_class, char const near *, int, int, int, int,
> void near *, window near *, int (near *)(), int )
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
> ProcessMessages()
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol classdefs
> near classdefs[]
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol int near
> MessageBoxProc( window near *, int unsigned, long, long )
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol
> __anonymous_enum near GenericMessage( window near *, char near *, char
> near *, int, int (near *)(), char near *, char near *, int, int, int )
> file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
> PostMessage( window near *, int unsigned, long, long )
> Error: Linker returned a bad status
>
> -mr
-appendix-
By changing the name dtest.cpp to dtest.c and using
wcl dtest.c DTOOL0LB.LIB DFLATPLO.LIB -ml
(also tested DTOOL1LB.LIB and DTOOL2LB.LIB with same result)
I could decrease the number of errors. The new error messages:
wcl dtest.c DTOOL1LB.LIB DFLATPLO.LIB -ml
Open Watcom C/C++16 Compile and Link Utility Version 1.6
Portions Copyri
Re: [Freedos-devel] compiling dflat+
Aitor Santamaría schrieb:
> No, that I didn't bother to adjust the final makefile to OW.
And did you test to build the example with dflat+ 1.0 and OW 1.6 yourself?
> OpenWatcom comes with the wcl utility (compile and link). Why don't
> you try that instead of WMAKE?
Don't know but I will try.
> I guess it'll be easier, and you can
> create HWORLD.EXE in a single line.
Yes.
> Check out the wcl options, you just have to tell it the source files,
> the headers and the libraries, and it should easily create the EXE
> file.
I have the OpenWatcom Tools.pdf
m{f,s,m,c,l,h} memory model — mf=flat ms=small mm=medium mc=compact ml=large
mh=huge (default is "ms" for 16-bit and Netware, "mf" for 32-bit)
On the command line, you can list source
file names as well as object file names. Source files are either
compiled or assembled based
on file extension; object files and libraries are simply included in the
link phase. Options can
be passed on to both the compiler and linker.
i= add directory to list of include directories
> Then you can put it inside a BAT
> files.
This is what I currently have:
wcl dtest.cpp C:\devel\dflatP\SOURCE\LIB\DTOOL0LB.LIB
C:\devel\dflatP\SOURCE\LIB\DFLATPLO.LIB /i=C:\devel\dflatP\SOURCE\INC
/i=C:\devel\dflatP\SOURCE\LIB /ml
I also tested to put everything from INC and LIB folder to one folder
(C:\devel\dtest) plus including dtest.cpp. (dtest.cpp is the example
from DFP100.HTM) And then:
wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
Error message:
wcl dtest.cpp DTOOL0LB.LIB DFLATPLO.LIB
Open Watcom C/C++16 Compile and Link Utility Version 1.6
Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
wpp DTEST.CPP
Open Watcom C++16 Optimizing Compiler Version 1.6
Portions Copyright (c) 1989-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
dfpcore.h(183): Warning! W146: col(2) unexpected storage class specifier
found
dfpcore.h(183): Note! N393: col(2) included from dflatp.h(30)
dfpcore.h(183): Note! N393: col(2) included from DTEST.CPP(8)
DTEST.CPP: 63 lines, included 4652, 1 warning, no errors
wlink @__wcl__.lnk
Open Watcom Linker Version 1.6
Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
loading object files
searching libraries
Error! E2028: __STK is an undefined reference
Error! E2028: window near * near CreateWindow( window_class, char const
near *, int, int, int, int, void near *, window near *, int (near *)(),
int ) is an undefined reference
Error! E2028: void near ProcessMessages() is an undefined reference
Error! E2028: classdefs near classdefs[] is an undefined reference
Error! E2028: int near MessageBoxProc( window near *, int unsigned,
long, long ) is an undefined reference
Error! E2028: __anonymous_enum near GenericMessage( window near *, char
near *, char near *, int, int (near *)(), char near *, char near *, int,
int, int ) is an undefined reference
Error! E2028: void near PostMessage( window near *, int unsigned, long,
long ) is an undefined reference
Error! E2028: _small_code_ is an undefined reference
Warning! W1014: stack segment not found
Warning! W1023: no starting address found, using :
creating a DOS executable
file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol __STK
file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol window near *
near CreateWindow( window_class, char const near *, int, int, int, int,
void near *, window near *, int (near *)(), int )
file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
ProcessMessages()
file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol classdefs
near classdefs[]
file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol int near
MessageBoxProc( window near *, int unsigned, long, long )
file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol
__anonymous_enum near GenericMessage( window near *, char near *, char
near *, int, int (near *)(), char near *, char near *, int, int, int )
file DTEST.obj(C:\DEVEL\DTEST\DTEST.CPP): undefined symbol void near
PostMessage( window near *, int unsigned, long, long )
Error: Linker returned a bad status
-mr
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] compiling dflat+
Hello,
2008/9/6 Michael Reichenbach <[EMAIL PROTECTED]>:
>> Also note that Borland's make and Watcom's wmake work a bit
>> differently, so maybe the changes are more than expected.
>
> Shall this implicate you didn't test it with watcom? (Sorry if my
> understanding of English is weak.)
No, that I didn't bother to adjust the final makefile to OW.
>> and if you continue to have
>> problems with that, ask to see if we can help.
>
> Thanks. Maybe you could have a look at my makefile?
> http://nopaste.com/p/aUtgTxnkp
I am afraid that the compile options (-m${MODEL}, ${CCEXTRA}) are
BorlandC specific, so you'll have to tune them up to BorlandC.
I think you'll have problems with linking, you need to create a
"linking descriptor" file for OW C/C++ (see the EDIT example). Also I
left some dirty stuff about names. Change the ${BIN_PATH} to
${OUTPATH_BIN} as the folder were HWORLD.EXE will be placed.
OpenWatcom comes with the wcl utility (compile and link). Why don't
you try that instead of WMAKE? I guess it'll be easier, and you can
create HWORLD.EXE in a single line. Then you can put it inside a BAT
files.
Check out the wcl options, you just have to tell it the source files,
the headers and the libraries, and it should easily create the EXE
file.
Aitor
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] compiling dflat+
Aitor Santamaría schrieb: > If you plan to develop for OpenWatcom C/C++ you'll need > to edit the makefile yourself and comment some lines in/out. wcc is > the compiler executable for open watcom. Done that already. So far only the HEADERS=tcdef.sym is questionable for me what to use for watcom. > Also note that Borland's make and Watcom's wmake work a bit > differently, so maybe the changes are more than expected. Shall this implicate you didn't test it with watcom? (Sorry if my understanding of English is weak.) > and if you continue to have > problems with that, ask to see if we can help. Thanks. Maybe you could have a look at my makefile? http://nopaste.com/p/aUtgTxnkp -mr - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] compiling dflat+
Michael, The HW.MAK as it is (Makefile for "Hello World"), is ready to compile for BorlandC. If you plan to develop for OpenWatcom C/C++ you'll need to edit the makefile yourself and comment some lines in/out. wcc is the compiler executable for open watcom. In many cases (as now) you need to tune by hand a bit the makefiles. Also note that Borland's make and Watcom's wmake work a bit differently, so maybe the changes are more than expected. Please read some WMAKE documentation from OpenWatcom, and if you continue to have problems with that, ask to see if we can help. Aitor 2008/9/6 Michael Reichenbach <[EMAIL PROTECTED]>: > unable to find "wcc.exe" > > A bit confusing. HW.MAK doesn't include the term wcc.exe, how can > executing HW.MAK with wmake bring this error? However, wcc.exe can be > started from any directory directly because it's in path. > > -mr > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
