wxcode-users

Re: [wxCode-users] wxCtb maintainance

[Joachim B. <jbu...@ze...>]

Hello Francesco,

(sorry, couldn't contact you directly)
I have updated my project sources (wxctb-0.9) in the CVS . But I'm personally 
no longer work with cvs and using svn instead. How can I switch my cvs to 
subversion.
As I try to import/add the sources to svn, I get the following error:

svn: Commit failed (details follow):
svn: MKACTIVITY 
of '/svnroot/wxcode/!svn/act/798da748-8e2b-0410-a062-8031419a0445': 403 
Forbidden (https://svn.sourceforge.net)

(I have checked out the wxCode as described in the document (part svn) linked 
by the automated message below).

BTW: I have changed my SourceForge password, but on wxCode (for edit the wxctb 
component) I have to use still my old (origin) password.

Can you give me some hints, how I can resolve this?
Someone else?

Best regards
Joachim


Am Sunday 11 March 2007 21:04 schrieb Joachim Buermann:
> ----------  Forwarded Message  ----------
>
> Subject: wxCtb maintainance
> Date: Sunday 11 March 2007 20:33
> From: Francesco Montorsi <fr...@pr...>
> To: jbu...@if...
>
> Hi Joachim Buermann,
> This is an automated message sent by wxCode project
>  (http://wxcode.sourceforge.net) because you are registered as the wxCode
>  maintainer for the wxCtb component.
>
> It looks like you haven't uploaded yet any source file to the repository:
>   http://wxcode.cvs.sourceforge.net/wxcode/wxCode/components/wxctb
>
> Please upload sources as soon as possible.
> For help on how to setup the CVS software and upload the sources, please
>  refer to: http://wxcode.sourceforge.net/maintguide.php
>
> Thanks!
> The wxCode project administrators
>
> -------------------------------------------------------

Re: [wxCode-users] wxCtb maintainance

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

[redirecting from wx-users mailing list back to wxcode-users...]

Hi Joachim,

Joachim Buermann ha scritto:
>> - after committing it to SVN, remove it from CVS
>> - you won't need to commit .cvsignore files (if you use them) in SVN
>> - you may want to set the svn:executable property on files which need them
>> (e.g. configure scripts for Unix if you use them)
>> - be careful when using SVN: it does not allow per-path authorizations so
>> that e.g. if you remove the sources of another components from
>> wxCode\components folder and then commit your changes, they'll go through:
>> i.e. you may damage other people's components. Please be careful to avoid
>> it.
> 
> Does this means: I have to checkout all components in a local folder, add the 
> wxctb stuff (as an additional folder) and than commit it via svn.
> Or can I import my sources to svn without checkout the other wxCode components 
> (to avoid confusion for the other users)?
yes, you can avoid checking out others' components using this url:

https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/ctb

Note that I have created your component's folder as "ctb" and not 
"wxctb" just because the "wx" prefix is "deprecated" as in wxcode 
project everything is wx-related and thus it makes no much sense...


>> Last: I see you've also made a new release for wxCTB 0.9, however the old
>> one (look below in the list of wxCode components download: there is a
>> "wxCTB" release already) should be versioned too (and maybe set as "hidden"
>> since it's the old one) to avoid confusion for the users.
> 
> Done!
great, thanks

Francesco

Re: [wxCode-users] wxCtb maintainance

[<jbu...@if...>]

Hello Francesco,

Sorry for the delay, but I'm very busy with my main job these days and 
couldn't find more time for my open source stuff ;-(
I also had some problems with my email provider and the delivering of my last responses are refused. So sorry again.

I have checked in the ctb sources in the svn repository, you have told me: 
https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/ctb

Can you also create a svn folder for my awx project, maybe
https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/awx
I've add some improvments and would like to put these also in the svn repository.
 
This would be great :-)

Best regards and many thanks for your friendly help.
Joachim

Re: [wxCode-users] wxCtb maintainance

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

Hi,

jbu...@if... ha scritto:
> Hello Francesco,
> 
> Sorry for the delay, but I'm very busy with my main job these days and 
> couldn't find more time for my open source stuff ;-(
> I also had some problems with my email provider and the delivering of my last responses are refused. So sorry again.
sure, no problem. I know what you mean - I'm going to have a very busy 
period in 2 next weeks.

> I have checked in the ctb sources in the svn repository, you have told me: 
> https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/ctb
thanks!

To complete the movement of the component you'd just need to remove the 
CVS sources... I can do it for you if you say it's ok (i.e. you've 
already moved all source files and don't need the CVS repo anymore).

Last, I see wxCtb has a bakefile build system which is not however based 
on wxCode bakefiles... that's fine but I wonder how it can adapt to the 
many possible wxWidgets different configurations... using wxCode 
bakefiles probably would result in a smaller bakefile and a better build 
system :)

Also I'm currently getting this:

g++ -c -o release/wxctb_lib_timer.o -DNDEBUG  -D_THREAD_SAFE -pthread 
-O0 -I../include   -MTrelease/wxctb_lib_timer.o -MF`echo 
release/wxctb_lib_timer.o | sed -e 's,\.o$,.d,'` -MD ../src/linux/timer.cpp
../src/linux/timer.cpp: In function ‘void kill_all_timer()’:
../src/linux/timer.cpp:93: error: ‘pthread_kill_other_threads_np’ was 
not declared in this scope

and that's strange because adding a #include <pthread.h> does not solve 
it...


> Can you also create a svn folder for my awx project, maybe
> https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/awx
> I've add some improvments and would like to put these also in the svn repository.
Sure, done.

As for wxctb, once you've moved sources, please remove them from CVS.

thanks,
Francesco

Re: [wxCode-users] wxCtb maintainance

[<jbu...@if...>]

Hello Francesco,

> To complete the movement of the component you'd just need to remove the
> CVS sources... I can do it for you if you say it's ok (i.e. you've
> already moved all source files and don't need the CVS repo anymore).

ok, you can remove it. The svn sources are the newest one.

> Last, I see wxCtb has a bakefile build system which is not however based
> on wxCode bakefiles... that's fine but I wonder how it can adapt to the
> many possible wxWidgets different configurations... using wxCode
> bakefiles probably would result in a smaller bakefile and a better build
> system :)

Yes, because the ctb library is used in some embedded systems and other pc =
applications without any wxWidget installation. I want to make the bakefile=
 as simple as possible and my first trials with the wxCode based bakefiles =
(one or more years ago) let me run in some trouble, I couldn't solve. Also =
I want to build the library independently from some needed directory struct=
s (maybe it's possible, but I couldn't figure out it), so the user can buil=
d the libs without a wxWidget or wxCode installation.
If you can give me some hints for a better, wxCode conform bakefile, that a=
lso create makefiles also for people without a wxWidget or wxCode installat=
ion, that would be great :-)
=20
>
> Also I'm currently getting this:
>
> g++ -c -o release/wxctb_lib_timer.o -DNDEBUG  -D_THREAD_SAFE -pthread
> -O0 -I../include   -MTrelease/wxctb_lib_timer.o -MF`echo
> release/wxctb_lib_timer.o | sed -e 's,\.o$,.d,'` -MD ../src/linux/timer.c=
pp
> ../src/linux/timer.cpp: In function =E2=80=98void kill_all_timer()=E2=80=
=99:
> ../src/linux/timer.cpp:93: error: =E2=80=98pthread_kill_other_threads_np=
=E2=80=99 was
> not declared in this scope
>
> and that's strange because adding a #include <pthread.h> does not solve
> it...

