Re: ver 4.0 No way to build new binaries
- Posted by bernie Apr 08, 2009
- 1041 views
Why did this mention two SVN and then just say to change one filename in one SVN ?
In 1709 the Windows build changed, I then had to work on the unix builds. They were finally changed in 1713. I forgot to mention in that post that if you are building a unix target from SVN, then you need to move ecu to eui. That would have happened at 1713.
When do the other names have to be changed ?
No other names need to be changed.
What do you have to change when you transition from SVN 1709 to SVN 1713 ?
What do you have to change to transition from SVN 1713 to higher SVNs ?
Nothing. It was windows change (1709) and unix change (1713).
What are you going to do about running the code in the archive ?
Same it has always been, programs that have a breaking change will need to be updated by their author.
Jeremy
I just built SVN 1700 and that was fine.
I then updated to SVN 1709 and changed exwc.exe file to eui.exe and tried building binaries for SVN 1709 with this error
<quote screen>
tab.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_w.c -fo=E:\dummey\source\intobj\back\be_w.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_socket.c -fo=E:\dummey\source\intobj\back\be_soc ket.obj wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s /I..\ /ol /zp8 /d EWINDOWS /dEWATCOM /dEOW be_pcre.c -fo=E:\dummey\source\intobj\back\be_pcre. obj e:\dummey\bin\eui.exe -i ..\include revget.ex revget.ex:58 in function is_current() slice length is less than 0 (-4) ... called from revget.ex:205 in procedure rev_1_4() ... called from revget.ex:259 in procedure rev_1_3() ... called from revget.ex:276 --> See ex.err Press Enter...</quote>
