wxcode-users — Submission, Questions, Information

Re: [wxCode-users] Updating wxCode bakefiles

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

On 8/30/06, John Labenski <jla...@gm...> wrote:
> > Thanks! I've checked it and found no errors except for the use of --
> > string as separator (which is not allowed within an XML file); I
> > replaced them with ~~

Oops, I just got bakefile working in linux so I can test things now. I
dunno what the problem I had with it was before, just got a clean copy
and hacked away...

> > > Secondly, I would really like to make it so that the library built for
> > > a component be given a name such as
> > > $(WXBASENAME)_mycomponent_name-$(WXRELEASE) to make it easier to link
> > > to, especially if you want to compile more than one version of them.
> > > We could use the same semantics as wxWidgets does where for example
> > > $(WXBASENAME) == 'wx-config --basename' == wx_gtk2ud for gtk, unicode, debug
> > > and then you would use <wx-lib>mycomp_name</wx-lib> in the bakefiles to get it.
> > Good point. I had noticed that this would be very useful lot of times
> > but never found time.
> >
> > >
> > > I have two problems with this,
> > > 1) where or how do you adjust the name of the created lib
> > Ok, I've added to wxhacks the wxlike-libname and wxlike-dllname tags so
> > that now you can write:
> >
> >      <lib id="keybinder_lib" template="complib" cond="WX_SHARED=='0'">
> >          <wxlike-libname>keybinder</wxlike-libname>
> >      </lib>
> >
> > if you want your lib to be named to the "wx" manner.

Great! I added these lines to wxhacks.bkl to also get the unicode and
debug syntax too.

  <set var="WXLIBPOSTFIX" cond="WX_UNICODE=='1'">$(WXLIBPOSTFIX)u</set>
  <set var="WXLIBPOSTFIX" cond="WX_DEBUG=='1'">$(WXLIBPOSTFIX)d</set>

Officially they use somthing like this, for richtext, which is of a
similar nature as a wxCode component.
          $(LIBDIRNAME)/$(DLLPREFIX)$(WXDLLNAMEPREFIXGUI)$(WXUNICODEFLAG)$(WXDEBUGFLAG)$(WX_LIB_FLAVOUR)_richtext$(WXCOMPILER)$(VENDORTAG)$(WXDLLVERSIONTAG)$(dll___targetsuf3)

> > > 2) would <wx-lib>mycomp_name</wx-lib> really work or would this line
> > > in build/autoconf/wxpresets.m4 not work?
> > >
> > > WX_LIBS="$($WX_CONFIG_PATH $wx_config_args $WXCFG_FLAGS
> > > $1,$WX_ADDITIONAL_LIBS --libs)"
> > need to test it as autoconf format will require some work.

Grrrr!!! The wxWidgets bakefile has a check so if you do
<wx-lib>sheet</wx-lib> to use the
<wxlike-libname>sheet</wxlike-libname> sheet lib you get this error
from bakefile_gen.

-----------------------------------------------------------------------
Unknown wxWidgets library given in the wx-lib tag
-----------------------------------------------------------------------

/home/john/lib/bakefile-0.2.0/share/bakefile/presets/wx_win32.bkl:299:
error: an error occured during processing
    when processing target at
/home/john/cvs/wxCode/wxCode/components/wxsheet/build/wxsheet.bkl:71

This is because they have this in wx.bkl, which doesn't even have richedit!

    <set var="LIB_LIST">base core net xml odbc xrc html adv media gl
dbgrid qa</set>
    <set var="CONTRIBLIB_LIST">animate applet deprecated fl foldbar
gizmos mmedia netutils ogl plot stc svg</set>
    <set var="ALLLIB_LIST">$(LIB_LIST) $(CONTRIBLIB_LIST)</set>

and this in wx_win32.bkl and wx_unix.bkl

        <if cond="value not in ALLLIB_LIST.split()">
            <error>Unknown wxWidgets library given in the wx-lib tag</error>
        </if>

