Hi! group,

I've built MFC 4.2 (nafxcw.lib) using 8.28 beta. But when I link my application, I get the following warning from the linker and the application fails to start.

OPTLINK : Warning 134 : No Start Address

What does this mean ?

thanks in advance,
-Krishnakumar

It's probably because the linker is looking for a 'main' and not for a 'WinMain'

Make sure you .def file uses:

EXETYPE        NT
SUBSYSTEM    WINDOWS,4.0

And include the .def file in your link command.

Jan



"V. Krishnakumar" wrote:

> Hi! group,
>
> I've built MFC 4.2 (nafxcw.lib) using 8.28 beta. But when I link my application, I get the following warning from the linker and the application fails to start.
>
> OPTLINK : Warning 134 : No Start Address
>
> What does this mean ?
>
> thanks in advance,
> -Krishnakumar

"Jan Knepper" <jan@smartsoft.cc> wrote in message news:3CC459FD.F4970216@smartsoft.cc...
> It's probably because the linker is looking for a 'main' and not for a
'WinMain'
>
> Make sure you .def file uses:
>
> EXETYPE        NT
> SUBSYSTEM    WINDOWS,4.0
>
> And include the .def file in your link command.
>

I did that and still get the same error (134: No Start Address)

TIA,

-Krish

No start address means you need a main(), a WinMain(), or a DllMain()
function to serve as entry point for your exe/dll.

"V. Krishnakumar" <lvimala@eth.net> wrote in message news:aa83ui$1t80$1@digitaldaemon.com...
>
> "Jan Knepper" <jan@smartsoft.cc> wrote in message news:3CC459FD.F4970216@smartsoft.cc...
> > It's probably because the linker is looking for a 'main' and not for a
> 'WinMain'
> >
> > Make sure you .def file uses:
> >
> > EXETYPE        NT
> > SUBSYSTEM    WINDOWS,4.0
> >
> > And include the .def file in your link command.
> >
>
> I did that and still get the same error (134: No Start Address)
>
> TIA,
>
> -Krish
>
>
>