Re: [Dev-C++] implementation .o procedure

[Elizabeth B. <sog...@ya...>]

"Santiago" <sa...@ho...> writes:

> Sorry I'm so new with this. I Tried compiling myClass.cpp
> (implementation of myClass.h) and I don't get the .o file. I only
> get the .o file when I compile the userCode.cpp and the myClass.cpp
> together.

When you compile source code (.c, .cpp, etc), you receive object code
(.o). Granted, it is possible to compile and link in one step, but to
the best of my understanding, Dev-C++ compiles (makes .o files) and
links (make .exe or .dll files) in separate steps. Regardless, you
should have a file entitled "myClass.o" in the same directory as
"myClass.cpp" after you compile. If you are using the "File Open"
dialog to check for myClass.o's existence, make sure you have it set
to "All Files (*.*)" so it will show up.

> In other words, do I have to link the implementation to userCode.cpp
> in order to create the .o file?

No. The .o (object file) is made after compiling a single source code
file.

Elizabeth