I have to give up now, since I cannot get the <wx-lib>adv</wx-lib> to
get added to the Makefile.in and GNUmakefile. Same for html or any
other wxlib.

> > In fact, I'm now trying to transfer some wxLua bakefile/m4 code to
> > wxCode bakefiles/m4 but since with wxLua we're using a patched bakefile
> > and wxCode not, the things are not easy and may require some time.
> >
> > If only my patches were applied to bakefile... (just daydreaming)

:)

Thanks,
    John Labenski

Re: [wxCode-users] components to put in SVN repo

[Ernesto R. D. <mid...@ya...>]

Francesco Montorsi escribió:
> Hi all,
>    to me it seems that I can begin to setup SVN repo.
> 
> Before uploading contents to it however, I'd like to know which 
> components are willing to use it (and thus be removed from CVS). Note 
> that all revision history will be preserved (in SVN).
> 
> I'm going to put in SVN the following components (which I maintain):
> 
>   keybinder
>   webupdate
>   wxextminiframe (with the extminiframe name)
>   wxscript
>   wxxml2
> 
> I guess Angelo wants his component moved, too (wxhttpengine - with 
> folder name 'httpengine' maybe ?), right ?
> 
> Also, looking at CVS I see that the hyperlink component is there - Otto, 
> I guess you know that I merged it with Ryan's implementation and already 
> submitted in to wxWidgets HEAD (and it's already part of wx) - so maybe 
> we can remove it from CVS, too ?
> 
> 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
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

I would appreciate if you could change my component (wxMSWResources) to 
the SNV repo.

Thanks!
__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

Re: [wxCode-users] SVN poll again

[Ernesto R. D. <mid...@ya...>]

I would like to see wxCode switch to SVN very much.
So my vote is "YES" go for SVN
__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

Re: [wxCode-users] Updating wxCode bakefiles

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

Thanks, I'll try to test it as soon as I get a chance.
    -John Labenski

On 8/30/06, Francesco Montorsi <f18...@ya...> wrote:
> John Labenski ha scritto:
> > I've added quite a few more comments to the
> > wxCode/bakefiles/empty.bkl.template file to (hopefully) make it easier
> > to understand. Please let me know if what I've written doesn't make
> > sense or if there are other items that should be clarified.
> Thanks! I've checked it and found no errors except for the use of --
> string as separator (which is not allowed within an XML file); I
> replaced them with ~~
>
> >
> > Secondly, I would really like to make it so that the library built for
> > a component be given a name such as
> > $(WXBASENAME)_mycomponent_name-$(WXRELEASE) to make it easier to link
> > to, especially if you want to compile more than one version of them.
> > We could use the same semantics as wxWidgets does where for example
> > $(WXBASENAME) == 'wx-config --basename' == wx_gtk2ud for gtk, unicode, debug
> > and then you would use <wx-lib>mycomp_name</wx-lib> in the bakefiles to get it.
> Good point. I had noticed that this would be very useful lot of times
> but never found time.
>
> >
> > I have two problems with this,
> > 1) where or how do you adjust the name of the created lib
> Ok, I've added to wxhacks the wxlike-libname and wxlike-dllname tags so
> that now you can write:
>
>      <lib id="keybinder_lib" template="complib" cond="WX_SHARED=='0'">
>          <wxlike-libname>keybinder</wxlike-libname>
>      </lib>
>
> if you want your lib to be named to the "wx" manner.
>
>
> > 2) would <wx-lib>mycomp_name</wx-lib> really work or would this line
> > in build/autoconf/wxpresets.m4 not work?
> >
> > WX_LIBS="$($WX_CONFIG_PATH $wx_config_args $WXCFG_FLAGS
> > $1,$WX_ADDITIONAL_LIBS --libs)"
> need to test it as autoconf format will require some work.
>
> In fact, I'm now trying to transfer some wxLua bakefile/m4 code to
> wxCode bakefiles/m4 but since with wxLua we're using a patched bakefile
> and wxCode not, the things are not easy and may require some time.
>
> If only my patches were applied to bakefile... (just daydreaming)
>
>
> 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
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] components to put in SVN repo

