wxcode-users — Submission, Questions, Information

Re: [wxCode-users] IMPORTANT: New bakefile build system

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

Hi,

John Labenski ha scritto:
> Great, is there a component (of yours) that is updated to compare to?
yes: in the SVN repo of wxCode (where I keep all my components) there 
are the components:

    KEYBINDER => simple sample of a self-contained component with 1 
lib/dll and 1 sample

    WXXML2 => more complex bakefile which handles building two 
dependencies (libxml2 and libiconv) which are stored in wxxml2\thirdparty

    WXEXTMINIFRAME => example of a library with a sample which however 
requires different set of sources for different wx ports used

    WEBUPDATE => much more complex than previous ones - I don't suggest 
to look at it

All the above ones have been updated - I need to update yet WXSCRIPT 
however...

Francesco

Re: [wxCode-users] Using <wxlike-libname> libraries in Bakefile.

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

Hi,
     please try to update your bakefile as described in "IMPORTANT: new 
bakefile build system" mail and retry. It should then work.

Francesco




Matías Szeftel ha scritto:
> Francesco Montorsi escribió:
>> Matías Szeftel ha scritto:
>>   
>>> I've just downloaded the 2.2 version of bakefile. And I can't create
>>> msvc2005 projects.
>>>     
>> seems strange, it works fine for many other projects I have baked...
>>
>>   
> 
> This is the output I get:
> 
> [1/5] generating msvs2005prj from centro_salud.bkl
> WARNING: Arbitrary commands are not implemented for project files.
> ...
> //many times
> ...
> WARNING: Arbitrary commands are not implemented for project files.
> E:\Disco Backup\BACKUP (D)\Proyectos\build\bakefiles\targets.bkl:60:
> error: unknown template '__phony'
>     included from E:\Disco Backup\BACKUP
> (D)\Proyectos\build\bakefiles\wxcode.bkl:19
>     included from E:\Disco Backup\BACKUP
> (D)\Proyectos\CentroSalud-SVN\build\centro_salud.bkl:52
> [bakefile_gen] error: bakefile exited with error
> 
> And this is my bakefile file, nothing special:
> 
> <?xml version="1.0" ?>
> 
> <!-- RCS-ID: $Id: centro_salud.bkl,v 1.5 2007/01/08 11:05:34 mszeftel
> Exp $ -->
> 
> <makefile>
>    
>     <!-- Set the defaults for the variables used by wxCode bakefiles -->
>     <set var="WXCODE_BAKEFILEDIR">../../build/bakefiles</set>
>     <include file="$(WXCODE_BAKEFILEDIR)/defaults.bkl"/>
>    
>     <!--
> ================================================================= -->
>     <!-- Settings for this
> component                                       -->
>     <!--
> ================================================================= -->
> 
>     <!--
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>         Set the name of the folder which contains this component and thus
>         should always be in lowercase, wxCode/component/MYCOMPONENT_NAME -->
>     <set var="COMP_NAME">CentroSalud</set>
> 
> 
>     <!--
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
>     <!-- Library file
> settings                                             -->
>     <!--
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
> 
>     <!-- COMP_SRC lists the component's sources with path relative to
> ../src -->
>     <set var="COMP_SRC">
>         ../src/PrincipalFrm.cpp
>         ../src/PrincipalFrmApp.cpp
>         ../src/MaestroFrm.cpp
>         ../src/MaestroAnalistas.cpp
>         ../src/MaestroPacientes.cpp
>         ../src/AnalistasListCtrl.cpp
>         ../src/PacientesListCtrl.cpp
>         ../src/CajaPanel.cpp
>         ../src/CajaListCtrl.cpp
>     </set>
>     <!-- COMP_HDR lists the component's headers with path relative to
> ../include -->
>     <set var="COMP_HDR">
>         ../include/PrincipalFrm.h
>         ../include/PrincipalFrmApp.h
>         ../include/MaestroFrm.h
>         ../include/MaestroAnalistas.h
>         ../include/MaestroPacientes.h
>         ../include/AnalistasListCtrl.h
>         ../include/PacientesListCtrl.h
>         ../include/CajaPanel.h
>         ../include/CajaListCtrl.h
>     </set>
> 
>     <!--
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
>     <!-- Include the wxCode bakefile after defining the COMP_XXXX
> vars...  -->
>     <include file="$(WXCODE_BAKEFILEDIR)/wxcode.bkl"/>
> 
> 
>     <exe id="CentroSalud" template="compsample">
>         <res-include>../src</res-include>
>         <win32-res>../src/CentroSalud.rc</win32-res>
> 
>         <sources>$(COMP_SRC)</sources>
>         <headers>$(COMP_HDR)</headers>
> 
> 
>         <wx-lib>xml</wx-lib>
>         <wx-lib>core</wx-lib>
>         <wx-lib>base</wx-lib> <!-- base must be last wx-lib -->
>     </exe>
> 
>  </makefile>
> 
> I might be missing something, but it works ok with the other formats.
> 
> Regards, Matías
> 
> 	
> 
> 	
> 		
> __________________________________________________ 
> Preguntá. Respondé. Descubrí. 
> Todo lo que querías saber, y lo que ni imaginabas, 
> está en Yahoo! Respuestas (Beta). 
> ¡Probalo ya! 
> http://www.yahoo.com.ar/respuestas 
> 
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

