Subj : Re: Linker Warning: Module Def File
To   : borland.public.cpp.borlandcpp
From : Ed Mulroy [TeamB]
Date : Sun Jan 23 2005 01:49 am

The warning is correct.

Every executable built for 16 bit Windows requires a module definition file.
That file is where the stack size is specified and it can also be used to
specify other items.

When the linker found that you did not provide such a file, instead of
generating an error it instead used default.def and told you of what it did.

If you do not want the warning then add a module definition file to the
project.

..  Ed

> Todd Burch wrote in message
> news:41f2dc3d$1@newsgroups.borland.com...
>
> I get a warning every time I link that a module definition file
> does not exist and the default options are being used.
>
> Being the anal retentive person I am, I don't want to get this
> warning any more.
>
> My program is test1.cpp.  I created a file called test1.def and
> put it in the same directory, with a few typical module
> definition statements in it (like NAME test1, etc.)
>
> But, it's not being picked up/recognized.
>
> I tried running IMPDEF, but that didn't seem to do anything and
> appeared to require a DLL to exist before running.
>
> I could not find in the manual or help system
> anywhere where it said where this
> file was supposed to reside.  Looking through the samples that
> came with BC++ 3.1, there are a few module definition files, so
> it seems as if this is not a required file (and my program does
> run just fine without it) and they all (the sample .def files)
> reside in the same directory as the sample source files.
>
> And, I searched this forum too.  Nothing.
>
> I've looked all through the menus to see if there might be
> a place that I could set a linker switch to not look for this,
> or to set enough checkboxes (or whatever) so that I could
> override the defaults, but alas, no success.
>
> I'm running BCW.

.