[Angelo M. <ama...@gm...>]

Awesome!  Renaming wxhttpengine to httpengine in SVN sounds good.

Thanks,
angelo



On 8/30/06, Francesco Montorsi <f18...@ya...> wrote:
>
> Hi all,
>    to me it seems that I can begin to setup SVN repo.
>
> Before uploading contents to it however, I'd like to know which
> components are willing to use it (and thus be removed from CVS). Note
> that all revision history will be preserved (in SVN).
>
> I'm going to put in SVN the following components (which I maintain):
>
>   keybinder
>   webupdate
>   wxextminiframe (with the extminiframe name)
>   wxscript
>   wxxml2
>
> I guess Angelo wants his component moved, too (wxhttpengine - with
> folder name 'httpengine' maybe ?), right ?
>
> Also, looking at CVS I see that the hyperlink component is there - Otto,
> I guess you know that I merged it with Ryan's implementation and already
> submitted in to wxWidgets HEAD (and it's already part of wx) - so maybe
> we can remove it from CVS, too ?
>
> 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
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] components to put in SVN repo

[Otto W. <ott...@or...>]

Francesco Montorsi wrote:
> While we are on it: I read on wx-users some time ago that someone 
> extended wxTreeListCtrl with a native wxMSW implementation. This makes 
> it eligible for integration in wx: in fact, if you would make a patch 
> containing the generic version and the wxMSW version I'm sure someone 
> will create a wxGTK-native version, too....
>
>   
Actually a copied and changed version was submitted to one of the 
wxForums. I've added most changes of that version to wxCode except for 
the native wxMSW changes. I think that's not the right way to do it, 
instead for 2.7 and later the native renderer functions were used for 
drawing the columns headers etc. So platform specific drawings should be 
done through the native renderer. All changes are in CVS I haven't found 
the time to do a file release.

O. Wyss

Re: [wxCode-users] components to put in SVN repo

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

>Before uploading contents to it however, I'd like to know which
>components are willing to use it (and thus be removed from CVS). Note
>that all revision history will be preserved (in SVN).

I will move wxMidi to SVN. But I'm living from vacation tomorrow
morning, so I will not do anything it in at least three weeks.

Regards,
Cecilio

Re: [wxCode-users] components to put in SVN repo

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

Otto Wyss ha scritto:
> Francesco Montorsi wrote:
>> Also, looking at CVS I see that the hyperlink component is there - Otto, 
>> I guess you know that I merged it with Ryan's implementation and already 
>> submitted in to wxWidgets HEAD (and it's already part of wx) - so maybe 
>> we can remove it from CVS, too ?
>>
>>   
> I'll check it. Just leave it there as long as wxWidgets 2.6 is stable, 
> remove it after 2.8 is released.
ok, good idea. BTW thanks for that control - it required few 
modifications to be submitted as patch and it's very very useful - thanks!

While we are on it: I read on wx-users some time ago that someone 
extended wxTreeListCtrl with a native wxMSW implementation. This makes 
it eligible for integration in wx: in fact, if you would make a patch 
containing the generic version and the wxMSW version I'm sure someone 
will create a wxGTK-native version, too....

Obviously, time permitting ;)

Francesco

Re: [wxCode-users] components to put in SVN repo

[Otto W. <ott...@or...>]