Re: [wxCode-users] IMPORTANT: New bakefile build system

[<msz...@ya...>]

Francesco Montorsi escribió:
> 4) substitute "complib" with "wxcode-lib" and "compdll" with 
> "wxcode-dll" templates.
>
> 5) don't use <exe></exe> tag for your wxCode samples; instead replace 
> them with <wxcode-sample>
>
>   
What about non-libs projects (programs like wxARG :) )?
Should I keep using <exe>? Any new templates?

Thanx for the commit, I will try it tonight if I can.

Regards, Matías.

	

	
		
__________________________________________________ 
Preguntá. Respondé. Descubrí. 
Todo lo que querías saber, y lo que ni imaginabas, 
está en Yahoo! Respuestas (Beta). 
¡Probalo ya! 
http://www.yahoo.com.ar/respuestas 

Re: [wxCode-users] IMPORTANT: New bakefile build system

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

Great, is there a component (of yours) that is updated to compare to?

Thanks,
    John Labenski

On 3/2/07, Francesco Montorsi <f18...@ya...> wrote:
> Hi all,
>
>      I've just committed to the wxCode CVS repo a new set of bakefiles
> which should make the build systems of wxCode components more reliable
> and much more easier to maintain (thanks to cleaner .bkl files).
>
> Please see the "wxCode bakefile changes" thread for more info (I've
> managed to workaround the problem about the msvs2005prj and msvc6prj
> formats there mentioned).
>
> In short these changes will:
>   - make easier for your users to compile your project (better error
> messages) and to match them to a wxWidgets build
>
>   - allow your project to be built in various build modes without
> conflicts (e.g. you'll be able to build a Unicode and ANSI version of
> your libraries as they will be named differently -- just as wxWidgets
> itself does). This means that libraries generated by your wxcode
> projects will be named e.g. libwxcode_gtk2d_keybinder-2.9.a and will go
> (on Windows) in a subfolder of "lib" created by the makefile: vc_lib,
> vc_dll, gcc_lib etc.
>
>   - allow your project to have .SLN and .VCPROJ generated next to the
> .DSW and .DSP ones (for MSVC 2005)
>
>   - allow your project to use "gnu" format instead of "autoconf" (which
> has the "trouble" of requiring additional config.sub, config.guess,
> configure.ac files, and require you to use aclocal & autoconf).
> Now "gnu" format works just fine with wx and basically will be the
> equivalent of makefile.vc|bcc|gcc|wat for Unix.
>
> The following mail describe the required changes to the
>   - .bkl
>   - configure.ac
>   - Bakefiles.bkgen
> files of your projects.
>
> For an example see the following diffs:
>
>
>
> =============== CHANGES TO THE .bkl FILE
>
> Example diff for a typical wxCode bakefile:
> http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/keybinder/build/keybinder.bkl?r1=346&r2=437
>
> 1) remove old <include> statements and add this at the beginning:
>
>       <include file="presets/wxcode.bkl"/>
>
> 2) replace <set var="COMP_NAME">yourCompName</set> with:
>
>       <set-comp-name>yourCompName</set-comp-name>
>
> 3) remove all other <set var="COMP_*"> statements: in particular you
> won't need anymore the _SRC and _HDR COMP variables as Bakefile will now
> detect all the .CPP and .H of your project automatically.
> This is a big enhancement as you now won't need anymore to keep such
> ugly lists in your bakefile and update them whenever you add/remove a
> source/header file from your project.
>
> 4) substitute "complib" with "wxcode-lib" and "compdll" with
> "wxcode-dll" templates.
>
> 5) don't use <exe></exe> tag for your wxCode samples; instead replace
> them with <wxcode-sample>
>
> 6) replace the <win32-res> and <res-include> from your wxCode samples with
>
>      <dir>directory_of_your_sample_project</dir>
>      <has-win32-res/>
>
> where the first tag needs the path to the directory containing the
> sample project relatively to the location of the bakefile and the second
> tag needs to be present only if you have a .rc file in that directory.
>
>
> ============ CHANGES TO THE Bakefiles.bkgen
>
> Example diff:
> http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/keybinder/build/Bakefiles.bkgen?r1=436&r2=HEAD
>
> 1) simply remove all contents inside <bakefile-gen> tag except for the
> <input> tag ;)
>
> 2) add a
>
> <include file="../../../build/bakefiles/presets/wxcode.bkgen"/>
>
> line before the <input> tag.
>
> Typically your Bakefiles.bkgen will become as simple as:
>
> <?xml version="1.0" ?>
> <bakefile-gen>
>      <include file="../../../build/bakefiles/presets/wxcode.bkgen"/>
>      <input>keybinder.bkl</input>
> </bakefile-gen>
>
>
>
> ============ CHANGES TO THE configure.ac
>
> Example diff:
> http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/keybinder/build/configure.ac?r1=346&r2=437
>
> 1) replace AM_WXCODE_INIT with WXCODE_INIT
> 2) replace AM_OPTIONS_WXCONFIG and AM_OPTIONS_WXPRESETS macros with a
> call to WXCODE_OPTIONS([debug,unicode,shared,toolkit,wxshared,wxversion])
>
> if you don't want e.g. the --with-toolkit=gtk|mac|msw|etc option, you
> can remove the "toolkit" option from the call to WXCODE_OPTIONS.
> Other options are very useful and should be left.
>
> 3) replace AM_WXCODE_CHECKS([2.8.0]) with
>      WXCODE_CHECKS([2.8.0], [core,base])
>
> where 2.8.0 is the minimal required wxWidgets version and core,base is
> the list of the wxWidgets libraries required by your project (base
> should always be present).
>
> 4) replace AM_WXCODE_END with WXCODE_END
>
>
> Please mail on _this_ mailing list for any doubt/problem so that anyone
> can see the reply ;)
>
> Francesco
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

