How to allow duplicate symbols between modules ??

Say I have two source programs A.C and B.C, which both include a header file called XX.H. I have defined
a variable 'xyz' in this header file. While linking, this gives an error like "xyz defined in A.C is duplicated in B.C".

Particularly I am using BC++4.52 compiler. Is there any
compiler/linker setting that can help me get rid of such huge no.of errors ??

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

can you give question clearly.

Hi alseenu !!
  U can have the header directive for the XX.H file like

#ifndef _XX_H
#define _XX_H



Now u can include this file as many times u want

try this
use the

This option tells the linker to create a valid .EXE file or DLL even if a symbol is referenced but not defined or is multiply defined.

On the command line, the /FORCE option can take an optional argument:

Use /FORCE:MULTIPLE to create an output file whether or not LINK finds more than one definition for a symbol.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Bootstrap 4: Exploring New Features

Learn how to use and navigate the new features included in Bootstrap 4, the most popular HTML, CSS, and JavaScript framework for developing responsive, mobile-first websites.

Take care that you know what it means to allow multiply defined symbols.  It may mean that two global variables are created and used, and you will not be able to easily check what actually happens.

It might be better to do it properly, that is, if you want a global variable that is declared in a header file, do it like this:

in xx.h

#ifndef _XX_H
#define _XX_H

extern int xyz;


and then have xx.cpp

which has:

#include "xx.h"

int xyz;

The suggestion from akalmani looks a whole lot better then that from inpras. Avoid such settings in the linker and compiler at all cost.
Use the #defines as shown for ALL your headers. It is common practice and will be invaluable if your projects grow in size.
I agree with Jason, do not define code and global data in header files.
I agree with that too.
I aggree with Jason and akalmani and both have the most common answer: declare _shared_ variable name, then define in which .c / .cpp file (so belatly ".o"->Unix, or ".obj" file) you want it declared (in Jason it's in "xx.cpp").

If you want global for both one for each file: a.C and b.C, declare it at ".C" file-scope not in ".h". probably the linker want have it twice.
The #define pre-compiler directive doesn't solve 2 declarations (and that will happen!) one for each file. That works only for Jason solution.

Anyway, if two independent vars one on A and other in B, why don't you just use 2 diferent names ?
I haven't been clear(improving): akalmani suggest one veil and Jason really adds the whole picture.
I described 2 cases:
 - One global scope (between a.C and b.C) var, implemented in xx.C for instance
 - two global scope vars, meaning file-scope, one in a.C and other in b.C. I'm not sure but probably must be two different var names, since compiler doesn't decorate var-symbol with file name("a" or "b") so when linking they conflict (xyz from a and xyz from b).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.