Re: [wxCode-users] bakefile gdiplus lib

[Francesco M. <f18...@ya...>]

Hi John, Klaas,

John Labenski ha scritto:
> I don't see how to automatically test for this, but we could add a 
> condition USE_GDIPLUS as wxWidgets does. Francesco, do you think this 
> would work?
> 
...
> Put this after the line "<sys-lib>odbc32</sys-lib>" in wx.blk
> <sys-lib>$(GDIPLUS_LIB)</sys-lib>
> 
> ============================================
> So I tried puttting this into wxCode's wx_win32.bkl and the output code 
> looks ok, but it's not tested. The dsp and vcproj are unchanged, but the 
> makefile.vc <http://makefile.vc> should work.
I think it should just be fine. I think that in fact we have no changes we need 
to preserve in wxCode wxpresets bakefiles respect official wxpresets. We keep a 
copy there just to facilitate baking for wxCode maintainers...
so that probably we can just overwrite wxCode's wxpresets with wx2.8.10 
wxpresets...


>     A second bakefile related problem is that building debug and release of
>     wxstedit, both result in the same library name:
>     wcode_msw28_stedit
> 
>     But for debug it should generate:
> 
>     wcode_msw28d_stedit
> 
> 
> I have rebaked the wxstedit build files in CVS and I see that the dsp 
> files put a 'd' in for debug so I assume that the makefile.vc 
> <http://makefile.vc> should too.
Looking at the makefile.vc I see that the lib target is called:

..\lib\vc_$(____stedit_lib__DIRNAME_SHARED_SUFFIX_FILENAMES)\wxcode_msw$(WX_VERSION)$(WXLIBPOSTFIX)_stedit.lib

and WXLIBPOSTFIX seems to be set correctly (i.e. contains 'u' and 'd' flags when 
required) so that I think everything is ok.

Bye,
Francesco