[wxCode-users] IMPORTANT: New bakefile build system

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

Hi all,

     I've just committed to the wxCode CVS repo a new set of bakefiles
which should make the build systems of wxCode components more reliable
and much more easier to maintain (thanks to cleaner .bkl files).

Please see the "wxCode bakefile changes" thread for more info (I've
managed to workaround the problem about the msvs2005prj and msvc6prj
formats there mentioned).

In short these changes will:
  - make easier for your users to compile your project (better error 
messages) and to match them to a wxWidgets build

  - allow your project to be built in various build modes without 
conflicts (e.g. you'll be able to build a Unicode and ANSI version of 
your libraries as they will be named differently -- just as wxWidgets 
itself does). This means that libraries generated by your wxcode 
projects will be named e.g. libwxcode_gtk2d_keybinder-2.9.a and will go 
(on Windows) in a subfolder of "lib" created by the makefile: vc_lib, 
vc_dll, gcc_lib etc.

  - allow your project to have .SLN and .VCPROJ generated next to the 
.DSW and .DSP ones (for MSVC 2005)

  - allow your project to use "gnu" format instead of "autoconf" (which 
has the "trouble" of requiring additional config.sub, config.guess, 
configure.ac files, and require you to use aclocal & autoconf).
Now "gnu" format works just fine with wx and basically will be the 
equivalent of makefile.vc|bcc|gcc|wat for Unix.

The following mail describe the required changes to the
  - .bkl
  - configure.ac
  - Bakefiles.bkgen
files of your projects.

For an example see the following diffs:



=============== CHANGES TO THE .bkl FILE

Example diff for a typical wxCode bakefile:
http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/keybinder/build/keybinder.bkl?r1=346&r2=437

1) remove old <include> statements and add this at the beginning:

      <include file="presets/wxcode.bkl"/>

2) replace <set var="COMP_NAME">yourCompName</set> with:

      <set-comp-name>yourCompName</set-comp-name>

3) remove all other <set var="COMP_*"> statements: in particular you 
won't need anymore the _SRC and _HDR COMP variables as Bakefile will now 
detect all the .CPP and .H of your project automatically.
This is a big enhancement as you now won't need anymore to keep such 
ugly lists in your bakefile and update them whenever you add/remove a 
source/header file from your project.

4) substitute "complib" with "wxcode-lib" and "compdll" with 
"wxcode-dll" templates.

5) don't use <exe></exe> tag for your wxCode samples; instead replace 
them with <wxcode-sample>

6) replace the <win32-res> and <res-include> from your wxCode samples with

     <dir>directory_of_your_sample_project</dir>
     <has-win32-res/>

where the first tag needs the path to the directory containing the 
sample project relatively to the location of the bakefile and the second 
tag needs to be present only if you have a .rc file in that directory.


============ CHANGES TO THE Bakefiles.bkgen

Example diff:
http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/keybinder/build/Bakefiles.bkgen?r1=436&r2=HEAD

1) simply remove all contents inside <bakefile-gen> tag except for the 
<input> tag ;)

2) add a

<include file="../../../build/bakefiles/presets/wxcode.bkgen"/>

line before the <input> tag.

Typically your Bakefiles.bkgen will become as simple as:

<?xml version="1.0" ?>
<bakefile-gen>
     <include file="../../../build/bakefiles/presets/wxcode.bkgen"/>
     <input>keybinder.bkl</input>
</bakefile-gen>



============ CHANGES TO THE configure.ac

Example diff:
http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/keybinder/build/configure.ac?r1=346&r2=437

1) replace AM_WXCODE_INIT with WXCODE_INIT
2) replace AM_OPTIONS_WXCONFIG and AM_OPTIONS_WXPRESETS macros with a 
call to WXCODE_OPTIONS([debug,unicode,shared,toolkit,wxshared,wxversion])

if you don't want e.g. the --with-toolkit=gtk|mac|msw|etc option, you 
can remove the "toolkit" option from the call to WXCODE_OPTIONS.
Other options are very useful and should be left.

