1. CHANGES IN BUILDING SOURCE ?
- Posted by bernie Feb 26, 2009
- 870 views
- Last edited Feb 27, 2009
I can no longer build the source because changes have been
made without notifying or explaining how to use the changes
in the build process.
First I don't see a makefile.wat and I don't understand how to
just build WIN98 and XP binaries with these changes.
I was using a batch file and the batch can't use the new process
without explanation about how to use wmake that comes with
Watcom.
This has been changed just prior to Matt fixing the callback problem.
So whoever came up with the changes needs to explain to the other
users what its all about ???
Does this mean that we can't use wmake ??
2. Re: CHANGES IN BUILDING SOURCE ?
- Posted by mattlewis (admin) Feb 26, 2009
- 849 views
- Last edited Feb 27, 2009
I can no longer build the source because changes have been
made without notifying or explaining how to use the changes
in the build process.
First I don't see a makefile.wat and I don't understand how to
just build WIN98 and XP binaries with these changes.
I was using a batch file and the batch can't use the new process
without explanation about how to use wmake that comes with
Watcom.
This has been changed just prior to Matt fixing the callback problem.
So whoever came up with the changes needs to explain to the other
users what its all about ???
Does this mean that we can't use wmake ??
You have to use wmake. Shawn has made more configuration changes, that allow more flexibility in where things end up. There's a mention about it in the commit log (r1392, which was the one that broke callbacks, BTW).
Matt
3. Re: CHANGES IN BUILDING SOURCE ?
- Posted by DerekParnell (admin) Feb 26, 2009
- 796 views
- Last edited Feb 27, 2009
I can no longer build the source because changes have been
made without notifying or explaining how to use the changes
in the build process.
I was wondering what you meant because I built the binaries just fine after that change, but I just went to rebuild them now and I can't either. A quick look at the changes seems to indicate that the "distclean" option deletes makefile.wat file. That has got to be a mistake.
I'll revert and see if I can fix this up.
4. Re: CHANGES IN BUILDING SOURCE ?
- Posted by DerekParnell (admin) Feb 26, 2009
- 800 views
- Last edited Feb 27, 2009
I can no longer build the source ...
I've uploaded a repaired makefile.wat. I can now build the system ok, but I'm not trying to build a release for win98 either. I don't know what options were/are required to do that.
Here is the batch file that I use ...
%echo off set EDJGPP= set ORIGINALWATCOM= set EBORLAND= set ELCC= set EMINGW= set EUNIX= set SRC=C:\Projects\eu_proj\eu40\trunk\source set BIN=C:\Projects\eu_proj\eu40\trunk\bin set BKUP=C:\backup\eubin cd %SRC% wmake -f makefile.wat clean wmake -f makefile.wat distclean call configure %1 %2 %3 wmake -f makefile.wat all %echo off echo Backing up previous binaries... if exist %BIN%\BACKENDD.EXE copy /Y /B %BIN%\BACKENDD.EXE %BKUP%\ if exist %BIN%\EC.EXE copy /Y /B %BIN%\EC.EXE %BKUP%\ if exist %BIN%\ec.lib copy /Y /B %BIN%\ec.lib %BKUP%\ if exist %BIN%\EX.EXE copy /Y /B %BIN%\EX.EXE %BKUP%\ if exist %BIN%\backendc.exe copy /Y /B %BIN%\BACKENDC.EXE %BKUP%\ if exist %BIN%\backendw.exe copy /Y /B %BIN%\BACKENDW.EXE %BKUP%\ if exist %BIN%\ecw.lib copy /Y /B %BIN%\ecw.lib %BKUP%\ if exist %BIN%\ecw.exe copy /Y /B %BIN%\ecw.exe %BKUP%\ if exist %BIN%\exwc.exe copy /Y /B %BIN%\exwc.exe %BKUP%\ if exist %BIN%\exw.exe copy /Y /B %BIN%\exw.exe %BKUP%\ echo Move new binaries to BIN if exist %SRC%\BACKENDD.EXE move /Y %SRC%\BACKENDD.EXE %BIN%\ if exist %SRC%\EC.EXE move /Y %SRC%\EC.EXE %BIN%\ if exist %SRC%\ec.lib move /Y %SRC%\ec.lib %BIN%\ if exist %SRC%\EX.EXE move /Y %SRC%\EX.EXE %BIN%\ if exist %SRC%\backendc.exe move /Y %SRC%\BACKENDC.EXE %BIN%\ if exist %SRC%\backendw.exe move /Y %SRC%\BACKENDW.EXE %BIN%\ if exist %SRC%\ecw.lib move /Y %SRC%\ecw.lib %BIN%\ if exist %SRC%\ecw.exe move /Y %SRC%\ecw.exe %BIN%\ if exist %SRC%\exwc.exe move /Y %SRC%\exwc.exe %BIN%\ if exist %SRC%\exw.exe move /Y %SRC%\exw.exe %BIN%\
5. Re: CHANGES IN BUILDING SOURCE ?
- Posted by bernie Feb 27, 2009
- 748 views
Thanks MATT and DEREK for your replies.
Derek your changes didn't solve the problem.
This is the same problem that I've seen in the past but
someone corrected it at that time but I don't know what they did.
Here is my screen where it fails during the build.
r.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_runtime.c -fo=E:\eu_master\source\dosobj\back\be_runtime. obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_symtab.c -fo=E:\eu_master\source\dosobj\back\be_symtab.ob j wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_w.c -fo=E:\eu_master\source\dosobj\back\be_w.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW be_regex.c -fo=E:\eu_master\source\dosobj\back\be_regex.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /dEDOS /dEWATCOM /dEOW regex.c -fo=E:\eu_master\source\dosobj\back\regex.obj wlink @E:\eu_master\source\dosobj\ex.lbc name E:\eu_master\source\ex.exe le23p E:\eu_master\source\ex.exe ------------------------------------------------------------------------------- LE to 3P Converter v2.02 Copyright 1994-96 Michael Devore; all rights reserved. ------------------------------------------------------------------------------- Reading specified LE file. Could not open specified LE file. Error(E42): Last command making (E:\eu_master\source\ex.exe) returned a bad stat us Should this file be deleted [Yes/No] ?
There is something wrong or missing in the MAKEFILE.WAT file.
As you can see le23p doesn't like the ex.exe thats built.
I can build SVN 1390 without errors but there is no way to use
that makefile in the latest SVN because of all the changes.
If the makefile is going to be changed then it has to be tested
on ALL SYSTEMS not just the one that the author is testing on.
I am using a XP system; I am not sure what all the options are
for in the configuration are used for ?
All I want to do is build a set of binaries for XP and one for WIN98.
which I could do before the makefile was changed.
Am I the only dummy on this forum ?
6. Re: CHANGES IN BUILDING SOURCE ?
- Posted by mattlewis (admin) Feb 27, 2009
- 752 views
Thanks MATT and DEREK for your replies.
Derek your changes didn't solve the problem.
This is the same problem that I've seen in the past but
someone corrected it at that time but I don't know what they did.
I am using a XP system; I am not sure what all the options are
for in the configuration are used for ?
All I want to do is build a set of binaries for XP and one for WIN98.
which I could do before the makefile was changed.
Am I the only dummy on this forum ?
No. Similar things have happened several times, where configure options were changed without much documentation or notice given. I rarely build DOS binaries, but I suspect that you may need to set the eubin config option. Could you post your config.wat file?
Matt
7. Re: CHANGES IN BUILDING SOURCE ?
- Posted by bernie Feb 27, 2009
- 758 views
No. Similar things have happened several times, where configure options were changed without much documentation or notice given. I rarely build DOS binaries, but I suspect that you may need to set the eubin config option. Could you post your config.wat file?
My build batch file.
This has worked in the past.
-------------------------------------------------------eubin e:\eu_master\bin
set SRC=E:\eu_master\source
set BIN=E:\eu_master\bin
set WIN98=E:\WIN98BIN
set WINXP=E:\WINXPBIN
wmake -f makefile.wat clean
wmake -f makefile.wat distclean
call configure
wmake -f makefile.wat all
echo COPYING WINXP BINARIES WINXPBIN
if exist %SRC%\BACKENDD.EXE copy /Y %SRC%\BACKENDD.EXE %WINXP%\
if exist %SRC%\EC.EXE copy /Y %SRC%\EC.EXE %WINXP%\
if exist %SRC%\ec.lib copy /Y %SRC%\ec.lib %WINXP%\
if exist %SRC%\EX.EXE copy /Y %SRC%\EX.EXE %WINXP%\
if exist %SRC%\backendc.exe copy /Y %SRC%\BACKENDC.EXE %WINXP%\
if exist %SRC%\backendw.exe copy /Y %SRC%\BACKENDW.EXE %WINXP%\
if exist %SRC%\ecw.lib copy /Y %SRC%\ecw.lib %WINXP%\
if exist %SRC%\ecw.exe copy /Y %SRC%\ecw.exe %WINXP%\
if exist %SRC%\exwc.exe copy /Y %SRC%\exwc.exe %WINXP%\
if exist %SRC%\exw.exe copy /Y %SRC%\exw.exe %WINXP%\
echo MOVING THE WINXP BINARIES TO eu_master\BIN
if exist %SRC%\BACKENDD.EXE move /Y %SRC%\BACKENDD.EXE %BIN%\
if exist %SRC%\EC.EXE move /Y %SRC%\EC.EXE %BIN%\
if exist %SRC%\ec.lib move /Y %SRC%\ec.lib %BIN%\
if exist %SRC%\EX.EXE move /Y %SRC%\EX.EXE %BIN%\
if exist %SRC%\backendc.exe move /Y %SRC%\BACKENDC.EXE %BIN%\
if exist %SRC%\backendw.exe move /Y %SRC%\BACKENDW.EXE %BIN%\
if exist %SRC%\ecw.lib move /Y %SRC%\ecw.lib %BIN%\
if exist %SRC%\ecw.exe move /Y %SRC%\ecw.exe %BIN%\
if exist %SRC%\exwc.exe move /Y %SRC%\exwc.exe %BIN%\
if exist %SRC%\exw.exe move /Y %SRC%\exw.exe %BIN%\
wmake -f makefile.wat clean
wmake -f makefile.wat distclean
call configure eubin e:\eu_master\bin managed-mem
wmake -f makefile.wat
echo MOVING THE WIN98 BINARIES TO WIN98BIN
if exist %SRC%\BACKENDD.EXE move /Y %SRC%\BACKENDD.EXE %WIN98%\
if exist %SRC%\EC.EXE move /Y %SRC%\EC.EXE %WIN98%\
if exist %SRC%\ec.lib move /Y %SRC%\ec.lib %WIN98%\
if exist %SRC%\EX.EXE move /Y %SRC%\EX.EXE %WIN98%\
if exist %SRC%\backendc.exe move /Y %SRC%\BACKENDC.EXE %WIN98%\
if exist %SRC%\backendw.exe move /Y %SRC%\BACKENDW.EXE %WIN98%\
if exist %SRC%\ecw.lib move /Y %SRC%\ecw.lib %WIN98%\
if exist %SRC%\ecw.exe move /Y %SRC%\ecw.exe %WIN98%\
if exist %SRC%\exwc.exe move /Y %SRC%\exwc.exe %WIN98%\
if exist %SRC%\exw.exe move /Y %SRC%\exw.exe %WIN98%\
set SRC=
set BIN=
set WIN98=
set WINXP=
echo OPERATION COMPLETE !
pause
This is what my config.wat looks like.
-------------------------------------------------------
# Configuration for Watcom
EUBIN=e:\eu_master\bin
EUPHORIA=1
DELTREE=del /Q /S
RM=del /Q
RMDIR=rmdir /Q/S
TRUNKDIR=E:\eu_master
BUILDDIR=E:\eu_master\source
The compiler runs so fast that it is hard to see what
it is doing during the compile.
I think it has to do something with DOS having to use
managed memory in some part of the makefile but the
make file is too complicated for me figure out.
Maybe someone that understands it can look makefile.wat
from SVN1388 and compare it with the new makefile.wat and
determine whats wrong or different with the new makefile.
8. Re: CHANGES IN BUILDING SOURCE ?
- Posted by DerekParnell (admin) Feb 27, 2009
- 749 views
I've found the problem, but I'm still working on the solution.
The problem is that the program lp23p does not understand about long directory names. It can't find e:\eu_master\source\ex.exe because "eu_master" is 9 characters long.
The changes to makefile.wat included not assuming that the current directory is set to the source directory. Now it puts the full path of the 'target' file on the various command lines.
My build batch file.
This has worked in the past.
Just a suggestion, but might it be better to move the XP binaries after you build the win98 binaries. That way, you are using the same binaries to build the new XP set and the new 98 set. Currently, you build a new XP set, move them then use that new set to build the 98 binaries.
9. Re: CHANGES IN BUILDING SOURCE ?
- Posted by DerekParnell (admin) Feb 27, 2009
- 758 views
A new makefile.wat has been uploaded. Hope it works for you now. I used a copy of your batch file to test it on my system and it works here.
10. Re: CHANGES IN BUILDING SOURCE ?
- Posted by bernie Feb 27, 2009
- 834 views
A new makefile.wat has been uploaded. Hope it works for you now. I used a copy of your batch file to test it on my system and it works here.
Thanks Derek:
That fixed the makefile.wat.
I can now build the binaries.
I'am getting a bad routine_id from a call_back
so I now have to find what causing that problem
This is a strange problem because it is the second place
in my code where I'am assigning a call_back to WinProc()
Yet it worked the first time I did it in my code.
Why does setting a call_back to a routine always return a
different address I would think each time it would be the
same but thats the way it worked ver3.11 also ??
Thanks again to you and Matt.