Re: [Plib-devel] Example Program Changes

[<p.l...@ci...>]

Scrive Wolfram Kuss <w_...@rz...>:

> I wrote:
>
> >M. wrote:
> >
> >>
> >>    p-guide doesn't compile. It issues this error message:
> >
> >It does not compile under Windows with a clean checkout either.
>
> I finally can commit to SVN and am so spending a bit more time.
> The issue with the MSVC6 compilation actually was fairly trivial and
> MSVC6 specific; It did not link to puAux in the *.dsp (MSVC6 project).
>
> Fixed and committed, here is the output of compilation:
>
> ------------Configuration: pGuide - Win32 Release----------------
> Compiling...
> LoadSave.cxx
> pGuide.cxx
> PropertiesWindow.cxx
> StatusWindow.cxx
> WidgetWindow.cxx
> WriteCode.cxx
> Linking...
> LINK : warning LNK4098: defaultlib "LIBCMT" conflicts with use of
> other libs; use /NODEFAULTLIB:library
>
> pGuide.exe - 0 error(s), 1 warning(s)
>
> I don't know what to do about that warning, sorry. But from experience
> it is harmless. Unfortunately Microsoft does not tell you what
> conflicts with what, only that there is a conflict. BTW I get the same
> with a few other PLIB projects as well.

It is usually due to different code generation modes among the various parts of
an application (libraries, the app itself) - in the case of a Release
Configuration, these are, namely, Single Threaded, Multithreaded, and
Multithreaded DLL. So the reccomendation is to unify all to the same code
generation model, typically Multithreaded or Multithreaded DLL (which is
probably the current mode for Plib, not sure yet).

This is a positive end case since in similar cases the link phase gives up with
error.

In this case just try to put LIBCMT.lib in Project settings -> Link tab ->
Category: Input -> Ignore libraries input field, or put libc.lib instead.

Greetings -

Paolo Leoncini