3) replace AM_WXCODE_CHECKS([2.8.0]) with
     WXCODE_CHECKS([2.8.0], [core,base])

where 2.8.0 is the minimal required wxWidgets version and core,base is 
the list of the wxWidgets libraries required by your project (base 
should always be present).

4) replace AM_WXCODE_END with WXCODE_END


Please mail on _this_ mailing list for any doubt/problem so that anyone 
can see the reply ;)

Francesco

Re: [wxCode-users] Using <wxlike-libname> libraries in Bakefile.

[<msz...@ya...>]

Francesco Montorsi escribió:
> Matías Szeftel ha scritto:
>   
>> I've just downloaded the 2.2 version of bakefile. And I can't create
>> msvc2005 projects.
>>     
> seems strange, it works fine for many other projects I have baked...
>
>   

This is the output I get:

[1/5] generating msvs2005prj from centro_salud.bkl
WARNING: Arbitrary commands are not implemented for project files.
...
//many times
...
WARNING: Arbitrary commands are not implemented for project files.
E:\Disco Backup\BACKUP (D)\Proyectos\build\bakefiles\targets.bkl:60:
error: unknown template '__phony'
    included from E:\Disco Backup\BACKUP
(D)\Proyectos\build\bakefiles\wxcode.bkl:19
    included from E:\Disco Backup\BACKUP
(D)\Proyectos\CentroSalud-SVN\build\centro_salud.bkl:52
[bakefile_gen] error: bakefile exited with error

And this is my bakefile file, nothing special:

<?xml version="1.0" ?>

<!-- RCS-ID: $Id: centro_salud.bkl,v 1.5 2007/01/08 11:05:34 mszeftel
Exp $ -->

<makefile>
   
    <!-- Set the defaults for the variables used by wxCode bakefiles -->
    <set var="WXCODE_BAKEFILEDIR">../../build/bakefiles</set>
    <include file="$(WXCODE_BAKEFILEDIR)/defaults.bkl"/>
   
    <!--
================================================================= -->
    <!-- Settings for this
component                                       -->
    <!--
================================================================= -->

    <!--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Set the name of the folder which contains this component and thus
        should always be in lowercase, wxCode/component/MYCOMPONENT_NAME -->
    <set var="COMP_NAME">CentroSalud</set>


    <!--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <!-- Library file
settings                                             -->
    <!--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->

    <!-- COMP_SRC lists the component's sources with path relative to
../src -->
    <set var="COMP_SRC">
        ../src/PrincipalFrm.cpp
        ../src/PrincipalFrmApp.cpp
        ../src/MaestroFrm.cpp
        ../src/MaestroAnalistas.cpp
        ../src/MaestroPacientes.cpp
        ../src/AnalistasListCtrl.cpp
        ../src/PacientesListCtrl.cpp
        ../src/CajaPanel.cpp
        ../src/CajaListCtrl.cpp
    </set>
    <!-- COMP_HDR lists the component's headers with path relative to
../include -->
    <set var="COMP_HDR">
        ../include/PrincipalFrm.h
        ../include/PrincipalFrmApp.h
        ../include/MaestroFrm.h
        ../include/MaestroAnalistas.h
        ../include/MaestroPacientes.h
        ../include/AnalistasListCtrl.h
        ../include/PacientesListCtrl.h
        ../include/CajaPanel.h
        ../include/CajaListCtrl.h
    </set>

    <!--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <!-- Include the wxCode bakefile after defining the COMP_XXXX
vars...  -->
    <include file="$(WXCODE_BAKEFILEDIR)/wxcode.bkl"/>


    <exe id="CentroSalud" template="compsample">
        <res-include>../src</res-include>
        <win32-res>../src/CentroSalud.rc</win32-res>

        <sources>$(COMP_SRC)</sources>
        <headers>$(COMP_HDR)</headers>


        <wx-lib>xml</wx-lib>
        <wx-lib>core</wx-lib>
        <wx-lib>base</wx-lib> <!-- base must be last wx-lib -->
    </exe>

 </makefile>

I might be missing something, but it works ok with the other formats.

Regards, Matías

	

	
		
__________________________________________________ 
Preguntá. Respondé. Descubrí. 
Todo lo que querías saber, y lo que ni imaginabas, 
está en Yahoo! Respuestas (Beta). 
¡Probalo ya! 
http://www.yahoo.com.ar/respuestas 

Re: [wxCode-users] wxCode problems and wxWPM (was Re: Announcing wxWPM 0.2: wxWidgets Package Manager)

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

cecilio ha scritto:
> Hi Francesco,
> 
> I have detected a problem in the wxCode component page for my
> component wxMIdi. Probably the bug is also in other pages but I didn't
> check. The problem is that I moved my component time ago to SVN. But
> in the component page there is still a 'Browse CVS' link pointing to
> obsolete code at CVS, and there is not a 'Browse SVN' link pointing to
> updated code. So please, I would appreciate if the CVS code could be
> deleted and the 'browse CVS' links updated to point to SVN.