Francesco Montorsi wrote:
> Also, looking at CVS I see that the hyperlink component is there - Otto, 
> I guess you know that I merged it with Ryan's implementation and already 
> submitted in to wxWidgets HEAD (and it's already part of wx) - so maybe 
> we can remove it from CVS, too ?
>
>   
I'll check it. Just leave it there as long as wxWidgets 2.6 is stable, 
remove it after 2.8 is released.

O. Wyss

[wxCode-users] components to put in SVN repo

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

Hi all,
   to me it seems that I can begin to setup SVN repo.

Before uploading contents to it however, I'd like to know which 
components are willing to use it (and thus be removed from CVS). Note 
that all revision history will be preserved (in SVN).

I'm going to put in SVN the following components (which I maintain):

  keybinder
  webupdate
  wxextminiframe (with the extminiframe name)
  wxscript
  wxxml2

I guess Angelo wants his component moved, too (wxhttpengine - with 
folder name 'httpengine' maybe ?), right ?

Also, looking at CVS I see that the hyperlink component is there - Otto, 
I guess you know that I merged it with Ryan's implementation and already 
submitted in to wxWidgets HEAD (and it's already part of wx) - so maybe 
we can remove it from CVS, too ?

Francesco

Re: [wxCode-users] SVN poll again

[Otto W. <ott...@or...>]

Francesco Montorsi wrote:
> Otto Wyss ha scritto:
>   
>> Anyone changed his mind ?
>>
>>
>> Not me, I stick to CVS.
>>     
> but would you accept to have CVS+SVN repo enabled for wxCode?
>
>
>   
Yes of course.

O. Wyss

Re: [wxCode-users] SVN poll again

[Angelo M. <ama...@gm...>]

I like the idea of using SVN.  It seems easier to setup and use.

Every time I setup a new computer I spend hours reconfiguring CVS, you
almost need to be an expert with it to get it working.  We would see a lot
more people contributing code if the revision check in/out process was
easier.  I think SVN offers just that.

If CVS and SVN can co-exist then I don't see a problem.

--angelo


On 8/30/06, Francesco Montorsi <f18...@ya...> wrote:
>
> Otto Wyss ha scritto:
> > Anyone changed his mind ?
> >
> >
> > Not me, I stick to CVS.
> but would you accept to have CVS+SVN repo enabled for wxCode?
>
> They could cohexist...
>
> 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
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] SVN poll again

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

Otto Wyss ha scritto:
> Anyone changed his mind ?
> 
> 
> Not me, I stick to CVS.
but would you accept to have CVS+SVN repo enabled for wxCode?

They could cohexist...

Francesco

Re: [wxCode-users] SVN poll again

[Otto W. <ott...@or...>]

Anyone changed his mind ?


Not me, I stick to CVS.

O. Wyss

Re: [wxCode-users] SVN poll again

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

On 8/30/06, cecilio <s.c...@gm...> wrote:
> Hi all,
>
>
> > 6) last time there were:
> >
> >     3 pro: me, Angelo and Cecilio
> >     2 against: John, Otto
> >     2 undecided: Ulrich, Joseph
> >
> > Anyone changed his mind ?
> I would prefer SVN, but my usage of either CVS / SVN will be minimal.
> So I would prefer to abstent in this votation. I will accept any
> solution the others prefer.
>
> Bets regards,
> Cecilio

If you can do both, then sure... I like the idea that you can comingle
the two repositories since that will make it much easier to share
components. Otherwise, what would happen if you used two components
one in CVS one in SVN, I think the current way to use a component is
to define an environment variable $(WXCODE) for the path. This would
be awkward if they're in different places.

If they're both able to work together, I have no problem.

Regards,
    John Labenski

Re: [wxCode-users] SVN poll again

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

Hi all,


> 6) last time there were:
>
>     3 pro: me, Angelo and Cecilio
>     2 against: John, Otto
>     2 undecided: Ulrich, Joseph
>
> Anyone changed his mind ?
I would prefer SVN, but my usage of either CVS / SVN will be minimal.
So I would prefer to abstent in this votation. I will accept any
solution the others prefer.

Bets regards,
Cecilio

[wxCode-users] SVN poll again

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

Hi all,
   some time has passed since the last poll, so I'd like to know if
anyone has changed idea about this.

To summarize:

1) I can grant SVN is easy to learn specially for those who use CVS.
Basically all you need to know (at least for basic usage) is:

    a) unlike CVS it uses a single number for revisions (e.g. CVS: 1.324
  SVN: 324). This makes a lot of sense once you get used it !

    b) HEAD is TRUNK in SVN terminology