That function is obsolete. Comment it out and try again. I will do that as =
soon as possible in the svn.

> > Can you also create a svn folder for my awx project, maybe
> > https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/componen=
ts
> >/awx I've add some improvments and would like to put these also in the s=
vn
> > repository.

Ok, need some days and let you know, when i'm ready.

> Sure, done.

again many thanks ;-)

> As for wxctb, once you've moved sources, please remove them from CVS.

You can remove it (but I don't want to waste your time ;-)

>
> thanks,
> Francesco

Many thanks for your effort and best regards
Joachim

Re: [wxCode-users] wxCtb maintainance

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

Hi
,
jbu...@if... ha scritto:
> Hello Francesco,
> 
>> To complete the movement of the component you'd just need to remove the
>> CVS sources... I can do it for you if you say it's ok (i.e. you've
>> already moved all source files and don't need the CVS repo anymore).
> 
> ok, you can remove it. The svn sources are the newest one.
done

>> Last, I see wxCtb has a bakefile build system which is not however based
>> on wxCode bakefiles... that's fine but I wonder how it can adapt to the
>> many possible wxWidgets different configurations... using wxCode
>> bakefiles probably would result in a smaller bakefile and a better build
>> system :)
> 
> Yes, because the ctb library is used in some embedded systems and other pc 
 > applications without any wxWidget installation.