This is a known issue, sorry.

I'll fix it ASAP together with some changes to wxCode structure.

I'd only like to get some feedback on the "wxCode problems and wxWPM" 
thread before going on the changes...

Francesco

Re: [wxCode-users] Using <wxlike-libname> libraries in Bakefile.

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

Matías Szeftel ha scritto:
> Francesco Montorsi escribió:
>> Matías Szeftel ha scritto:
>>   
>>> Hi! Joseph has change to the <wxlike-libname> for the DatabaseLayer libraries 
>>> naming. This is a good feature I belieave, but how do I point to this 
>>> libraries from inside my bakefile (wxarg.bkl).
>>>
>>> I've been using <sys-lib> for now but this doesn't work now 
>>> (obviously ... :) ).
>>>     
>> in the new bakefile framework there will be a <wxlike-lib> tag which will act 
>> like <sys-lib> just for libs following wx rule naming ;)
>>
>>   
> Great! The bakefile framework you say, are the presets for wxWidgets and
> wxCode?
right


> Will it have 2.8.0 version as default?
yes


> I've just downloaded the 2.2 version of bakefile. And I can't create
> msvc2005 projects.
seems strange, it works fine for many other projects I have baked...

> Is this the bug you have to fix?
no, it's a bug described on the bakefile mailing list (see thread 
"endless loop while reordering tags"). I've found the cause of the bug 
but unfortunately it's not clear to me how to fix it... I'm waiting 
Vaclav's opinion on it.

Francesco

Re: [wxCode-users] wxCode problems and wxWPM (was Re: Announcing wxWPM 0.2: wxWidgets Package Manager)

[cecilio <s.c...@gm...>]

Hi Francesco,

I have detected a problem in the wxCode component page for my
component wxMIdi. Probably the bug is also in other pages but I didn't
check. The problem is that I moved my component time ago to SVN. But
in the component page there is still a 'Browse CVS' link pointing to
obsolete code at CVS, and there is not a 'Browse SVN' link pointing to
updated code. So please, I would appreciate if the CVS code could be
deleted and the 'browse CVS' links updated to point to SVN.

Thank you.
Regards,
Cecilio

Re: [wxCode-users] Using <wxlike-libname> libraries in Bakefile.

[<msz...@ya...>]

Francesco Montorsi escribió:
> Matías Szeftel ha scritto:
>   
>> Hi! Joseph has change to the <wxlike-libname> for the DatabaseLayer libraries 
>> naming. This is a good feature I belieave, but how do I point to this 
>> libraries from inside my bakefile (wxarg.bkl).
>>
>> I've been using <sys-lib> for now but this doesn't work now 
>> (obviously ... :) ).
>>     
> in the new bakefile framework there will be a <wxlike-lib> tag which will act 
> like <sys-lib> just for libs following wx rule naming ;)
>
>   
Great! The bakefile framework you say, are the presets for wxWidgets and
wxCode?
Will it have 2.8.0 version as default?

>> Btw, any idea when the new wx bakefile stuff will be ready?
>>     
> as soon as I manage to fix a nasty bug I've found.
> The best thing would be to find a workaround for it since bakefile 0.2.3 is far 
> anyway and until then you'd require to patch your installation of bakefile if I 
> commit my bakefile changes...
>
>
>   
>> Should I wait for this to make my source release?
>>     
> possibly yes. I'll try to look again at that bug tonight.
>
> Francesco
>
>   

I've just downloaded the 2.2 version of bakefile. And I can't create
msvc2005 projects. Is this the bug you have to fix?

Thanks for all.

Regards, Matías.




	

	
		
__________________________________________________ 
Preguntá. Respondé. Descubrí. 
Todo lo que querías saber, y lo que ni imaginabas, 
está en Yahoo! Respuestas (Beta). 
¡Probalo ya! 
http://www.yahoo.com.ar/respuestas 

Re: [wxCode-users] Using <wxlike-libname> libraries in Bakefile.

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

Matías Szeftel ha scritto:
> Hi! Joseph has change to the <wxlike-libname> for the DatabaseLayer libraries 
> naming. This is a good feature I belieave, but how do I point to this 
> libraries from inside my bakefile (wxarg.bkl).
> 
> I've been using <sys-lib> for now but this doesn't work now 
> (obviously ... :) ).
in the new bakefile framework there will be a <wxlike-lib> tag which will act 
like <sys-lib> just for libs following wx rule naming ;)


> Btw, any idea when the new wx bakefile stuff will be ready?
as soon as I manage to fix a nasty bug I've found.
The best thing would be to find a workaround for it since bakefile 0.2.3 is far 
anyway and until then you'd require to patch your installation of bakefile if I 
commit my bakefile changes...


> Should I wait for this to make my source release?
possibly yes. I'll try to look again at that bug tonight.

Francesco

[wxCode-users] Using <wxlike-libname> libraries in Bakefile.

[<msz...@ya...>]

Hi! Joseph has change to the <wxlike-libname> for the DatabaseLayer librari=
es=20
naming. This is a good feature I belieave, but how do I point to this=20
libraries from inside my bakefile (wxarg.bkl).

