1  |   Order by index

Oct 20, 1998, 5:31pm

I use the LCC compiler/environment but i can't compile the sample pgm :/ dont know wath i make wrong
and now i'm tired with all the testing!
I think i have to put some in the "#defines" field but wath?? If the field is blank alot error's
about methods coming (unrecognized declaration).
Did anyone work also with LCC and compile the sample pgm??
Thanks for all help!!

Oct 20, 1998, 9:48pm

Can you dump the complete set of error messages you get when you compile. I
do not know the LCC compiler but if it can handle ANSI C you should be able
to make it work.

Edward Sumerfield.

[View Quote]

Oct 21, 1998, 5:50pm

The dump is not mutch. On each line where the methods in aw.h start, the error msg is "unrecognized
declaration". Is this because the compiler dont find the aw.lib? or the aw.dll?

Thanks Plati


Edward Sumerfield schrieb in Nachricht <362d209f.0 at homer>...
>Can you dump the complete set of error messages you get when you compile. I
>do not know the LCC compiler but if it can handle ANSI C you should be able
>to make it work.
>
>Edward Sumerfield.

Oct 21, 1998, 9:32pm

Unrecognized declaration sounds like a compile error as apposed to a linker
error. I don't know how much you know about the compile and link stages of
development. I explained it in a previous post. To summaries

.c+.h compiler to .obj or .o then linker to .exe

Next you must post your code.

Edward Sumerfield.

[View Quote]

Oct 21, 1998, 10:10pm

This is right I think - can someone just confirm this for me?

..c
==[compiler]==> .o[bj] ==[linker]==> .exe
..h .lib

[View Quote] > Unrecognized declaration sounds like a compile error as apposed to a linker
> error. I don't know how much you know about the compile and link stages of
> development. I explained it in a previous post. To summaries
>
> .c+.h compiler to .obj or .o then linker to .exe
>
> Next you must post your code.
>
> Edward Sumerfield.
>
[View Quote]

Oct 22, 1998, 12:29am

This is basically right. I would modify it by moving your .lib

..c
==[compiler]==> .o[bj] ======================[linker]==> .exe
..h =====[archive]=>.lib =====>

[linker]==> .dll

The "ar" command takes a group of objects and puts them into a lib file.
This lib file is then used by the linker to resolve function calls to entry
points within those objects.

The only other addition is the dll (dynamic link library). An exe file will
contain the functions that are linked from a .lib file but a linker will not
include functions from a dll file into the exe file. Instead they are
"linked" at run time. Usually when they are first called but in windows case
there is specific code to load the dll and resolve the points to the
functions within it.

Edward Sumerfield.

[View Quote]

1  |   Order by index