Menu
▾
▴
libvisual-devel — libvisual mailinglist for developers
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(38) |
May
(22) |
Jun
(92) |
Jul
(101) |
Aug
(18) |
Sep
(286) |
Oct
(180) |
Nov
(73) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(18) |
Feb
(74) |
Mar
(56) |
Apr
(11) |
May
(5) |
Jun
(4) |
Jul
(20) |
Aug
(4) |
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
| 2006 |
Jan
(11) |
Feb
(2) |
Mar
(10) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(24) |
Aug
(11) |
Sep
(5) |
Oct
(16) |
Nov
(25) |
Dec
(8) |
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
(4) |
Nov
(12) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
|
From: Dennis S. <sy...@yo...> - 2004-06-29 09:04:41
|
On Sun, 2004-06-27 at 23:38 -0300, Duilio Javier Protti wrote: > However, if you have any problem, I can send you a > distro package for to make the release. Then we can > keep trying to resolve the problem, even online as > we did the other day, if you like. I've fixed it, a complete clean checkout helped it. I'm preparing to do a release ! Thanks and cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-06-29 04:55:30
|
On Mon, 2004-06-28 at 21:36 -0300, Gustavo Sverzut Barbieri wrote: > Em Sunday 27 June 2004 23:38, Duilio Javier Protti escreveu: > > > I know i know, you're not understanding me! :) > > > > > > 1. Within the CVS directory I ran make dist. > > > > > > The resulting package I unpacked and did ./configure ; make in > > > This is where i get errors regarding the .deps directory. Thus I can't > > > release tonight :) It would be good if we could solve this tomorrow. > > > > > > Cheers, > > > Dennis > > > > You make 'cvs co' or 'cvs update'? Because I have heard > > somewhere that CVS on sf.net doesn't actualize things > > well, and is different to make co or update (for a week!). > > > > I always use the SSH version (-d:ext:...). It's always up2date. The other > methods (pserver) are against backups, so older. I'm also using the SSH version. I've developed a serious flu so I'll be taking it easy for the day, we have to look at it asap tho. Thanks, Dennis |
|
From: Gustavo S. B. <gu...@gs...> - 2004-06-29 00:18:48
|
Em Sunday 27 June 2004 23:38, Duilio Javier Protti escreveu: > > I know i know, you're not understanding me! :) > > > > 1. Within the CVS directory I ran make dist. > > > > The resulting package I unpacked and did ./configure ; make in > > This is where i get errors regarding the .deps directory. Thus I can't > > release tonight :) It would be good if we could solve this tomorrow. > > > > Cheers, > > Dennis > > You make 'cvs co' or 'cvs update'? Because I have heard > somewhere that CVS on sf.net doesn't actualize things > well, and is different to make co or update (for a week!). > I always use the SSH version (-d:ext:...). It's always up2date. The other methods (pserver) are against backups, so older. - Gustavo Sverzut Barbieri --------------------------------------- Engenharia de Computacao 2001 - UNICAMP GPSL - Grupo Pro Software Livre Cell..: +55 (19) 9165 8010 Jabber: gsb...@ja... ICQ#: 17249123 GPG: 0xB640E1A2 @ wwwkeys.pgp.net |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-28 02:36:22
|
> I know i know, you're not understanding me! :) > > 1. Within the CVS directory I ran make dist. > > The resulting package I unpacked and did ./configure ; make in > This is where i get errors regarding the .deps directory. Thus I can't > release tonight :) It would be good if we could solve this tomorrow. > > Cheers, > Dennis You make 'cvs co' or 'cvs update'? Because I have heard somewhere that CVS on sf.net doesn't actualize things well, and is different to make co or update (for a week!). I suggest you try this (within your working directory): make distclean cvs update mkdir BUILD cd BUILD ../configure make make install I have take a look at the CVS, and the ./deps/* files are not there. I have tried the above and it works well. However, if you have any problem, I can send you a distro package for to make the release. Then we can keep trying to resolve the problem, even online as we did the other day, if you like. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-27 20:28:19
|
I know i know, you're not understanding me! :) 1. Within the CVS directory I ran make dist. The resulting package I unpacked and did ./configure ; make in This is where i get errors regarding the .deps directory. Thus I can't release tonight :) It would be good if we could solve this tomorrow. Cheers, Dennis On Sun, 2004-06-27 at 15:25 -0300, Duilio Javier Protti wrote: > > Well this was after doing make dist, untarring etc. As in this is the > > package that should be in the release... > > Oh, but you the people must not run autogen.sh! > autogen.sh script must not be on the distro package > at all. End users must only run ./configure. > > > Duilio. > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Libvisual-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libvisual-devel |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-27 18:55:56
|
I have added to lv_log.h the macro visual_log_return_if_fail(expr) and another returning a value. With this I have modified lv_video.c, and now XMMS plugin show some messages out there. Take a look. Duilio. |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-27 18:23:17
|
> I'm not sure about this, I do agree tho that we should > do extensive error checking using visual_log, I think > this should be sufficient and this way we don't have to > change the code. Maybe it's best tho to just use > return_if_null macro in which we can do an assert > temporarly. Ok, that's true, that way we need less code rewriting. I will see how that macro must be. Duilio. |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-27 18:23:13
|
> Well this was after doing make dist, untarring etc. As in this is the > package that should be in the release... Oh, but you the people must not run autogen.sh! autogen.sh script must not be on the distro package at all. End users must only run ./configure. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-27 16:09:51
|
Well this was after doing make dist, untarring etc. As in this is the package that should be in the release... On Sun, 2004-06-27 at 12:27 -0300, Duilio Javier Protti wrote: > > From a fresh checkout after doing: > > > > ./autogen.sh ; ./configure ; make dist > > > > Then extracting the package and running there ./configure ; make > > > > I'am having the following failures: > > > > bromodimethoxy:/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5# > > make > > cd . && /bin/sh ./config.status config.h > > config.status: creating config.h > > make all-recursive > > make[1]: Entering directory > > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5' > > Making all in libvisual > > make[2]: Entering directory > > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5/libvisual' > > Makefile:288: .deps/lv_actor.Plo: No such file or directory > > Makefile:289: .deps/lv_audio.Plo: No such file or directory > > Makefile:290: .deps/lv_bin.Plo: No such file or directory > > Makefile:291: .deps/lv_bmp.Plo: No such file or directory > > Makefile:292: .deps/lv_event.Plo: No such file or directory > > Makefile:293: .deps/lv_fft.Plo: No such file or directory > > Makefile:294: .deps/lv_input.Plo: No such file or directory > > Makefile:295: .deps/lv_keysym.Plo: No such file or directory > > Makefile:296: .deps/lv_libvisual.Plo: No such file or directory > > Makefile:297: .deps/lv_list.Plo: No such file or directory > > Makefile:298: .deps/lv_log.Plo: No such file or directory > > Makefile:299: .deps/lv_morph.Plo: No such file or directory > > Makefile:300: .deps/lv_palette.Plo: No such file or directory > > Makefile:301: .deps/lv_plugin.Plo: No such file or directory > > Makefile:302: .deps/lv_songinfo.Plo: No such file or directory > > Makefile:303: .deps/lv_video.Plo: No such file or directory > > make[2]: *** No rule to make target `.deps/lv_video.Plo'. Stop. > > make[2]: Leaving directory > > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5/libvisual' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory > > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5' > > make: *** [all] Error 2 > > > > > > Do you have any idea what is going wrong ? > > Yes, I known about this problem. The .deps directory must be > removed from the CVS, because it contains cached files. We must > remove every of the *.Plo files and after that we must update > and checkout with the -P option (prune option, this remove > directories that are empty after being updated). I have this on > my ~/.cvsrc: > > -z3 > update -dP > rdiff -u > diff -ubBwpN > checkout -P > > This makes life better :-) > > If you want to make the release, don't worry about the CVS for > now, just 'make dist' on your working copy, then untarred, then > configure/compile/install the fresh directory, and if everything > works well the release is ready. I have checked this way and > it works. > > > Duilio. > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Libvisual-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libvisual-devel |
|
From: Dennis S. <sy...@yo...> - 2004-06-27 16:05:01
|
On Sun, 2004-06-27 at 12:42 -0300, Duilio Javier Protti wrote:
> I think next step must be enforce all preconditions to
> catch bugs:
>
> int visual_some_thing (VisSome *vis)
> {
> if (vis == NULL)
> return -1;
> }
>
> must be changed for:
>
> int visual_some_thing (VisSome *vis)
> {
> assert (vis != NULL);
> ...
> }
I'm not sure about this, I do agree tho that we should
do extensive error checking using visual_log, I think
this should be sufficient and this way we don't have to
change the code. Maybe it's best tho to just use
return_if_null macro in which we can do an assert
temporarly.
> This way we can catch them early, before the bug
> propagate to obscure places. This is on the devel
> line and just for a while, to clean up things and
> to detect where the problems are, before to
> change the VisBin module or create the new param
> module.
> On the final release we will use a nice macro
> _lv_return_if_null(), as you suggest on the TODO
> list, that will show a critical warning but will
> not abort.
>
>
> Duilio.
|
|
From: Dennis S. <sy...@yo...> - 2004-06-27 15:52:26
|
Any other things I should keep in mind while releasing? --enable-examples and for libvisual-plugins enabling the disabled plugins right ? Cheers, Dennis On Sun, 2004-06-27 at 12:27 -0300, Duilio Javier Protti wrote: > -z3 > update -dP > rdiff -u > diff -ubBwpN > checkout -P |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-27 15:40:23
|
> Btw now you're getting more indepth with the system, how
> do you like the overall design ? ofcourse there are some
> rough edges here and there, both API, design and
> implementation wise...
I think the module design is perfect, however I have
not seen exhaustively the interface offered by every
module.
I think next step must be enforce all preconditions to
catch bugs:
int visual_some_thing (VisSome *vis)
{
if (vis == NULL)
return -1;
}
must be changed for:
int visual_some_thing (VisSome *vis)
{
assert (vis != NULL);
...
}
This way we can catch them early, before the bug
propagate to obscure places. This is on the devel
line and just for a while, to clean up things and
to detect where the problems are, before to
change the VisBin module or create the new param
module.
On the final release we will use a nice macro
_lv_return_if_null(), as you suggest on the TODO
list, that will show a critical warning but will
not abort.
Duilio.
|
|
From: Duilio J. P. <dp...@fc...> - 2004-06-27 15:24:57
|
> From a fresh checkout after doing: > > ./autogen.sh ; ./configure ; make dist > > Then extracting the package and running there ./configure ; make > > I'am having the following failures: > > bromodimethoxy:/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5# > make > cd . && /bin/sh ./config.status config.h > config.status: creating config.h > make all-recursive > make[1]: Entering directory > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5' > Making all in libvisual > make[2]: Entering directory > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5/libvisual' > Makefile:288: .deps/lv_actor.Plo: No such file or directory > Makefile:289: .deps/lv_audio.Plo: No such file or directory > Makefile:290: .deps/lv_bin.Plo: No such file or directory > Makefile:291: .deps/lv_bmp.Plo: No such file or directory > Makefile:292: .deps/lv_event.Plo: No such file or directory > Makefile:293: .deps/lv_fft.Plo: No such file or directory > Makefile:294: .deps/lv_input.Plo: No such file or directory > Makefile:295: .deps/lv_keysym.Plo: No such file or directory > Makefile:296: .deps/lv_libvisual.Plo: No such file or directory > Makefile:297: .deps/lv_list.Plo: No such file or directory > Makefile:298: .deps/lv_log.Plo: No such file or directory > Makefile:299: .deps/lv_morph.Plo: No such file or directory > Makefile:300: .deps/lv_palette.Plo: No such file or directory > Makefile:301: .deps/lv_plugin.Plo: No such file or directory > Makefile:302: .deps/lv_songinfo.Plo: No such file or directory > Makefile:303: .deps/lv_video.Plo: No such file or directory > make[2]: *** No rule to make target `.deps/lv_video.Plo'. Stop. > make[2]: Leaving directory > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5/libvisual' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5' > make: *** [all] Error 2 > > > Do you have any idea what is going wrong ? Yes, I known about this problem. The .deps directory must be removed from the CVS, because it contains cached files. We must remove every of the *.Plo files and after that we must update and checkout with the -P option (prune option, this remove directories that are empty after being updated). I have this on my ~/.cvsrc: -z3 update -dP rdiff -u diff -ubBwpN checkout -P This makes life better :-) If you want to make the release, don't worry about the CVS for now, just 'make dist' on your working copy, then untarred, then configure/compile/install the fresh directory, and if everything works well the release is ready. I have checked this way and it works. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-27 12:00:10
|
Duilio, >From a fresh checkout after doing: ./autogen.sh ; ./configure ; make dist Then extracting the package and running there ./configure ; make I'am having the following failures: bromodimethoxy:/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5# make cd . && /bin/sh ./config.status config.h config.status: creating config.h make all-recursive make[1]: Entering directory `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5' Making all in libvisual make[2]: Entering directory `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5/libvisual' Makefile:288: .deps/lv_actor.Plo: No such file or directory Makefile:289: .deps/lv_audio.Plo: No such file or directory Makefile:290: .deps/lv_bin.Plo: No such file or directory Makefile:291: .deps/lv_bmp.Plo: No such file or directory Makefile:292: .deps/lv_event.Plo: No such file or directory Makefile:293: .deps/lv_fft.Plo: No such file or directory Makefile:294: .deps/lv_input.Plo: No such file or directory Makefile:295: .deps/lv_keysym.Plo: No such file or directory Makefile:296: .deps/lv_libvisual.Plo: No such file or directory Makefile:297: .deps/lv_list.Plo: No such file or directory Makefile:298: .deps/lv_log.Plo: No such file or directory Makefile:299: .deps/lv_morph.Plo: No such file or directory Makefile:300: .deps/lv_palette.Plo: No such file or directory Makefile:301: .deps/lv_plugin.Plo: No such file or directory Makefile:302: .deps/lv_songinfo.Plo: No such file or directory Makefile:303: .deps/lv_video.Plo: No such file or directory make[2]: *** No rule to make target `.deps/lv_video.Plo'. Stop. make[2]: Leaving directory `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5/libvisual' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/libvis-newcvs/test-packages/libvisual-0.1.5' make: *** [all] Error 2 Do you have any idea what is going wrong ? |
|
From: Dennis S. <sy...@yo...> - 2004-06-27 11:13:12
|
Duilio I'd like to point out that you've got tracker admin permissions, so feel free to add categories :) Also, I think CVS is now near final for the new release, could you do some final testing as well ? Cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-06-27 09:41:38
|
Wow thanks a lot! On Sun, 2004-06-27 at 02:59 -0300, Duilio Javier Protti wrote: > > Do you know if we can use a format string within the visual_log debug > > macro. I've tried todo this but failed, could you have a look at it ? > > I have submitted that stuff. After checkout and compile > LibVisual, recompile also the XMMS plugin, because > visual_log() works by macro expansion. > > > Enjoy it. > Duilio. |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-27 05:57:45
|
> Do you know if we can use a format string within the visual_log debug > macro. I've tried todo this but failed, could you have a look at it ? I have submitted that stuff. After checkout and compile LibVisual, recompile also the XMMS plugin, because visual_log() works by macro expansion. Enjoy it. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-26 22:14:19
|
Duilio, Do you know if we can use a format string within the visual_log debug macro. I've tried todo this but failed, could you have a look at it ? Thanks, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-06-26 22:12:47
|
Duilio,
visual_video_depth_enum_from_value
In the xmms plugin within the visual_initialize
function you use:
switch (lv_depth) {
case 8:
depth = VISUAL_VIDEO_DEPTH_8BIT;
case 16:
depth = VISUAL_VIDEO_DEPTH_16BIT;
case 24:
depth = VISUAL_VIDEO_DEPTH_24BIT;
case 32:
depth = VISUAL_VIDEO_DEPTH_32BIT;
break;
default:
depth = lv_depth = VISUAL_VIDEO_DEPTH_24BIT;
break;
}
I'd like to point out that libvisual has a function:
visual_video_depth_enum_from_value that does this.
Dennis
|
|
From: Dennis S. <sy...@yo...> - 2004-06-26 21:59:15
|
On Sat, 2004-06-26 at 16:40 -0300, Duilio Javier Protti wrote: > I have submitted many things to plugins package. > > Before to ckeckout, run 'make distclean', then > checkout, then run autogen.sh. > > > Duilio. Cool. thanks a lot! :) Btw now you're getting more indepth with the system, how do you like the overall design ? ofcourse there are some rough edges here and there, both API, design and implementation wise... |
|
From: Dennis S. <sy...@yo...> - 2004-06-26 21:52:39
|
On Sat, 2004-06-26 at 14:50 -0300, Duilio Javier Protti wrote: > I have updated the NEWS on XMMS plugin. > > Dennis, don't forget to remove autogen.sh > from Makefile.am:EXTRA_DIST before to make > releases, because end users don't want this > script, it is just for CVS bootstrapping. > > > Duilio. Thanks for updating the NEWS file, why is it in EXTRA_DIST in the first place ? Dennis |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-26 19:38:11
|
I have submitted many things to plugins package. Before to ckeckout, run 'make distclean', then checkout, then run autogen.sh. Duilio. |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-26 17:47:56
|
I have updated the NEWS on XMMS plugin. Dennis, don't forget to remove autogen.sh from Makefile.am:EXTRA_DIST before to make releases, because end users don't want this script, it is just for CVS bootstrapping. Duilio. |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-26 17:16:13
|
> We might start on thinking about 0.1.6, > > Do you have any ideas for the versioning system ?, besides that I > personally want to land the param system and do some plugin stuff. The versioning system will take us just a couple of days. Technically is simple to resolve, but we must decide how to make evolve the versions. To understand the libtool notion of versioning, I send you attached a fragment of the libtool documentation. I really recommend you to read it, the question is explained very clear there. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-26 09:49:24
|
On Fri, 2004-06-25 at 20:31 -0300, Duilio Javier Protti wrote: > > * Create NEWS files. > > Very important. > > According to GNU standards, NEWS file must talk about user visible > changes made in the software. In the case of libvisual itself, users > are developers, but NEWS must talk about changes on the interface or > buiding process, or a major performance improvement, not changes in > the code (which are in ChangeLog). Thanks for the information, I didn't knew that GNU has real standards for this! You don't have any items to add to the list of things TODO before sunday right ? We might start on thinking about 0.1.6, Do you have any ideas for the versioning system ?, besides that I personally want to land the param system and do some plugin stuff. Cheers, Dennis |
10 messages has been excluded from this view by a project administrator.
