Re: Unreferenced static obj gets eliminated by linker?

From:

Mike M <nospam@nospam.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Fri, 30 Mar 2007 14:45:49 -0500

Message-ID:

<eujpdh05d3@enews2.newsguy.com>

Hmm well that's not working for me. I generally build Debug builds so
/OPT:NOREF's supposed to be on already. I confirmed this by using
/VERBOSE:REF and toggling /OPT:[REF|NOREF] and I believe it to be true.

One more bit of info is that the module being excluded is in a static
library. I've confirmed that the module is in the static lib (with
dumpbin) but it's not making it to the .exe.

Perhaps there's an issue with /opt:noref on a static .lib? I've run
into one or two other issues with static libs in VS2005. I suppose
the blessed way to do this is with a .dll.

Thanks,
Mike

Joseph M. Newcomer wrote:

Add /OPT:NOREF to the linker command line.
joe

On Thu, 29 Mar 2007 18:01:19 -0500, Mike M <nospam@nospam.com> wrote:

I've got these derived classes which register themselves (via inherited
methods) at run time through a registration call in the constructor.
I forget the pattern name but...

Each derived class lives in a seperate .cpp file. There's no need for a
.h file since nothing ever constructs one but itself. The .cpp file
looks like;

class MyDerived: public MyBase {
public:
MyDerived::MyDerived() {
registerThySelf(){m_Name="o1";...}
} MyInstance;

Then at runtime I call base methods to get a list of the derived objs
and call them through polymorphism, etc.

Problem is MyInstance is not being instantiated at runtime. I suspect
it's because the linker eliminates it because nothing references it.

I used to do this in gnu/g++. How is it done in VS2005?

Thanks,
Mike

Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm