Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

FPC 2.6.4 released! (Announce)

posted by Rugxulo(R) Homepage, Usono, 22.04.2014, 02:18

> The main problems are PPAS.BAT running WLIB with one really long cmdline
> (or, worse, splitting into two [fpctris 91..11, 10..1], which makes my
> kludge run twice unnecessarily). The longest line there is 2064 bytes,
> which is way beyond reasonable. Again, if FPC was smart enough to make the
> response files itself, that would solve this problem. As is, it's a very
> tedious kludge just to get things to work. Oh, and sometimes, depending on
> where WLIB + WLINK are found, it puts their full path in quotes, which
> breaks my kludge.
> ppas.bat :
> g:\others\wlib.exe -q -fo -c gameunit.a\GameUnit0s36.o
>\GameUnit0s35.o\GameUnit0s34.o ...
> if errorlevel 1 goto linkend
> make.bat :
> cd
> dir /b *.o > gameunit.rsp
> wlib.exe -q -fo -c -n ..\gameunit.a @gameunit.rsp
> del gameunit.rsp
> cd..
> if errorlevel 1 goto linkend

Some of these compiler switches get confusing fast. This kludge isn't always 100% necessary just to compile. I mistakenly thought -CX (compiling units) smartlinking was required for everything here, but apparently not. In fact, for simple stuff like fpctris and samegame, it seems to make almost no size difference at all. (Presumably units other than gameunit are much more bloated.)

But I guess? that -XX is always required since (linking) smartlinking makes a difference in whether it looks for libs or objects, and the pre-compiled units are all smartlinked (by necessity?). BTW, I'm not sure if "-Xs" (strip) even does anything here (intentionally or otherwise).

But just for simple stuff, I can get away with "ppcross8086 -XX -O3 samegame", and it'll compile (in DOS) okay, by default, no kludges needed. At least with latest Win32-hosted snapshots (run under HX).

Then I got the "bright" idea to build a helper frontend tool (in 16-bit real mode, using TP55 or FPC itself) to workaround this kludge for me (using -s and tweaking the .BAT output). Or maybe you really expect me to "svn co" trunk (under Linux) and weakly try to fix it there? I just assumed using "chdir" and "dir /b *.o > blah.rsp" was still portable to Windows, but I forgot that somebody might want to cross-compile from Linux. Though I guess it still makes sense for "-st" (target). Or maybe only {$ifdef DOS-hosted}.

Dunno, I just hate that it seems to be so close to being DOS-hosted but not quite there yet. Oh well.

P.S. I guess you heard what was the SourceForge April Community Choice Project of the Month. :-)


Complete thread:

Back to the forum
Board view  Mix view
15296 Postings in 1378 Threads, 254 registered users, 12 users online (0 registered, 12 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum