Re: [Wxlua-users] Re: [Wxart2d-users_dev] cmake MSVC 7 compilation woes

[k. h. <kla...@nl...>]

Hi All,

John Labenski wrote:

>at wxWidgets/build/msw/makefile.vc, search for "/M" and you see that
>it uses all sorts of variables to store them. Look also at
>build/msw/config.vc and samples/minimal/makefile.vc.
>  
>
Whooo, i searched for __RUNTIME_LIBS_ and it is enormous, i wonder if 
the eventual setting is different all the time.

>I'm not sure the best way to do this, we need to get wxLua built
>identically to wxWidgets, and in your case with the wxArt2D library. I
>would have thought that bakefile was supposed to have "fixed" this,
>but I never saw how it could work unless the end users bakefiles (our
>bakefiles) used all the internal variables of the wxWidgets bakefiles.
>I fought about that a few times on wx-dev, but I couldn't seem to get
>the seriousness of this problem across.
>  
>
I can't judge it. But searched for NODEFAULT, it  is not found. So 
where  does that one come from?

Compiling wxLua without  setting the switch  results in a warning, so 
maybe someone just added it to get rid of it.

LINK : warning LNK4098: defaultlib "MSVCRT" conflicts with use of other 
libs; use /NODEFAULTLIB:library

And looking at a few of the results of the Searching Libraries flag 
(/VERBOSE:LIB):

    Searching \data\art2d\wxluacvs\wxLua\lib\vc_lib\wxluasocket.lib:
    ====>>Searching C:\Program Files\Microsoft Visual 
Studio\vc98\LIB\MSVCRTD.lib:
    Searching C:\Program Files\Microsoft Visual 
Studio\vc98\LIB\OLDNAMES.lib:
    ====>>Searching C:\Program Files\Microsoft Visual 
Studio\vc98\LIB\MSVCRT.lib:
 
I do understand that this must be a conflict.
But why are those two libraries loaded?? Can one say it is 
wxluasocket.lib causing this?

>  
>
> I read those messages, bakefile doesn't seem to be right. Take a look

I see that it is confusing, i can't say they are not right.
We first need to figure out why the two conflicting libraries are 
searched for.
I looked at it (wxlua.exe) with the tool "depends", but that does not 
help much.

Someone has an idea on how to find the reason behind loading the two 
conflicting libs?

Regards,

Klaas



-- 
Unclassified