wxcode-users

[wxCode-users] Bakefile issues

[Jaakko S. <jaa...@pp...>]

Hi all,

I'm compiling a component for wxWidgets 2.7.0,
and it seems that bakefile-generated makefiles
are not generated correctly for it. In the
resulting makefile.vc, for instance, I would
need to manually adjust WX_VERSION to 27 before
it builds. I did double-check that my WXWIN was
set to directory with correct wxWidgets version.

Also, can anyone tell me why makefile command-
line uses different symbols than when building
wxWidgets itself? Atleast for makefile.vc, I
need to specify WX_DEBUG=1 instead of DEBUG=1,
and so forth.

Thanks,
  Jaakko Salli

Re: [wxCode-users] Bakefile issues

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

Jaakko Salli ha scritto:
> Hi all,
Hi,
    just back from holidays so, sorry for the delay.


> 
> I'm compiling a component for wxWidgets 2.7.0,
> and it seems that bakefile-generated makefiles
> are not generated correctly for it. In the
> resulting makefile.vc, for instance, I would
> need to manually adjust WX_VERSION to 27 before
> it builds.
you can fix this using:

  <set var="WX_VERSION_DEFAULT">27</set>

just after

  <include file="$(WXCODE_BAKEFILEDIR)/defaults.bkl"/>


> I did double-check that my WXWIN was
> set to directory with correct wxWidgets version.
makefile.vc is not able to understand the wx version from the location 
of wxWidgets (like all other formats except autoconf); so it needs 
WX_VERSION to be correctly set.

> Also, can anyone tell me why makefile command-
> line uses different symbols than when building
> wxWidgets itself? Atleast for makefile.vc, I
> need to specify WX_DEBUG=1 instead of DEBUG=1,
> and so forth.
This is a known "problem". the logic behind this is acceptable for a 
generic wx-based application: you want wxWidgets-specific settings to be 
separed from the app-specific settings. This is why I've never asked 
Vaclav to change these names in wx presets.

OTOH, since WX_UNICODE and WX_DEBUG must be always set to the same 
values of the app's own unicode and debug options (otherwise you'll get 
linking errors), I tried to make it possible to rename from a bakefile 
an option defined in another bakefile.
I managed to allow it in a transparent way. But the patch which does 
that 
(http://sourceforge.net/tracker/index.php?func=detail&aid=1363938&group_id=83016&atid=568031) 
lies in the patch tracker...

Francesco

Re: [wxCode-users] Bakefile issues

[Jaakko S. <jaa...@pp...>]

Francesco Montorsi wrote:
>> I'm compiling a component for wxWidgets 2.7.0,
>> and it seems that bakefile-generated makefiles
>> are not generated correctly for it. In the
>> resulting makefile.vc, for instance, I would
>> need to manually adjust WX_VERSION to 27 before
>> it builds.
>>     
> you can fix this using:
>
>   <set var="WX_VERSION_DEFAULT">27</set>
>
> just after
>
>   <include file="$(WXCODE_BAKEFILEDIR)/defaults.bkl"/>
>   
That didn't work, but <set var="WX_VERSION">27</set>
seemed to do the trick instead.

Also, I'm getting following error message, with wxWidgets
2.7.0 only, even now with the version set:

[6/6] generating autoconf from mycomp.bkl
...\wxCode\build\bakefiles\wxhacks.bkl:53: error: option 'WX_DIR' 
already defined
    included from ...\wxCode\build\bakefiles\defaults.bkl:87
    included from ...\wxCode\components\mycomp\build\mycomp.bkl:7
[bakefile_gen] error: bakefile exited with error

>> Also, can anyone tell me why makefile command-
>> line uses different symbols than when building
>> wxWidgets itself? Atleast for makefile.vc, I
>> need to specify WX_DEBUG=1 instead of DEBUG=1,
>> and so forth.
>>     
> This is a known "problem". the logic behind this is acceptable for a 
> generic wx-based application: you want wxWidgets-specific settings to be 
> separed from the app-specific settings. This is why I've never asked 
> Vaclav to change these names in wx presets.
>
> OTOH, since WX_UNICODE and WX_DEBUG must be always set to the same 
> values of the app's own unicode and debug options (otherwise you'll get 
> linking errors), I tried to make it possible to rename from a bakefile 
> an option defined in another bakefile.
> I managed to allow it in a transparent way. But the patch which does 
> that 
> (http://sourceforge.net/tracker/index.php?func=detail&aid=1363938&group_id=83016&atid=568031) 
> lies in the patch tracker...
>   
Ok, thanks for explaining it.

Regards,
  Jaakko Salli

Re: [wxCode-users] Bakefile issues

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

Jaakko Salli ha scritto:
> Francesco Montorsi wrote:
>>> I'm compiling a component for wxWidgets 2.7.0,
>>> and it seems that bakefile-generated makefiles
>>> are not generated correctly for it. In the
>>> resulting makefile.vc, for instance, I would
>>> need to manually adjust WX_VERSION to 27 before
>>> it builds.
>>>     
>> you can fix this using:
>>
>>   <set var="WX_VERSION_DEFAULT">27</set>
>>
>> just after
>>
>>   <include file="$(WXCODE_BAKEFILEDIR)/defaults.bkl"/>
>>   
> That didn't work, but <set var="WX_VERSION">27</set>
> seemed to do the trick instead.
strange - need to look into this later.


> Also, I'm getting following error message, with wxWidgets
> 2.7.0 only, even now with the version set:
> 
> [6/6] generating autoconf from mycomp.bkl
> ...\wxCode\build\bakefiles\wxhacks.bkl:53: error: option 'WX_DIR' 
> already defined
>     included from ...\wxCode\build\bakefiles\defaults.bkl:87
>     included from ...\wxCode\components\mycomp\build\mycomp.bkl:7
> [bakefile_gen] error: bakefile exited with error
I've checked in a little fix for that; it should work now.

Francesco

Re: [wxCode-users] Bakefile issues

[Jaakko S. <jaa...@pp...>]

Francesco Montorsi wrote:
> Jaakko Salli ha scritto:
>   
>> Francesco Montorsi wrote:
>>     
>>>> I'm compiling a component for wxWidgets 2.7.0,
>>>> and it seems that bakefile-generated makefiles
>>>> are not generated correctly for it. In the
>>>> resulting makefile.vc, for instance, I would
>>>> need to manually adjust WX_VERSION to 27 before
>>>> it builds.
>>>>     
>>>>         
>>> you can fix this using:
>>>
>>>   <set var="WX_VERSION_DEFAULT">27</set>
>>>
>>> just after
>>>
>>>   <include file="$(WXCODE_BAKEFILEDIR)/defaults.bkl"/>
>>>   
>>>       
>> That didn't work, but <set var="WX_VERSION">27</set>
>> seemed to do the trick instead.
>>     
> strange - need to look into this later.
>   
If its any help, <set var="WX_VERSION_DEFAULT">27</set>
only worked for me if it was placed before the include
line, and the default value was commented out in
defaults.bkl.

>> Also, I'm getting following error message, with wxWidgets
>> 2.7.0 only, even now with the version set:
>>
>> [6/6] generating autoconf from mycomp.bkl
>> ...\wxCode\build\bakefiles\wxhacks.bkl:53: error: option 'WX_DIR' 
>> already defined
>>     included from ...\wxCode\build\bakefiles\defaults.bkl:87
>>     included from ...\wxCode\components\mycomp\build\mycomp.bkl:7
>> [bakefile_gen] error: bakefile exited with error
>>     
> I've checked in a little fix for that; it should work now.
>   
Indeed it does.

Thanks,
  Jaakko