RE: [Dev-C++] Still more linker problems...

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

It's a bit strange, because the inline functions should generate code
placed in Common segments, and the linker should accept multiple
definitions of symbols in Common segments as long as the Common blocks are
identical. It's only with --warn-common that the linker should emit a
warning for a symbol available in more than one Common block.

/Per W

On Thu, 3 Jun 2004, Siva Chandra wrote:

>
> Hello,
>
> --- Per Westermark <pw...@ia...> wrote:
> > When you create a library, you are supposted to
> > _link_ to the functions in
> > the library. What use is a library if you are using
> > inline functions?
>
> The library( I created a hypothetical situation, but I
> was trying to build OpenCV) and the header file has
> other non-inline functions too. This header comes
> along with 100-odd C++ source files which define the
> other non-inline functions declared in the header. So
> I followed the normal procedure and compiled and ar'ed
> them into a *.a file!
>
> Siva Chandra
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Friends.  Fun.  Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>