SOURCELIBS, TARGETLIBS

[Tim Clacy]

What's the difference between SOURCELIBS and TARGETLIBS? The documentation
doesn't shed much light... it's like a 'spot the difference' quiz.

[Rupen]

Well, as far I know (that's how I use) following is the difference.

Say, you have a big project with multiple module then and you compile
each of them as seperate library. For your final dll you use those
module library as source module and put under sourcelibs

Your final dll also has to be linked with coredll.lib (for activex
control ole32.lib) etc. So these system suplied dll you put under
targetlibs.

I hope this helps
rupen

"Tim Clacy" <timo...@zonal.co.uk> wrote in message news:<3b9f3d24$0$233$ed9e...@reading.news.pipex.net>...

[Sergey Solyanik [MS]]

This is componentization feature of Windows CE.

The link has two steps. First, whatever is in SOURCELIBS gets combined in a
signle library yourproductname_ALL.lib. In the second step, executable
module is linked from that library and all the targetlibs.

This is done to allow stubs to be conditionally linked: if the function is
defined into your source already, stubs get excluded. If it is not there,
stubbed version (returning ERROR_NOT_IMPLEMENTED or something to that
effect) gets linked in instead.

If the link were to be performed in just one step, it would be impossible to
predict which version (real or stub) would get included. As it is,
implemented functions have a priority over stubs.

--
Sergey Solyanik
Windows CE Core OS

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

"Tim Clacy" <timo...@zonal.co.uk> wrote in message
news:3b9f3d24$0$233$ed9e...@reading.news.pipex.net...