1  |   Order by index

Sep 10, 1998, 1:17am

Ok when I use the compiler it says theres to many errors in aw.h than I
run it with the .lib included and it generates the proggy ut the proggy
crashes the second I open it...

Sep 10, 1998, 4:05am

What compiler are you using? I suppose I should have mentioned that so far
the SDK has only been tested with Visual C++.

-Roland

[View Quote]

Sep 10, 1998, 10:22am

Maybe I should try saving it as C++ huh? :)
[View Quote]

Sep 10, 1998, 7:50pm

Just FYI, I tried running the sample program with Borland C++ 4.01 (I know
precious little C - the basic stuff - slowly learning more) and it seems
it's having problems either finding the stuff in aw.h or in aw.dll - pops up
13 error messages saying stuff about the aw_xyz_abc calls... Does the
compiler have to be able to write 100% Windows 95 programs? cos this one
only goes as far as Win32 proggies... And yes, all the files from the SDK as
well as the .cpp file I have the sample proggie code in are in the same
directory (dumped them into F:\Active Worlds\sdk, if it matters).

[View Quote]

Sep 10, 1998, 10:40pm

I'm not sure but I *think* this is a problem with the aw.lib file being in a
format that Borland doesn't like. I used Borland once upon a time long ago
and I vaguely recall this being an issue - Microsoft and Borland .lib files
are in different formats. If anyone happens to know how to make a Borland
..lib file without actually having to purchase Borland, please let me know.
:)

-Roland

[View Quote]

Sep 10, 1998, 10:42pm

>Just FYI, I tried running the sample program with Borland C++ 4.01 (I know

oops just for clarity's sake, just checked and it's actually 4.02 :)

[View Quote]

Sep 11, 1998, 1:17am

I've been starving myself of the newsgroups for a long time, but I figured
I'd stick my neck out on this one (I use Borland myself). I know this
applies to C++ Builder, which is what I use, but it seems to be a general
thing. Check it out:
http://www.inprise.com/devsupport/bcppbuilder/qna/257.html
I've been having some problems with the fact that my 'main' function becomes
undefined, but I figure this gets us down from 13 LinkerErrors to one. Why
not kill 12 birds with one stone? Anyway, the dilemma with main() is that
when you cut off the underscores, it looks for main() and sees _main()
instead (I think). I'm also assuming that Roland uses main() in the .LIB
file, since when I #define main _main it misses all the SDK's functions
again. A paradox to me, but maybe not to a more experienced programmer.
Hmmm?

-Cyborganic

[View Quote]

Sep 11, 1998, 1:32am

main() isn't used or referenced anywhere in the SDK files, so I'm not sure
why doing a #define main _main is changing the way the linker looks for the
SDK entry points. How about instead of doing a #define, just declare the
routine as _main() instead of main().

That's a useful page though, I'll keep it bookmarked for future reference.

-Roland

[View Quote]

Sep 11, 1998, 9:51pm

Myabe I'm just missing something, but it seems that Borland won't let me do
that... I can't find a way to set it to _main() without having the compiler
*automatically* disable all its 'make' and 'compile' menu items and buttons.

[View Quote]

1  |   Order by index