It's possible to make a bakefile which builds a lib without anything 
wx-related and then add a target (e.g. a sample) which builds against 
that lib and wxWidgets...

BTW I didn't know CTB could build also without wx given that its classes 
are named with the 'wx' prefix (AFAIR).

> I want to make the bakefile 
 >as simple as possible and my first trials with the wxCode based bakefiles
 >(one or more years ago) let me run in some trouble, I couldn't solve.
probably they do not exist anymore :)

 >Also I want to build the library independently from some needed 
directory structs
 >(maybe it's possible, but I couldn't figure out it), so the user can 
build the
 >libs without a wxWidget or wxCode installation.
that's possible too. You could just create an option USE_WXWIDGETS which 
would enable/disable the wx-specific portions.

> If you can give me some hints for a better, wxCode conform bakefile, that also 
 >create makefiles also for people without a wxWidget or wxCode 
installation,
 >that would be great :-)
wxCode stuff is not required at all by wxCode components build system. 
However wxWidgets stuff is.


>> Also I'm currently getting this:
>>
>> g++ -c -o release/wxctb_lib_timer.o -DNDEBUG  -D_THREAD_SAFE -pthread
>> -O0 -I../include   -MTrelease/wxctb_lib_timer.o -MF`echo
>> release/wxctb_lib_timer.o | sed -e 's,\.o$,.d,'` -MD ../src/linux/timer.cpp
>> ../src/linux/timer.cpp: In function ‘void kill_all_timer()’:
>> ../src/linux/timer.cpp:93: error: ‘pthread_kill_other_threads_np’ was
>> not declared in this scope
>>
>> and that's strange because adding a #include <pthread.h> does not solve
>> it...
> 
> That function is obsolete. Comment it out and try again. I will do that as soon as possible in the svn.
thanks, it now compiles.

However I see it does not uses wxWidgets even in the sample... so that 
in effect it does not uses wxWidgets at all. So, the question is: why 
call the classes 'wx*' and why make wxCTB a wxWidgets "component" ?

:)

Francesco

Re: [wxCode-users] wxCtb maintainance

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

Joachim Buermann ha scritto:
> Hello Francesco,
> 
> (sorry, couldn't contact you directly)
hmm why?
btw there's no problem in posting here if you don't need to communicate private 
things (e.g. passwords).


> I have updated my project sources (wxctb-0.9) in the CVS .
Great!

> But I'm personally 
> no longer work with cvs and using svn instead. How can I switch my cvs to 
> subversion.
just tell us ;)



> As I try to import/add the sources to svn, I get the following error:
> 
> svn: Commit failed (details follow):
> svn: MKACTIVITY 
> of '/svnroot/wxcode/!svn/act/798da748-8e2b-0410-a062-8031419a0445': 403 
> Forbidden (https://svn.sourceforge.net)
yes, that's because you hadn't the "svn access" authorization set. I've changed 
it now.

Now you should be able to commit your component in the SVN repo: just some notes:

- after committing it to SVN, remove it from CVS
- you won't need to commit .cvsignore files (if you use them) in SVN
- you may want to set the svn:executable property on files which need them (e.g. 
configure scripts for Unix if you use them)
- be careful when using SVN: it does not allow per-path authorizations so that 
e.g. if you remove the sources of another components from wxCode\components 
folder and then commit your changes, they'll go through: i.e. you may damage 
other people's components. Please be careful to avoid it.

Last: I see you've also made a new release for wxCTB 0.9, however the old one 
(look below in the list of wxCode components download: there is a "wxCTB" 
release already) should be versioned too (and maybe set as "hidden" since it's 
the old one) to avoid confusion for the users.


> (I have checked out the wxCode as described in the document (part svn) linked 
> by the automated message below).
> 
> BTW: I have changed my SourceForge password, but on wxCode (for edit the wxctb 
> component) I have to use still my old (origin) password.
yes, SF and wxCode passwords are completely unrelated. In fact, in general using 
different passwords for different things is the safest thing.

If you want to change it however, please go to http://md5.rednoize.com/, type 
your new password, click "md5" and then mail me back the MD5 string you get 
generated (i.e. I need only the md5 of your new password, I don't care how you 
md5-ify it, e.g. if you don't trust that site you can use one of the many other 
tools that give you the md5 digest of strings).

Thanks,
Francesco