Reading first paragraphs of the "Subversion for CVS Users" doc at

   http://svnbook.red-bean.com/en/1.0/apa.html

will be enough to be able to do practically everything you did in CVS in
the new SVN world!

2) GUI tools for SVN are available for both win and Unix even if on Unix
I always use command-line tools (just like I use commandline tools also
for CVS).

3) HD usage of SVN will be more than CVS. I did almost all steps (not
the final one!) for importing CVS contents of wxCode into a new wxCode
SVN repo and found that wxCode CVS repository is around 108 Megabytes
currently. The "svn dump" I obtained for upload in SVN repo is around
240 Megabytes. I'm not sure however if this means that a SVN checkout
will take the same amount of space... (I strongly doubt - since 240 MB
is the repo with all revision history; a checkout only contains last
revision).

4) if we enable SVN for wxCode, we do not need to turn off CVS. The two
can coexist. In fact, I think we will never be able to satisfy all
maintainers if we choose X over Y. Thus I think we should have both CVS
and SVN repositories, *without* component duplication: a component is
either in the CVS or in SVN, not in both.
I know that many of you noted that this makes it harder to have all
components of wxCode in a single place. However this problem could be
solved creating a simple script (for Unix at least) which check-out all
CVS repository and SVN repository and "merge" them in the local harddisk
of the user. This can be obtained just doing:

    a) cd $folder_where_we_must_checkout
    b) cvs -d:ext:fr...@cv...:/cvsroot/wxcode checkout wxCode
    c) svn co
https://svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components
wxCode/components

in that way user will get a wxCode/components folder containing both
components under CVS and components under SVN.

5) SVN is

   a)somewhat faster
   b) allows to do practically everything offline (eg see which files 
have been modified and how), including removing folders added by error
   c) SVN supports attributes and permissions; this means that e.g. a 
Windows developer can set the executable flag on the "configure" script 
of its component without changing to Unix workstation. I'm sure this 
will greatly help people which develop from Windows components 
supporting also Unix.


6) last time there were:

    3 pro: me, Angelo and Cecilio
    2 against: John, Otto
    2 undecided: Ulrich, Joseph

Anyone changed his mind ?
:D

Francesco

Re: [wxCode-users] Updating wxCode bakefiles

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

John Labenski ha scritto:
> I've added quite a few more comments to the
> wxCode/bakefiles/empty.bkl.template file to (hopefully) make it easier
> to understand. Please let me know if what I've written doesn't make
> sense or if there are other items that should be clarified.
Thanks! I've checked it and found no errors except for the use of -- 
string as separator (which is not allowed within an XML file); I 
replaced them with ~~

> 
> Secondly, I would really like to make it so that the library built for
> a component be given a name such as
> $(WXBASENAME)_mycomponent_name-$(WXRELEASE) to make it easier to link
> to, especially if you want to compile more than one version of them.
> We could use the same semantics as wxWidgets does where for example
> $(WXBASENAME) == 'wx-config --basename' == wx_gtk2ud for gtk, unicode, debug
> and then you would use <wx-lib>mycomp_name</wx-lib> in the bakefiles to get it.
Good point. I had noticed that this would be very useful lot of times 
but never found time.

> 
> I have two problems with this,
> 1) where or how do you adjust the name of the created lib
Ok, I've added to wxhacks the wxlike-libname and wxlike-dllname tags so 
that now you can write:

     <lib id="keybinder_lib" template="complib" cond="WX_SHARED=='0'">
         <wxlike-libname>keybinder</wxlike-libname>
     </lib>

if you want your lib to be named to the "wx" manner.


> 2) would <wx-lib>mycomp_name</wx-lib> really work or would this line
> in build/autoconf/wxpresets.m4 not work?
> 
> WX_LIBS="$($WX_CONFIG_PATH $wx_config_args $WXCFG_FLAGS
> $1,$WX_ADDITIONAL_LIBS --libs)"
need to test it as autoconf format will require some work.