I've been using <sys-lib> for now but this doesn't work now=20
(obviously ... :) ).

Btw, any idea when the new wx bakefile stuff will be ready?
Should I wait for this to make my source release?
I would really like a replacement for the "compsample" template.

Well, thanks in advanced,

Regards, Mat=EDas=20

	

	
		
__________________________________________________ 
Preguntá. Respondé. Descubrí. 
Todo lo que querías saber, y lo que ni imaginabas, 
está en Yahoo! Respuestas (Beta). 
¡Probalo ya! 
http://www.yahoo.com.ar/respuestas 

Re: [wxCode-users] wxCode bakefile changes

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

John Labenski ha scritto:
> Anything that makes it easier and better is good by me.
good. As soon as I'll manage to work around the bug I've found in 
bakefile, I'll commit my changes...

Francesco

[wxCode-users] RFC - Re: wxCode problems and wxWPM

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

Hi all,
   what about this?

the mail is long but if you want just the "summary" you can read just 
the last lines ;)

Thanks!
Francesco



Francesco Montorsi ha scritto:
> Matías Szeftel ha scritto:
>> Every one on wxCode could try this if is no too much hassle and offer it
>> as a download option. In the hope of having a nice users base.  It would
>> be nice to have a nice packaging system for our wxWidgets applications.
>> I'll try to use it in the next wxARG release.
> Great, thanks!
> 
> This makes it possible for me to introduce a big topic which I already wanted to 
> do :)
> 
> Currently wxCode internals have some drawbacks:
> 
>   1) administration is not as easy as it should be: approving new components 
> takes various time and the current internal structure of wxCode website is not 
> very easy-to-update / straightforward.
> 
>   2) browsing the component list is not as fast as possible: except for the 
> links at the top and at the bottom of the page (those to other categories of 
> components) the content is still generated on-the-fly.
> Initially I thought to cache only the links (since generating that set of links 
> is a _very_ slow operation) to allow the developer which uses the
> 
>   http://wxcode.sourceforge.net/edit.php
> 
> page to immediately see his changes reflected on the component list page, 
> without the need of waiting that some cron job on SF regenerates that page.
> 
> However, I now realize that the infos of the components are not updated so often 
>   and that the entire contents of the complist.php page could easily be cached 
> and refreshed only, say, once per day.
> 
>   3) component infos are not in CVS: before my restructuring of wxCode the (very 
> few) info characterizing each components were kept in the Readme.txt file which 
> any component should have placed in its root folder.
> While this made impossible an automatic generation of nice web reports, it was 
> more programmer-friendly than the current DB-driven solution because it allowed 
> the developer to avoid to use the web interface at 
> http://wxcode.sourceforge.net/edit.php to modify and/or keep updated the 
> component infos. The file was kept in the source repository and thus when e.g. 
> making a new release the programmer only had to modify the version number there.
> 
> I don't know how many of you use http://wxcode.sourceforge.net/edit.php but I'd 
> guess (not sure however) that many components have outdated infos also because 
> of the lazyness of the programmer to update the wxCode internal DB.
> 
>   4) programmers do not keep up2date their components / upload sources to CVS.
> 
>   [ 5) if you think I'm missing something else, please say your opinion... ]
> 
> 
> If we decide to solve problem #2, i.e. cache the components HTML description, 
> then the wxWPM project may help us to partially solve #1, #3 problems providing 
> the following (big IMO) advantages:
> 
>   1) the component infos would be stored in the CVS in an XML-like format, i.e. 
> as a wxWidgets package descriptor (WXP).
> A sample WXP file for my wxXml2 component is at:
> 
> http://wxcode.svn.sourceforge.net/viewvc/wxcode/trunk/wxCode/components/wxxml2/build/wxxml2.wxp?view=markup
> 
> having it in the CVS/SVN allows the developer to easily keep it updated.
> 
> 
>   2) the component list HTML pages could be easily created using 'wxp' command 
> line program (just look at http://wxwpm.sourceforge.net/packages.php - it looks 
> familiar, isn't it ;) ?), and thus also cached and regenerated anytime there's a 
> change.
> 
> Also, updating the website to e.g. a new look would be extremehely easy: just 
> changing the "viewformat" used by the 'wxp' utility (while to change the look of 
> the component list would currently require changing lots of PHP code).
> 
> 
>   3) it would simplify the wxCode website structure, because the DB should not 
> be necessary anymore: from that WXP file (which also contains MORE INFO on the 
> component rather than those currently contained ), the 'wxp' command line 
> utility can generate the HTML description of the packages. Thus the wxCode PHP 
> website should not query the DB anymore but rather use those cached HTML code 
> snippets.
> 
> 
>   4) the maintainer of the component could create more easily the releases of 
> his component. With the info taken from the WXP the 'wxp' utility is able to 
> automatically create the .zip or .tar.gz excluding e.g. the object files, the 
> CVS/.svn folders from the archive, etc.
> Those releases would automatically be directly usable as wxWidgets packages from 
> the wxWPM Package Manager.
> 
> 
> The drawbacks of switching to the use of WXP files rather than the current DB 
> solution:
> 
>   1) administrators of wxCode should necessarily install 'wxp' utility to update 
> the HTML descriptions and/or add new components
> 
>   2) all the maintainers should keep the WXP file (and update it) in the repo of 
> their components.
> 
> 
> What do you think? Are they acceptable?
> 
> 
> Looking forward to hear your opinion,
> Francesco
> 
> 
> 
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: [wxCode-users] Maintainer question

[M. G. <fir...@ho...>]

>have you tried to left-click the items with CTRL pressed?
>It should allow you to select scattered items.

Okay that's what i guessed - however i'm on mac and on mac ctrl-click popus 
up a contextual menu. That's most likely a Firefox flaw - thanks anyway.

_________________________________________________________________
http://magasiner.sympatico.msn.ca

Re: [wxCode-users] Maintainer question

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

Hi,

M. Gagnon ha scritto:
> Hi, i have just taken over bsizer and am now trying to update it. First of 
> all, i wanted to update supported platforms since i know it also works on 
> mac. However the platform is displayed as some List controls (at least in 
> Firefox) and i can only select contiguous elements (i.e. i cannot select MSW 
> and MAC without also selkecting GTK and X11 ,which are in the middle. ) 
have you tried to left-click the items with CTRL pressed?
It should allow you to select scattered items.


> wouldn't checkboxes be better for that?
dynamically generated lists of checkboxes are not so comfortable to handle from 
PHP so I preferred listboxes...

HTH,
Francesco

[wxCode-users] Maintainer question

[M. G. <fir...@ho...>]

Hi, i have just taken over bsizer and am now trying to update it. First of 
all, i wanted to update supported platforms since i know it also works on 
mac. However the platform is displayed as some List controls (at least in 
Firefox) and i can only select contiguous elements (i.e. i cannot select MSW 
and MAC without also selkecting GTK and X11 ,which are in the middle. ) 
wouldn't checkboxes be better for that?

_________________________________________________________________
Achetez ce que vous voulez, quand vous voulez sur Sympatico / MSN Magasiner 
http://magasiner.sympatico.msn.ca/content/shp/?ctId=101,ptnrid=176,ptnrdata=081805

Re: [wxCode-users] wxCode bakefile changes

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

Anything that makes it easier and better is good by me.

-John Labenski

On 2/14/07, Francesco Montorsi <f18...@ya...> wrote:
> Hi all,
>
>     now that bakefile 0.2.2 is out and that the wxpresets have been
> greatly enhanced I'd like to make some BIG changes to wxCode bakefiles.
>
> I've been working on them today and yesterday and I've managed to get
> many advantages:
>
>     - extremely smaller Bakefiles.bkgen files
>     - _much_ cleaner bakefiles (less, more friendly code): you won't
> even need to list your component's sources & headers anymore!
> (Bakefile will automatically detect your component's sources & headers)
>     - painless setting of
>        => wx-style build directory to allow multi-builds with different
> settings for WX_UNICODE/DEBUG/UNICODE
>        => wx-style "lib/[compiler]_lib" directory to allow multi-builds
>        => wx-style lib naming
>     - full support for "gnu" makefile format as alternative to the fat
> "autoconf" format for Unix
>
> The new bakefile 0.2.2 also supports msvs2005 which is surely a Good
> Thing (but see below)
>
> However all these changes have two drawbacks:
>
>   1) currently I've hit a bug in bakefile which makes it loop endlessly
> when generating msvs2005prj and msvc6prj formats for the component samples
>
>   2) it requires modifications to all your component's build files:
>
>       - Bakefiles.bkgen
>       - yourcomp.bkl
>       - configure.ac
>
>      since the new bakefiles are incompatible with the previous ones.
>
>     I've updated all the build systems of my components (changes not yet
> committed) and I can say it requires about 30 minutes to do all the
> changes to the build system.
>
> All in all, I'd say that as soon as the problem #1 will be fixed I'll
> commit the new bakefiles (thus forcing everyone which wants to
> regenerate its component's build system to do the upgrade)... what do
> you say?
>
> Do you agree?
>
> I strongly think it's worth the effort also because I didn't describe in
> details all the advantages you get - e.g. you now get a nice error
> message like "The selected wx build does not exist" when you do "nmake
> -fmakefile.vc WX_UNICODE=1" and you don't have any Unicode build of wx;
> previously you only get a compiler error about an unreachable
> "wx/wxprec.h"...
>
> Francesco
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] Take over unmaintained wxCode project

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

Ok, you're now the maintainer of the "bsizer" component!

Please refer to the maintainer's guide (on wxCode website) for more info 
about setting up CVS repo, making releases etc.

Ask here (on this mailing list) for any doubt,
Francesco


