Re: [Wxlua-users] Re: MSVC6 warning for /Fd switch in release multilib

[John L. <jla...@gm...>]

On 4/1/06, Francesco Montorsi <f18...@ya...> wrote:
> John Labenski ha scritto:
> > --------------------Configuration: mod_lua - Win32 Release
> > Multilib--------------------
> > Compiling...
> > Command line warning D4025 : overriding '/Fdmsvc6prj\mod_lua/' with
> > '/Fd..\..\..\bin\wxlua-lua.pdb'
> > lua.c
> > Linking...
> >
> > Here's the ./modules/build/msw/modules_mod_lua.dsp file for the warning=
.
> >
> > !ELSEIF  "$(CFG)" =3D=3D "mod_lua - Win32 Release Multilib"
> >
> > # PROP BASE Use_MFC 0
> > # PROP BASE Use_Debug_Libraries 0
> > # PROP BASE Output_Dir "..\..\..\bin"
> > # PROP BASE Intermediate_Dir "msvc6prj\mod_lua"
> > # PROP BASE Target_Dir ""
> > # PROP Use_MFC 0
> > # PROP Use_Debug_Libraries 0
> > # PROP Output_Dir "..\..\..\bin"
> > # PROP Intermediate_Dir "msvc6prj\mod_lua"
> > # PROP Target_Dir ""
> > # ADD BASE CPP /nologo /FD /MD /GR /EHsc /w /O2 /I "..\..\lua\include"
> > /Fd..\..\..\bin\wxlua-lua.pdb /D "WIN32" /D "_CONSOLE" /c
> > # ADD CPP /nologo /FD /MD /GR /EHsc /w /O2 /I "..\..\lua\include"
> > /Fd..\..\..\bin\wxlua-lua.pdb /D "WIN32" /D "_CONSOLE" /c
> > # ADD BASE RSC /l 0x409 /d "_CONSOLE" /i ..\..\lua\include
> > # ADD RSC /l 0x409 /d "_CONSOLE" /i ..\..\lua\include
> > BSC32=3Dbscmake.exe
> > # ADD BASE BSC32 /nologo
> > # ADD BSC32 /nologo
> > LINK32=3Dlink.exe
> > # ADD BASE LINK32 ..\..\..\lib\vc_lib\wxlua_msw26_lua.lib /nologo
> > /machine:i386 /out:"..\..\..\bin\wxlua-lua.exe" /subsystem:console
> > # ADD LINK32 ..\..\..\lib\vc_lib\wxlua_msw26_lua.lib /nologo
> > /machine:i386 /out:"..\..\..\bin\wxlua-lua.exe" /subsystem:console
> >
> > I guess it doesn't like that the "Intermediate_Dir" is not the same as
> > where the pdb file goes? Maybe the /Fd should also use
> > "msvc6prj\mod_lua"?
> I think it is because cl is being called with two /Fd options with
> different folders and it warns the user that only the last one will take
> effect...
>
> >
> > Any ideas?
> I'll look at this as soon as I'll get my hands on a win32 installation;
> however it will take a week at least probably - but this shouldn't be a
> big priority problem, right ?

No, it seems to work just fine, just a warning.

Thanks,
    John Labenski