In fact, I'm now trying to transfer some wxLua bakefile/m4 code to 
wxCode bakefiles/m4 but since with wxLua we're using a patched bakefile 
and wxCode not, the things are not easy and may require some time.

If only my patches were applied to bakefile... (just daydreaming)


Francesco

Re: [wxCode-users] Updating wxCode bakefiles

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

On a more important note, there are some changes to the configure
script and/or bakefiles that need to be made.

1) Makefile.in uses "-I./include" instead of "-I$(srcdir)/include" so
that you cannot run configure from anywhere other than the root dir of
the component. I cannot for the life of me figure out where this code
comes from.

2) the generated configure script needs the lines
mkdir -p lib
mkdir -p samples/MYSAMPLE_NAME
before the end, perhaps before "# end in a nice way the configure
script" so that if you build from anywhere other than the root dir of
the components these dirs exist. Again, it's easy enough to add to the
generated configure script, but I cannot figure out where they should
be added upstream.

Thanks (Francesco :),
    John Labenski


On 8/28/06, John Labenski <jla...@gm...> wrote:
> I've added quite a few more comments to the
> wxCode/bakefiles/empty.bkl.template file to (hopefully) make it easier
> to understand. Please let me know if what I've written doesn't make
> sense or if there are other items that should be clarified.
>
> Secondly, I would really like to make it so that the library built for
> a component be given a name such as
> $(WXBASENAME)_mycomponent_name-$(WXRELEASE) to make it easier to link
> to, especially if you want to compile more than one version of them.
> We could use the same semantics as wxWidgets does where for example
> $(WXBASENAME) == 'wx-config --basename' == wx_gtk2ud for gtk, unicode, debug
> and then you would use <wx-lib>mycomp_name</wx-lib> in the bakefiles to get it.
>
> I have two problems with this,
> 1) where or how do you adjust the name of the created lib
> 2) would <wx-lib>mycomp_name</wx-lib> really work or would this line
> in build/autoconf/wxpresets.m4 not work?
>
> WX_LIBS="$($WX_CONFIG_PATH $wx_config_args $WXCFG_FLAGS
> $1,$WX_ADDITIONAL_LIBS --libs)"
>
> Thanks,
>     John Labenski
>

[wxCode-users] Updating wxCode bakefiles

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

I've added quite a few more comments to the
wxCode/bakefiles/empty.bkl.template file to (hopefully) make it easier
to understand. Please let me know if what I've written doesn't make
sense or if there are other items that should be clarified.

Secondly, I would really like to make it so that the library built for
a component be given a name such as
$(WXBASENAME)_mycomponent_name-$(WXRELEASE) to make it easier to link
to, especially if you want to compile more than one version of them.
We could use the same semantics as wxWidgets does where for example
$(WXBASENAME) == 'wx-config --basename' == wx_gtk2ud for gtk, unicode, debug
and then you would use <wx-lib>mycomp_name</wx-lib> in the bakefiles to get it.

I have two problems with this,
1) where or how do you adjust the name of the created lib
2) would <wx-lib>mycomp_name</wx-lib> really work or would this line
in build/autoconf/wxpresets.m4 not work?

WX_LIBS="$($WX_CONFIG_PATH $wx_config_args $WXCFG_FLAGS
$1,$WX_ADDITIONAL_LIBS --libs)"

Thanks,
    John Labenski

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

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:
>> 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] Removing wxMidi from wxCode CVS

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

cecilio ha scritto:
> Having to maintain wxMidi also in wxCode is causing me a lot of
> trouble, specially because I no longer use CVS (I moved lenmus project
> to SVN). 
Actually I don't remember how the "Moving to subversion" thread ended, 
i.e. if we took a definitive solution. BTW I think I'll be able to 
revise this entire issue very soon (few days) since my SoC project ended 
and with that I'll be able to do various improvements to wxCode 
automation for project management.

Francesco

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