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

[Per W. <pw...@ia...>]

And you have to use the same compiler with the same settings - or whatever
combination of compilers/settings that will:
- generate same memory layout of objects
- generate same calling conventions for the class methods
- supply identical definitions of runtime library as used by class code.
- ...

As can be seen, it isn't so easy to just take a precompiled object file,
made by someone else, and just include in a project. When you buy a
software library from a vendor, you either get precompiled libraries for
your compiler (debug + release [+ small/large memory model]), or you get
the full source.

Even under the assumption that the object file is generated with MingW,
you would still like a description of which compiler switches was used
when building the file.

/Per W

On 6 Oct 2002, Elizabeth Barham wrote:

> "Santiago" <sa...@ho...> writes:
> 
> > Does anyone know how use a compiled class implementation (ie: =
> > myClass.o)?
> > The class was defined by someone else. When theygave me the myClass.o =
> > and it's public functions, I was asked to refer to it by using #include =
> > "myClass.h" but that didn't work.
> > Please let me know if you have the correct procedure.
> 
> If I understand you correctly, the implementation is in myClass.o and
> the interface is in myClass.h.
> 
> So, that you do is add myClass.o to the list of object files you use
> to link.
> 
> That is, in the code *you* write, you use #include "myClass.h" but the
> implementation is in myClass.o, so you add myClass.o to the list of
> files you link with.
> 
> Elizabeth
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>