M. Gagnon ha scritto:
> Hi,
> 
> i would like to take over unmaintained project wxBorderSizer. I have already 
> many fixes done for my project, that uses it.
> 
> New features includ:
> 
> - removing use of deprecated functions
> - cleaning up code and documenting it to make it more readable
> - replacing undocumented constants by enums
> - add an option to use flags instead of string parsing
> 
> thanks
> 
> _________________________________________________________________
> Windows Live Spaces: partagez vos photos du Nouvel An! 
> http://discoverspaces.live.com/?loc=fr-CA
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: [wxCode-users] 2.8 missing on wxWidgets supported versions list

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

Matías Szeftel ha scritto:
> Ulrich Telle escribió:
>> As wxWidgets 2.8 is around for quite a while it would be nice to have 
>> the option to flag a wxCode component as compatible with wxWidgets 2.8, 
>> but currently 2.8 is missing from the list of supported wxWidgets 
>> versions. It would be nice, if one of the wxCode adminstrators could add 
>> this option to the list. Thanks!
>>
>> Regards,
>>
>> Ulrich
>>
>>   
>     I wanted to add that bakefile is currently generating projects for
> wx2.6, you can see this in the msw projects as it lists the dependecies:
> wxbase26.lib, wxmsw26_core.lib, etc.
>     Is there a way to set what wx versions should the component be
> compiled against? 
sure - just set WX_VERSION_DEFAULT before including wxcode's 
defaults.bkl to the version you want (e.g. 28).

>Or maybe generating different projects for each wx
> version?
This is another issue - it can be done but requires some trickery: also 
Ulrich asked it to me so I'll post some more details about it in another 
thread.

Francesco

Re: [wxCode-users] A better template for my aplication.

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

Matías Szeftel ha scritto:
> Hello all!
> 
> Regarding bakefile: is there a more suitable template than compsample
> for an application?
> I would like to have different destinations for both debug and release
> version of the executable.
soon there will be - see my mail about bakefile changes.

Francesco

[wxCode-users] wxCode bakefile changes

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

Hi all,

    now that bakefile 0.2.2 is out and that the wxpresets have been
greatly enhanced I'd like to make some BIG changes to wxCode bakefiles.

I've been working on them today and yesterday and I've managed to get 
many advantages:

    - extremely smaller Bakefiles.bkgen files
    - _much_ cleaner bakefiles (less, more friendly code): you won't 
even need to list your component's sources & headers anymore!
(Bakefile will automatically detect your component's sources & headers)
    - painless setting of
       => wx-style build directory to allow multi-builds with different 
settings for WX_UNICODE/DEBUG/UNICODE
       => wx-style "lib/[compiler]_lib" directory to allow multi-builds
       => wx-style lib naming
    - full support for "gnu" makefile format as alternative to the fat 
"autoconf" format for Unix

The new bakefile 0.2.2 also supports msvs2005 which is surely a Good 
Thing (but see below)

However all these changes have two drawbacks:

  1) currently I've hit a bug in bakefile which makes it loop endlessly 
when generating msvs2005prj and msvc6prj formats for the component samples

  2) it requires modifications to all your component's build files:

      - Bakefiles.bkgen
      - yourcomp.bkl
      - configure.ac

     since the new bakefiles are incompatible with the previous ones.

    I've updated all the build systems of my components (changes not yet 
committed) and I can say it requires about 30 minutes to do all the 
changes to the build system.

All in all, I'd say that as soon as the problem #1 will be fixed I'll 
commit the new bakefiles (thus forcing everyone which wants to 
regenerate its component's build system to do the upgrade)... what do 
you say?

Do you agree?

I strongly think it's worth the effort also because I didn't describe in 
details all the advantages you get - e.g. you now get a nice error 
message like "The selected wx build does not exist" when you do "nmake 
-fmakefile.vc WX_UNICODE=1" and you don't have any Unicode build of wx; 
previously you only get a compiler error about an unreachable 
"wx/wxprec.h"...

Francesco

Re: [wxCode-users] 2.8 missing on wxWidgets supported versions list

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

Ulrich Telle ha scritto:
> As wxWidgets 2.8 is around for quite a while it would be nice to have 
> the option to flag a wxCode component as compatible with wxWidgets 2.8, 
> but currently 2.8 is missing from the list of supported wxWidgets 
> versions. It would be nice, if one of the wxCode adminstrators could add 
> this option to the list. Thanks!
done

Francesco

Re: [wxCode-users] Take over unmaintained wxCode project

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

Hi,

M. Gagnon ha scritto:
> i would like to take over unmaintained project wxBorderSizer. I have already 
> many fixes done for my project, that uses it.
that's great news - thanks.

In order to register as maintainer you'll need both a SF account and a 
wxCode maintainer (see http://wxcode.sourceforge.net/register.php).

Once you have both, please mail the user account names to me and I'll 
set you as wxBorderSizer maintainer.

Thanks,
Francesco

Re: [wxCode-users] Can't compile my own component in Linux. Works fine with VS C++ 2005

[Klaas H. <db...@nl...>]

Matías Szeftel wrote:

>     Well, I finally got it working. 

And in my case it were really missing implementations of declared virtual members in the base class.
This is because of a newer gcc, since the code compiled already a long time on Unix.

Klaas


-- 
Unclassified