You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(3) |
Oct
(3) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
(3) |
Dec
(5) |
| 2011 |
Jan
(14) |
Feb
|
Mar
(26) |
Apr
(7) |
May
(10) |
Jun
(6) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(26) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2013 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
(2) |
May
(19) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alejandro M. <am...@ge...> - 2013-05-21 11:52:42
|
El 21/05/2013 13:42, "Angelo GIRARDI" <ang...@sw...> escribió: > > Ok, but how do I need to use git to upload a "tgz" file. you don't upload snapshot blobs to the source repos. you make a tag. |
|
From: Angelo G. <ang...@sw...> - 2013-05-21 11:42:28
|
Ok, but how do I need to use git to upload a "tgz" file. Thanks On 21/05/13 13:20, Alejandro Mery wrote: > > please. use git > > El 21/05/2013 13:07, "Angelo GIRARDI" <ang...@sw... > <mailto:ang...@sw...>> escribió: > > On 21/05/13 10:40, Alejandro Mery wrote: > > > it's no "my" version, I only turned the CVS Uri left into git > and fixed bug together with other devs. > > > Do not bother, all my source files (*.c, *.prg, *.y,..) are token > from clip-itk. > I just update clip-prg.32-64 branch. > > Have a look at the structure. > Would you try just a little command from clip-prg.32.64.src > directory : > > $kwrite */clip/*/Makefile* > > or > > $gedit */clip/*/Makefile* > > > doing it this way nothing will be lost and it will be simple > to see the changes. > > I'm available to answer all your git or vcs question. > > Thanks. > > > I just pushed a new version clip-prg.32-64 for detailed files. > > But, I do not know how to push for tgz file as you did it for me once. > > > By the way, I think that I better have to move prg/debug to > clip/debug. > > > Regards > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance > monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! > http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > clip-itk-devel mailing list > cli...@li... > <mailto:cli...@li...> > https://lists.sourceforge.net/lists/listinfo/clip-itk-devel > |
|
From: Alejandro M. <am...@ge...> - 2013-05-21 11:20:09
|
please. use git El 21/05/2013 13:07, "Angelo GIRARDI" <ang...@sw...> escribió: > On 21/05/13 10:40, Alejandro Mery wrote: > >> >> it's no "my" version, I only turned the CVS Uri left into git and fixed >> bug together with other devs. >> >> > Do not bother, all my source files (*.c, *.prg, *.y,..) are token from > clip-itk. > I just update clip-prg.32-64 branch. > > Have a look at the structure. > Would you try just a little command from clip-prg.32.64.src directory : > > $kwrite */clip/*/Makefile* > > or > > $gedit */clip/*/Makefile* > > > doing it this way nothing will be lost and it will be simple to see the >> changes. >> >> I'm available to answer all your git or vcs question. >> >> Thanks. > > > I just pushed a new version clip-prg.32-64 for detailed files. > > But, I do not know how to push for tgz file as you did it for me once. > > > By the way, I think that I better have to move prg/debug to clip/debug. > > > Regards > > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > clip-itk-devel mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clip-itk-devel > > |
|
From: Angelo G. <ang...@sw...> - 2013-05-21 11:07:18
|
On 21/05/13 10:40, Alejandro Mery wrote: > > it's no "my" version, I only turned the CVS Uri left into git and > fixed bug together with other devs. > Do not bother, all my source files (*.c, *.prg, *.y,..) are token from clip-itk. I just update clip-prg.32-64 branch. Have a look at the structure. Would you try just a little command from clip-prg.32.64.src directory : $kwrite */clip/*/Makefile* or $gedit */clip/*/Makefile* > doing it this way nothing will be lost and it will be simple to see > the changes. > > I'm available to answer all your git or vcs question. > Thanks. I just pushed a new version clip-prg.32-64 for detailed files. But, I do not know how to push for tgz file as you did it for me once. By the way, I think that I better have to move prg/debug to clip/debug. Regards |
|
From: Alejandro M. <am...@ge...> - 2013-05-21 08:40:42
|
it's no "my" version, I only turned the CVS Uri left into git and fixed bug together with other devs. clone what's on the master of sf's bit. make a local branch, do the `git mv` and the changes needed to the current build system to support those relocations (nothing 32/64 related please), and push that branch (with a meaningful name) for review/comments. doing it this way nothing will be lost and it will be simple to see the changes. I'm available to answer all your git or vcs question. El 21/05/2013 10:30, "Angelo GIRARDI" <ang...@sw...> escribió: > On 21/05/13 00:19, Alejandro Mery wrote: > >> On 20 May 2013 10:25, Angelo GIRARDI <ang...@sw...> wrote: >> >>> Hi Alejandro, >>> >>> >>> On 19/05/13 17:55, Alejandro Mery wrote: >>> >>>> On 19/05/13 11:08, Angelo GIRARDI wrote: >>>> >>>>> Hi All, >>>>> >>>>> I did not succeed to port Clip-ITK packages to "auto tools". >>>>> >>>>> There are too many dependencies. Or, maybe, I did not follow the right >>>>> way to do it. >>>>> >>>>> iirc the idea was first to reorder the tree before trying to port it >>>> to >>>> autotools... only a bunch of `git mv` and the minimal required changes >>>> to the current build system to make it work. >>>> >>> You did not have had a look to my structure. >>> >>> *once* ported all the prefix/arch/packaging voodoo will be much simpler >>>> to do. refactoring works because things are done in baby steps ;-) >>>> >>> You always answer that, but none worked on it. Just have a look to my >>> version. >>> >>> >>> making yet another custom/hackish/broken build system is a bad idea. >>>> >>> >>> As anybody did make one step, I change all the "bunch". >>> Just try my version >>> >> please, for everyone's sanity, use the git repo and git mv instead of >> dumping tarballs of your local dirs :( >> >> > Sorry, I forget that there is a separate branch. > > > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > clip-itk-devel mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clip-itk-devel > > |
|
From: Angelo G. <ang...@sw...> - 2013-05-21 08:30:32
|
On 21/05/13 00:19, Alejandro Mery wrote: > On 20 May 2013 10:25, Angelo GIRARDI <ang...@sw...> wrote: >> Hi Alejandro, >> >> >> On 19/05/13 17:55, Alejandro Mery wrote: >>> On 19/05/13 11:08, Angelo GIRARDI wrote: >>>> Hi All, >>>> >>>> I did not succeed to port Clip-ITK packages to "auto tools". >>>> >>>> There are too many dependencies. Or, maybe, I did not follow the right >>>> way to do it. >>>> >>> iirc the idea was first to reorder the tree before trying to port it to >>> autotools... only a bunch of `git mv` and the minimal required changes >>> to the current build system to make it work. >> You did not have had a look to my structure. >> >>> *once* ported all the prefix/arch/packaging voodoo will be much simpler >>> to do. refactoring works because things are done in baby steps ;-) >> You always answer that, but none worked on it. Just have a look to my >> version. >> >> >>> making yet another custom/hackish/broken build system is a bad idea. >> >> As anybody did make one step, I change all the "bunch". >> Just try my version > please, for everyone's sanity, use the git repo and git mv instead of > dumping tarballs of your local dirs :( > Sorry, I forget that there is a separate branch. |
|
From: Angelo G. <ang...@sw...> - 2013-05-21 08:01:31
|
Hi All, I have uploaded my last version 1.2.6.06.03.03 to SourceForge. http://sourceforge.net/projects/clip-itk This is for the moment still a "user" version. I hope that the next version will be system wide. Regards. Angelo |
|
From: Alejandro M. <am...@ge...> - 2013-05-20 22:45:53
|
On 20 May 2013 10:25, Angelo GIRARDI <ang...@sw...> wrote: > Hi Alejandro, > > > On 19/05/13 17:55, Alejandro Mery wrote: >> >> On 19/05/13 11:08, Angelo GIRARDI wrote: >>> >>> Hi All, >>> >>> I did not succeed to port Clip-ITK packages to "auto tools". >>> >>> There are too many dependencies. Or, maybe, I did not follow the right >>> way to do it. >>> >> iirc the idea was first to reorder the tree before trying to port it to >> autotools... only a bunch of `git mv` and the minimal required changes >> to the current build system to make it work. > > You did not have had a look to my structure. > >> >> *once* ported all the prefix/arch/packaging voodoo will be much simpler >> to do. refactoring works because things are done in baby steps ;-) > > You always answer that, but none worked on it. Just have a look to my > version. > > >> >> making yet another custom/hackish/broken build system is a bad idea. > > > As anybody did make one step, I change all the "bunch". > Just try my version please, for everyone's sanity, use the git repo and git mv instead of dumping tarballs of your local dirs :( |
|
From: Alejandro M. <am...@ge...> - 2013-05-20 13:07:16
|
On 20/05/13 10:28, Angelo GIRARDI wrote:
> On 19/05/13 22:20, Angelo GIRARDI wrote:
>> On 19/05/13 17:43, Alejandro Mery wrote:
>>> On 19/05/13 14:07, Angelo GIRARDI wrote:
>>>> Hi All,
>>>>
>>>> In file ./clip/clip.c or ./clip/compiler/clip.c :
>>>>
>>>> You should replace line 1211 :
>>>>
>>>> <cut/>
>>>> yywarning("possible not defined function %s", s);
>>>>
>>>> </cut>
>>>>
>>>> *by*
>>>>
>>>> yyerrror("possible not defined function %s", s);
>>>>
>>>>
>>>> Will reserve some surprises.
>>> diffs are more useful ;-) like:
>>> diff --git a/clip/clip.c b/clip/clip.c
>>> index a73ce3e..42fbe7d 100644
>>> --- a/clip/clip.c
>>> +++ b/clip/clip.c
>>> @@ -1208,7 +1208,7 @@ check_names(Coll * ex, Coll * nm)
>>>
>>> s = (char *) ex->items[i];
>>> if (!search_Coll(nm, s, &no))
>>> - yywarning("possible not defined function %s",
>>> s);
>>> + yyerror("possible not defined function %s", s);
>>> }
>>> }
>>>
>>>
>>> but... won't this break dynamic loading when composing different modules
>>> after compiling them separated? I haven't used clip/harbour/clipper in a
>>> pretty long time, but that used to be quite common practice.
>>>
>>> cheers,
>>> Alejandro
>>>
>>>
>> Hi Alejandro,
>>
>> That is a suggestion.
>>
>> I test it on compiling and/or linking and it has the same result.
>>
>> It gives the name of the not define function at compile time, not at
>> runtime.
>>
>> But, it will be very helpful to get an error message instead of
>> warning message.
>>
>> For a conditional compile, it make an exit 1 from Makefile files, that
>> is just a suggestion.
>>
>> I will use it because normally all functions have to be defined at
>> link time.
>>
>> Regards
>>
>> Angelo
>>
>
> Hi All,
>
> I think that it is better to have an error at link time than at run time.
>
> Cheers.
ok :) commited as 13662f1cbbfc37215f52711a39028beb3020b13c
http://clip-itk.git.sourceforge.net/git/gitweb.cgi?p=clip-itk/clip-itk;a=commitdiff;h=13662f1cbbfc37215f52711a39028beb3020b13c
cheers,
Alejandro Mery
|
|
From: Алексей К. <us...@ci...> - 2013-05-20 09:37:30
|
"I think that it is better to have an error at link time than at run time." --- agree ! -- Kozlov Alex V. 8-0162-238650 8-029-2220835 www.cis.by <bo...@ci...> bo...@ci... icq 242491317 Skype AxelF_61 |
|
From: Angelo G. <ang...@sw...> - 2013-05-20 08:28:21
|
On 19/05/13 22:20, Angelo GIRARDI wrote:
> On 19/05/13 17:43, Alejandro Mery wrote:
>> On 19/05/13 14:07, Angelo GIRARDI wrote:
>>> Hi All,
>>>
>>> In file ./clip/clip.c or ./clip/compiler/clip.c :
>>>
>>> You should replace line 1211 :
>>>
>>> <cut/>
>>> yywarning("possible not defined function %s", s);
>>>
>>> </cut>
>>>
>>> *by*
>>>
>>> yyerrror("possible not defined function %s", s);
>>>
>>>
>>> Will reserve some surprises.
>> diffs are more useful ;-) like:
>> diff --git a/clip/clip.c b/clip/clip.c
>> index a73ce3e..42fbe7d 100644
>> --- a/clip/clip.c
>> +++ b/clip/clip.c
>> @@ -1208,7 +1208,7 @@ check_names(Coll * ex, Coll * nm)
>>
>> s = (char *) ex->items[i];
>> if (!search_Coll(nm, s, &no))
>> - yywarning("possible not defined function %s",
>> s);
>> + yyerror("possible not defined function %s", s);
>> }
>> }
>>
>>
>> but... won't this break dynamic loading when composing different modules
>> after compiling them separated? I haven't used clip/harbour/clipper in a
>> pretty long time, but that used to be quite common practice.
>>
>> cheers,
>> Alejandro
>>
>>
> Hi Alejandro,
>
> That is a suggestion.
>
> I test it on compiling and/or linking and it has the same result.
>
> It gives the name of the not define function at compile time, not at
> runtime.
>
> But, it will be very helpful to get an error message instead of
> warning message.
>
> For a conditional compile, it make an exit 1 from Makefile files, that
> is just a suggestion.
>
> I will use it because normally all functions have to be defined at
> link time.
>
> Regards
>
> Angelo
>
Hi All,
I think that it is better to have an error at link time than at run time.
Cheers.
Angelo
|
|
From: Angelo G. <ang...@sw...> - 2013-05-20 08:25:49
|
Hi Alejandro, On 19/05/13 17:55, Alejandro Mery wrote: > On 19/05/13 11:08, Angelo GIRARDI wrote: >> Hi All, >> >> I did not succeed to port Clip-ITK packages to "auto tools". >> >> There are too many dependencies. Or, maybe, I did not follow the right >> way to do it. >> > iirc the idea was first to reorder the tree before trying to port it to > autotools... only a bunch of `git mv` and the minimal required changes > to the current build system to make it work. You did not have had a look to my structure. > > *once* ported all the prefix/arch/packaging voodoo will be much simpler > to do. refactoring works because things are done in baby steps ;-) You always answer that, but none worked on it. Just have a look to my version. > > making yet another custom/hackish/broken build system is a bad idea. As anybody did make one step, I change all the "bunch". Just try my version Cheers. Angelo |
|
From: Angelo G. <ang...@sw...> - 2013-05-19 20:20:51
|
On 19/05/13 17:43, Alejandro Mery wrote:
> On 19/05/13 14:07, Angelo GIRARDI wrote:
>> Hi All,
>>
>> In file ./clip/clip.c or ./clip/compiler/clip.c :
>>
>> You should replace line 1211 :
>>
>> <cut/>
>> yywarning("possible not defined function %s", s);
>>
>> </cut>
>>
>> *by*
>>
>> yyerrror("possible not defined function %s", s);
>>
>>
>> Will reserve some surprises.
> diffs are more useful ;-) like:
> diff --git a/clip/clip.c b/clip/clip.c
> index a73ce3e..42fbe7d 100644
> --- a/clip/clip.c
> +++ b/clip/clip.c
> @@ -1208,7 +1208,7 @@ check_names(Coll * ex, Coll * nm)
>
> s = (char *) ex->items[i];
> if (!search_Coll(nm, s, &no))
> - yywarning("possible not defined function %s", s);
> + yyerror("possible not defined function %s", s);
> }
> }
>
>
> but... won't this break dynamic loading when composing different modules
> after compiling them separated? I haven't used clip/harbour/clipper in a
> pretty long time, but that used to be quite common practice.
>
> cheers,
> Alejandro
>
>
Hi Alejandro,
That is a suggestion.
I test it on compiling and/or linking and it has the same result.
It gives the name of the not define function at compile time, not at
runtime.
But, it will be very helpful to get an error message instead of warning
message.
For a conditional compile, it make an exit 1 from Makefile files, that
is just a suggestion.
I will use it because normally all functions have to be defined at link
time.
Regards
Angelo
|
|
From: Alejandro M. <am...@ge...> - 2013-05-19 16:09:20
|
On 19/05/13 14:07, Angelo GIRARDI wrote:
> Hi All,
>
> In file ./clip/clip.c or ./clip/compiler/clip.c :
>
> You should replace line 1211 :
>
> <cut/>
> yywarning("possible not defined function %s", s);
>
> </cut>
>
> *by*
>
> yyerrror("possible not defined function %s", s);
>
>
> Will reserve some surprises.
diffs are more useful ;-) like:
diff --git a/clip/clip.c b/clip/clip.c
index a73ce3e..42fbe7d 100644
--- a/clip/clip.c
+++ b/clip/clip.c
@@ -1208,7 +1208,7 @@ check_names(Coll * ex, Coll * nm)
s = (char *) ex->items[i];
if (!search_Coll(nm, s, &no))
- yywarning("possible not defined function %s", s);
+ yyerror("possible not defined function %s", s);
}
}
but... won't this break dynamic loading when composing different modules
after compiling them separated? I haven't used clip/harbour/clipper in a
pretty long time, but that used to be quite common practice.
cheers,
Alejandro
|
|
From: Alejandro M. <am...@ge...> - 2013-05-19 16:00:29
|
On 19/05/13 11:08, Angelo GIRARDI wrote: > Hi All, > > I did not succeed to port Clip-ITK packages to "auto tools". > > There are too many dependencies. Or, maybe, I did not follow the right > way to do it. > iirc the idea was first to reorder the tree before trying to port it to autotools... only a bunch of `git mv` and the minimal required changes to the current build system to make it work. *once* ported all the prefix/arch/packaging voodoo will be much simpler to do. refactoring works because things are done in baby steps ;-) making yet another custom/hackish/broken build system is a bad idea. cheers, Alejandro Mery |
|
From: Angelo G. <ang...@sw...> - 2013-05-19 12:07:36
|
Hi All,
In file ./clip/clip.c or ./clip/compiler/clip.c :
You should replace line 1211 :
<cut/>
yywarning("possible not defined function %s", s);
</cut>
*by*
yyerrror("possible not defined function %s", s);
Will reserve some surprises.
Regards.
Angelo
|
|
From: Angelo G. <ang...@sw...> - 2013-05-19 09:08:45
|
Hi All,
I did not succeed to port Clip-ITK packages to "auto tools".
There are too many dependencies. Or, maybe, I did not follow the right
way to do it.
So, I suggest know to move to common"rpm/deb" packages as follow :
xxx is the version number.
nnn is the library name.
*1.* *System wide architecture* :
/usr/bin/clip(32/64)/*bin (we would have to manage PATH search);
*or* /usr/local/bin/clip(32/64)/*bin (we would have to manage PATH search);
*or* /opt/clip(32/64)/bin ../lib ... (we would have to manage PATH search);
*or very much better*
/usr/bin/clip(32/64) & all bin files ... as any common compiler(s) and tools
/usr/lib/lib32clip.xxx.nnn.a/so
/usr/lib64/lib64clip.xxx.nnn
/usr/include/clip-itk/*.ch *.h
*2. Source **packages* for clip-itk developers :
to common development directory /usr/src/clip-itk/clip-xxx/
2.1. clip-xxx-src.rpm will contain clip and prg directories source files.
2.2. libclip-nnn-xxx-src.rpm will contain each sub-directory from
libclips and libclip-codbsource files.
*3. User packages* for clip-itk application(s) development and use:
3.1. clip-xxx-(32/64).rpm will contain compiler.
3.2. clip-xxx-utils(32/64).rpm will contain tools.
3.3. lib(32/64)clip-xxx.rpm will contain run-time library.
3.2. lib(32/64)clip-xxx-nnn.rpm will contain run-time library.
Any comment(s), advise(s) or ... are welcome.
Regards
Angelo
|
|
From: Angelo G. <ang...@sw...> - 2013-05-01 10:55:19
|
Hi All, clip-gtk2 examples work fine. Thanks a lot. Regards. Angelo On 01/05/13 12:00, Angelo GIRARDI wrote: > Thanks. > > I will try it. > > Regards. > > Angelo > > On 30/04/13 17:10, Soporte - Estilo Informática wrote: >> >> Hi Angelo, i'm only use ncurses, but make sample >> >> clip/cliplibs/clip-gtk2/example and run without problems >> >> The binary file to run is clipgtktest >> >> Regards >> >> Ricardo Brisighelli >> >> El Mar 30 Abr 2013 08:30:31 Angelo GIRARDI escribió: >> >> > Hi All, >> >> > >> >> > Does anybody succeed in developing and running a graphic application >> >> > with clip-ITK? >> >> > >> >> > If, Yes. Would you let me know your running environment and Makefile? >> >> > >> >> > Thanks. >> >> > >> >> > Regards. >> >> > >> >> > Angelo >> >> > >> >> > >> >> > >> >> > !DSPAM:517f6d99110141581349206! >> >> >> >> ------------------------------------------------------------------------------ >> >> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET >> Get 100% visibility into your production application - at no cost. >> Code-level diagnostics for performance bottlenecks with <2% overhead >> Download for free and get started troubleshooting in minutes. >> http://p.sf.net/sfu/appdyn_d2d_ap1 >> >> >> _______________________________________________ >> clip-itk-devel mailing list >> cli...@li... >> https://lists.sourceforge.net/lists/listinfo/clip-itk-devel > > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > > > _______________________________________________ > clip-itk-devel mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clip-itk-devel |
|
From: Angelo G. <ang...@sw...> - 2013-05-01 10:00:17
|
Thanks. I will try it. Regards. Angelo On 30/04/13 17:10, Soporte - Estilo Informática wrote: > > Hi Angelo, i'm only use ncurses, but make sample > > clip/cliplibs/clip-gtk2/example and run without problems > > The binary file to run is clipgtktest > > Regards > > Ricardo Brisighelli > > El Mar 30 Abr 2013 08:30:31 Angelo GIRARDI escribió: > > > Hi All, > > > > > > Does anybody succeed in developing and running a graphic application > > > with clip-ITK? > > > > > > If, Yes. Would you let me know your running environment and Makefile? > > > > > > Thanks. > > > > > > Regards. > > > > > > Angelo > > > > > > > > > > > > !DSPAM:517f6d99110141581349206! > > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > > > _______________________________________________ > clip-itk-devel mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clip-itk-devel |
|
From: Soporte - E. I. <so...@es...> - 2013-04-30 15:47:51
|
Hi Angelo, i'm only use ncurses, but make sample clip/cliplibs/clip-gtk2/example and run without problems The binary file to run is clipgtktest Regards Ricardo Brisighelli El Mar 30 Abr 2013 08:30:31 Angelo GIRARDI escribió: > Hi All, > > Does anybody succeed in developing and running a graphic application > with clip-ITK? > > If, Yes. Would you let me know your running environment and Makefile? > > Thanks. > > Regards. > > Angelo > > > > !DSPAM:517f6d99110141581349206! |
|
From: Angelo G. <ang...@sw...> - 2013-04-30 07:06:25
|
Hi All, Does anybody succeed in developing and running a graphic application with clip-ITK? If, Yes. Would you let me know your running environment and Makefile? Thanks. Regards. Angelo |
|
From: Alejandro M. <am...@ge...> - 2013-02-28 10:54:51
|
On 26 February 2013 04:21, Angelo GIRARDI <ang...@sw...> wrote: > Hi all, > > I received some times ago a message about an update about 32 or 64 bits > access but I do not remember in which file. > > I could not find the message in my history. > > Does anybody still have a copy of this update? > > It was made under cvs and I need the update references or the name of the > file. no idea what "update" you mean, but everything in the cvs was imported into the git tree. |
|
From: Angelo G. <ang...@sw...> - 2013-02-26 03:23:15
|
Hi all, I received some times ago a message about an update about 32 or 64 bits access but I do not remember in which file. I could not find the message in my history. Does anybody still have a copy of this update? It was made under cvs and I need the update references or the name of the file. Thanks. Regards Angelo |
|
From: Soporte - E. I. <so...@es...> - 2013-01-30 10:59:00
|
I'm Gentoo user and installed missing programs (many for my, not needed in the original branch) but always some fail. Example libiconv test. Regards Ricardo Brisighelli On Sáb 26 Ene 2013 03:06:13 Angelo GIRARDI escribió: > Hi, all > > Would everybody let me know on which version of OS you work for development? > > I found out that there are many packages differences between 2 > Linux's.(names, contains and dependencies) > > So, I have to know your OS version to install the different versions on > my PC to test the different abilities. > > Regards > > Angelo |
|
From: Angelo G. <ang...@sw...> - 2013-01-26 02:06:22
|
Hi, all Would everybody let me know on which version of OS you work for development? I found out that there are many packages differences between 2 Linux's.(names, contains and dependencies) So, I have to know your OS version to install the different versions on my PC to test the different abilities. Regards Angelo |