jdb@reef.cis.ufl.edu (Brian K. W. Hook) (01/04/91)
I was writing a simple demo program today using TC++. nothing fancy, nothing special....worked just fine when I compiled within TC. To get smaller code (read: No debug) I tend to exit then run TCC. Thus, this program, which uses graphics: TCC demo works within the environment. But I ran TCC and then tlink, tried a couple of switches (to see if it would open the graphics.lib) and guess what? It trashed GRAPHICS.LIB and about half o f my libraries, probably because of an incorrect switch (tlink has CRAPPY documentation). I did link in a .BGI and .CHR file into the .LIB after running BGIOBJ. This, to me, is not very good. Graphics.lib ended up being 2048 bytes. Oh, after adding the .BGI and .CHR file, it still worked fine. It was when I compiled and linked from the command line that my LIB directory got eaten ALIVE. anyone have any ideas? Brian
nelson@sun.soe.clarkson.edu (Russ Nelson) (01/05/91)
See Marshall Cline's monthly TC++ bug list in comp.lang.c++. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600 It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.