From a.janke at gmail.com Wed Jun 3 06:27:30 2009 From: a.janke at gmail.com (Andrew Janke) Date: Wed, 3 Jun 2009 20:27:30 +1000 Subject: [MINC-development] MINC2 and required NetCDF version In-Reply-To: <20090527194841.1152052413@kingu.local> References: <20090527183204.812119703@kingu.local> <20090527194841.1152052413@kingu.local> Message-ID: Hi Sean, >>/* Maximum number of icv's allowed */ >>#define MI_MAX_NUM_ICV MAX_NC_OPEN >> >>Maybe this could just be changed to 32 (NetCDF's old value)? > > Actually, it's used elsewhere too... If I #define MAX_NC_OPEN 32 just > after the #include in minc.h then compilation succeeds. First why 4.x? :) unidata still distribute 3.6.x and I think they will for a while yet. As it is the 4.x version is not in debian that I can see. :( Anyhow I would prefer something like this: /* hack to get around netcdf 3.x -> 4x. */ #ifndef MAX_NC_OPEN #define MI_MAX_NUM_ICV 32 #else #define MI_MAX_NUM_ICV MAX_NC_OPEN #endif. Can you test this please? if it works fine I can commit this to CVS. -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From sean at rogue-research.com Wed Jun 3 09:14:48 2009 From: sean at rogue-research.com (Sean McBride) Date: Wed, 3 Jun 2009 09:14:48 -0400 Subject: [MINC-development] MINC2 and required NetCDF version In-Reply-To: References: <20090527183204.812119703@kingu.local> <20090527194841.1152052413@kingu.local> Message-ID: <20090603131448.766792806@kingu.local> On 6/3/09 8:27 PM, Andrew Janke said: >>>/* Maximum number of icv's allowed */ >>>#define MI_MAX_NUM_ICV MAX_NC_OPEN >>> >>>Maybe this could just be changed to 32 (NetCDF's old value)? >> >> Actually, it's used elsewhere too... If I #define MAX_NC_OPEN 32 just >> after the #include in minc.h then compilation succeeds. > >First why 4.x? :) For the same reason I'm not using MINC 1.x. :) >unidata still distribute 3.6.x and I think they >will for a while yet. As it is the 4.x version is not in debian that I >can see. :( > >Anyhow I would prefer something like this: > >/* hack to get around netcdf 3.x -> 4x. */ >#ifndef MAX_NC_OPEN >#define MI_MAX_NUM_ICV 32 >#else >#define MI_MAX_NUM_ICV MAX_NC_OPEN >#endif. > >Can you test this please? if it works fine I can commit this to CVS. That would work great. I had actually done that (though without the else) in a previous test. However, one could argue that since MAX_NC_OPEN is gone from NetCDF (I searched the whole NetCDF 3.6.3 source tree and MAX_NC_OPEN appears only where it's defined, in other words, it's deprecated in 3.x also.) that it would be better to purge MINC of this constant. Its current value of 32 will never change. BTW, everything seems to be working fine built against 4.0.1. -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From sean at rogue-research.com Wed Jun 3 09:34:19 2009 From: sean at rogue-research.com (Sean McBride) Date: Wed, 3 Jun 2009 09:34:19 -0400 Subject: [MINC-development] MINC2 and required NetCDF version In-Reply-To: <20090603131448.766792806@kingu.local> References: <20090527183204.812119703@kingu.local> <20090527194841.1152052413@kingu.local> <20090603131448.766792806@kingu.local> Message-ID: <20090603133419.1947013960@kingu.local> On 6/3/09 9:14 AM, Sean McBride said: >>Anyhow I would prefer something like this: >> >>/* hack to get around netcdf 3.x -> 4x. */ >>#ifndef MAX_NC_OPEN >>#define MI_MAX_NUM_ICV 32 >>#else >>#define MI_MAX_NUM_ICV MAX_NC_OPEN >>#endif. >> >>Can you test this please? if it works fine I can commit this to CVS. > >That would work great. I had actually done that (though without the >else) in a previous test. Ack. I misread, sorry. What I tried was: #ifndef MAX_NC_OPEN #define MAX_NC_OPEN 32 #endif. Your proposal is insufficient since MAX_NC_OPEN is used not only to define MI_MAX_NUM_ICV but used elsewhere too. -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From a.janke at gmail.com Thu Jun 4 07:43:23 2009 From: a.janke at gmail.com (Andrew Janke) Date: Thu, 4 Jun 2009 21:43:23 +1000 Subject: [MINC-development] MINC2 and required NetCDF version In-Reply-To: <20090603131448.766792806@kingu.local> References: <20090527183204.812119703@kingu.local> <20090527194841.1152052413@kingu.local> <20090603131448.766792806@kingu.local> Message-ID: >>First why 4.x? :) > > For the same reason I'm not using MINC 1.x. :) Orright, point taken... > That would work great. ?I had actually done that (though without the > else) in a previous test. > > However, one could argue that since MAX_NC_OPEN is gone from NetCDF (I > searched the whole NetCDF 3.6.3 source tree and MAX_NC_OPEN appears only > where it's defined, in other words, it's deprecated in 3.x also.) that > it would be better to purge MINC of this constant. ?Its current value of > 32 will never change. True and from a search of the CVS tree (not only of MINC) no-one else seems to have ever used it. Still it _does_ have a use and predominately in voxel_loop which things like mincaverage use. In this case removing it will have nasty effects specifically in things like mincaverage. Take the case of where you are averaging 2000 files and you attempt to open the first chunk of all of them. Before you realise it you are out of RAM... Mind you this is somewhat broken with HDF files anyhow but that is another issue. So from a dig in the code the only problem I see in removing it is here: libsrc/image_conversion.c: 218 /* How much space will be needed? */ 219 new_nalloc = minc_icv_list_nalloc + MI_MAX_NUM_ICV; In which the list of open icvids is dynamically increased with realloc. So we could probably just change this to 1 or 10 if we want to kid ourselves that this will optimise something. Still if we do this I would prefer to keep the limit (of 32 or something like it) in voxel_loop.c Claude? Your proposal is insufficient since MAX_NC_OPEN is used not only to define MI_MAX_NUM_ICV but used elsewhere too. True, if we remove it though it is all sort of moot.. :) -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From anthonin at bic.mni.mcgill.ca Thu Jun 4 16:52:16 2009 From: anthonin at bic.mni.mcgill.ca (Anthonin REILHAC) Date: Thu, 4 Jun 2009 16:52:16 -0400 Subject: [MINC-development] MINC1/MINC2 Message-ID: Hello everybody, I am just about to start developping codes using the minc lib (opening/treating/saving in a new file). I am (was) a bit familiar with the minc1 interface, but a bit confused now that minc2 is here. What programming interface should I be using considering that the input files my codes will read will be minc{1,2} and considering that I would like to save in minc{1,2}? In other words, should I re-read the MINC 1.0 Programmers Reference or get familiar with MINC 2.0 Reference Manual? I guess that this question is often asked, and maybe the answer is written somewhere on the wiki pages. Thanks in advance. Anthonin Reilhac McConnell Brain Imaging Centre, WB2B Montreal Neurological Institute 3801 University Montreal, Quebec, Canada phone: (514) 398 4965 From a.janke at gmail.com Thu Jun 4 18:52:52 2009 From: a.janke at gmail.com (Andrew Janke) Date: Fri, 5 Jun 2009 08:52:52 +1000 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: Hi Anthonin, On Fri, Jun 5, 2009 at 06:52, Anthonin REILHAC wrote: > I am just about to start developping codes using the minc lib > (opening/treating/saving in a new file). I am (was) a bit familiar with > the minc1 interface, but a bit confused now that minc2 is here. What > programming interface should I be using considering that the input files > my codes will read will be minc{1,2} and considering that I would like to > save in minc{1,2}? I would definitely use the MINC2 API it can read MINC 1 and 2. You can also force the API to write out old MINC1 files if you want to. I would suggest you look at some of the tutorials that Jason Lerch Wrote here: http://en.wikibooks.org/wiki/MINC/Tutorials Use the Programming01 -> Programming06 links. -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From vladimir.fonov at gmail.com Thu Jun 4 19:14:08 2009 From: vladimir.fonov at gmail.com (Vladimir Fonov) Date: Thu, 4 Jun 2009 19:14:08 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: Hello, On Thu, Jun 4, 2009 at 6:52 PM, Andrew Janke wrote: > On Fri, Jun 5, 2009 at 06:52, Anthonin REILHAC > wrote: >> I am just about to start developping codes using the minc lib >> (opening/treating/saving in a new file). I am (was) a bit familiar with >> the minc1 interface, but a bit confused now that minc2 is here. What >> programming interface should I be using considering that the input files >> my codes will read will be minc{1,2} and considering that I would like to >> save in minc{1,2}? > > I would definitely use the MINC2 API it can read MINC 1 and 2. You can I think you meant MINC1 API , as MINC2 API is not able to read files in old format. -- Best regards, Vladimir S. Fonov ~ v.s.fonov <@> ilmarin.info From vladimir.fonov at gmail.com Thu Jun 4 19:16:36 2009 From: vladimir.fonov at gmail.com (Vladimir Fonov) Date: Thu, 4 Jun 2009 19:16:36 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: Hello, On Thu, Jun 4, 2009 at 4:52 PM, Anthonin REILHAC wrote: > I am just about to start developping codes using the minc lib > (opening/treating/saving in a new file). I am (was) a bit familiar with > the minc1 interface, but a bit confused now that minc2 is here. What > programming interface should I be using considering that the input files > my codes will read will be minc{1,2} and considering that I would like to > save in minc{1,2}? In other words, should I re-read the MINC 1.0 > Programmers Reference or get familiar with MINC 2.0 Reference Manual? > I guess that this question is often asked, and maybe the answer is written > somewhere on the wiki pages. Take a look at my library : http://www.bic.mni.mcgill.ca/~vfonov/software/ezminc_r29.tar.gz - there is simplified C++ interface to MINC1 API (so it reads and writes both MINC1 and MINC2 ) , also it is used to add MINC1/2 IO to ITK. -- Best regards, Vladimir S. Fonov ~ v.s.fonov <@> ilmarin.info From a.janke at gmail.com Thu Jun 4 19:32:50 2009 From: a.janke at gmail.com (Andrew Janke) Date: Fri, 5 Jun 2009 09:32:50 +1000 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: >> I would definitely use the MINC2 API it can read MINC 1 and 2. You can > > I think you meant MINC1 API , as MINC2 API is not able to read files > in old format. erk! Yes (sorry!) Far far too early in the morning over here for me to function normally. (8.30am :) -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From anthonin at bic.mni.mcgill.ca Fri Jun 5 08:19:13 2009 From: anthonin at bic.mni.mcgill.ca (Anthonin REILHAC) Date: Fri, 5 Jun 2009 08:19:13 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: Ok thanks for your quick answers. Then I should use the MINC1 API. And I guess, the code exemples on Jason Lerch Wiki pages would not work with minc1 files as it seems to be pure minc2 codes. Anthonin Anthonin Reilhac McConnell Brain Imaging Centre, WB2B Montreal Neurological Institute 3801 University Montreal, Quebec, Canada phone: (514) 398 4965 From a.janke at gmail.com Fri Jun 5 09:16:12 2009 From: a.janke at gmail.com (Andrew Janke) Date: Fri, 5 Jun 2009 23:16:12 +1000 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: > And I guess, the code exemples on Jason Lerch Wiki pages would not work > with minc1 files as it seems to be pure minc2 codes. Yup, don't know where my brain was yesterday. Take a look at the examples in the minc distro itself. mincexample{1,2} a From anthonin at bic.mni.mcgill.ca Fri Jun 5 09:22:19 2009 From: anthonin at bic.mni.mcgill.ca (Anthonin REILHAC) Date: Fri, 5 Jun 2009 09:22:19 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: Thanks Andrew. Anthonin Anthonin Reilhac McConnell Brain Imaging Centre, WB2B Montreal Neurological Institute 3801 University Montreal, Quebec, Canada phone: (514) 398 4965 On Fri, 5 Jun 2009, Andrew Janke wrote: > > And I guess, the code exemples on Jason Lerch Wiki pages would not work > > with minc1 files as it seems to be pure minc2 codes. > > Yup, don't know where my brain was yesterday. Take a look at the > examples in the minc distro itself. mincexample{1,2} > > > a > _______________________________________________ > MINC-development mailing list > MINC-development at bic.mni.mcgill.ca > http://www2.bic.mni.mcgill.ca/mailman/listinfo/minc-development > From sean at rogue-research.com Fri Jun 5 17:37:44 2009 From: sean at rogue-research.com (Sean McBride) Date: Fri, 5 Jun 2009 17:37:44 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: Message-ID: <20090605213744.875888297@kingu.local> On 6/5/09 9:32 AM, Andrew Janke said: >>> I would definitely use the MINC2 API it can read MINC 1 and 2. You can >> >> I think you meant MINC1 API , as MINC2 API is not able to read files >> in old format. > >erk! Yes (sorry!) Could someone clarify this? I am admittedly ignorant about most MINC things (in my usage, it is merely a dependency of a higher level library), but I find it odd that the MINC1 API supports MINC2 files. Or am I missing a distinction between 'API' and 'library'? Does the MINC2 library provide two APIs? I guess what I'm getting at is the following: if one wants to support both the MINC1 and MINC2 file formats, is the MINC 2.0.18 library/ download sufficient or is the 1.5.1 library also needed? Thanks, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From vladimir.fonov at gmail.com Fri Jun 5 20:30:39 2009 From: vladimir.fonov at gmail.com (Vladimir Fonov) Date: Fri, 05 Jun 2009 20:30:39 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: <20090605213744.875888297@kingu.local> References: <20090605213744.875888297@kingu.local> Message-ID: <4A29B8AF.4010309@gmail.com> Hello, Sean McBride wrote: > Could someone clarify this? I am admittedly ignorant about most MINC > things (in my usage, it is merely a dependency of a higher level > library), but I find it odd that the MINC1 API supports MINC2 files. Or > am I missing a distinction between 'API' and 'library'? Does the MINC2 > library provide two APIs? Yes, even three - MINC1 API, MINC2 API and Volume IO > I guess what I'm getting at is the following: if one wants to support > both the MINC1 and MINC2 file formats, is the MINC 2.0.18 library/ > download sufficient or is the 1.5.1 library also needed? 2.xx would be sufficient. -- Best regards, Vladimir S. Fonov ~ vladimir dot fonov at gmail dot com From anthonin at bic.mni.mcgill.ca Mon Jun 8 14:30:37 2009 From: anthonin at bic.mni.mcgill.ca (Anthonin REILHAC) Date: Mon, 8 Jun 2009 14:30:37 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: <20090605213744.875888297@kingu.local> References: <20090605213744.875888297@kingu.local> Message-ID: And then another question: Does the volume_io API works with any minc version? Anthonin Anthonin Reilhac McConnell Brain Imaging Centre, WB2B Montreal Neurological Institute 3801 University Montreal, Quebec, Canada phone: (514) 398 4965 From vladimir.fonov at gmail.com Mon Jun 8 14:34:12 2009 From: vladimir.fonov at gmail.com (Vladimir Fonov) Date: Mon, 08 Jun 2009 14:34:12 -0400 Subject: [MINC-development] MINC1/MINC2 In-Reply-To: References: <20090605213744.875888297@kingu.local> Message-ID: <4A2D59A4.2090308@gmail.com> Hello, Anthonin REILHAC wrote: > And then another question: Does the volume_io API works with any minc > version? yes, it's supposed to work with both MINC1 and MINC2. -- Best regards, Vladimir S. Fonov ~ vladimir dot fonov at gmail dot com From sean at rogue-research.com Sat Jun 13 00:12:10 2009 From: sean at rogue-research.com (Sean McBride) Date: Fri, 12 Jun 2009 21:12:10 -0700 Subject: [MINC-development] Small API change suggestion, for C++ compatibility Message-ID: <20090613041210.1989321060@76.65.240.2> Hi all, I know MINC is written in C, but one might want to use its API from C++ code. There are several functions that take a char* when it seems to me they should really take a const char*. Consider this C++ code: --------- #include "minc.h" void main (void) { miattgetstr (0, 0, MIfull_name, 0, NULL); } --------- Clearly it is useless, but note the 3rd parameter seems to be a typical case, passing one of the MI #defines. Compiled as C++ this warns: warning: deprecated conversion from string constant to 'char*' Would you accept a patch adding a bunch of consts? It would be correct C and C++. Thanks, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From sean at rogue-research.com Mon Jun 15 03:33:44 2009 From: sean at rogue-research.com (Sean McBride) Date: Mon, 15 Jun 2009 00:33:44 -0700 Subject: [MINC-development] compiler warnings when building in 2.0.18 Message-ID: <20090615073344.1887184503@76.65.240.2> Andrew, all, Building MINC 2.0.18 in 64bit I notice several serious/legit warnings: libsrc/ParseArgv.c: In function 'ParseArgv': libsrc/ParseArgv.c:177: warning: cast from pointer to integer of different size libsrc/ParseArgv.c:180: warning: cast from pointer to integer of different size libsrc/ParseArgv.c:202: warning: cast from pointer to integer of different size libsrc/ParseArgv.c:225: warning: cast from pointer to integer of different size libsrc/ParseArgv.c:241: warning: cast from pointer to integer of different size libsrc/ParseArgv.c: In function 'PrintUsage': libsrc/ParseArgv.c:402: warning: cast from pointer to integer of different size libsrc/ParseArgv.c:411: warning: cast from pointer to integer of different size libsrc/ParseArgv.c:421: warning: cast from pointer to integer of different size I'd offer a patch, but I'm not 100% sure about how this code works. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From a.janke at gmail.com Thu Jun 18 01:59:54 2009 From: a.janke at gmail.com (Andrew Janke) Date: Thu, 18 Jun 2009 15:59:54 +1000 Subject: [MINC-development] Small API change suggestion, for C++ compatibility In-Reply-To: <20090613041210.1989321060@76.65.240.2> References: <20090613041210.1989321060@76.65.240.2> Message-ID: > I know MINC is written in C, but one might want to use its API from C++ > code. ?There are several functions that take a char* when it seems to me > they should really take a const char*. True... (call it history). > Consider this C++ code: > > --------- > #include "minc.h" > > void main (void) > { > ? ? ? ?miattgetstr (0, 0, MIfull_name, 0, NULL); > } > --------- > > Clearly it is useless, but note the 3rd parameter seems to be a typical > case, passing one of the MI #defines. ?Compiled as C++ this warns: > > warning: deprecated conversion from string constant to 'char*' > > Would you accept a patch adding a bunch of consts? ?It would be correct > C and C++. Well I certainly would and am happy to apply it to CVS. -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From sean at rogue-research.com Thu Jun 18 14:36:44 2009 From: sean at rogue-research.com (Sean McBride) Date: Thu, 18 Jun 2009 11:36:44 -0700 Subject: [MINC-development] Small API change suggestion, for C++ compatibility In-Reply-To: References: <20090613041210.1989321060@76.65.240.2> Message-ID: <20090618183644.2008100360@76.65.240.2> On 6/18/09 3:59 PM, Andrew Janke said: >> Would you accept a patch adding a bunch of consts? ?It would be correct >> C and C++. > >Well I certainly would and am happy to apply it to CVS. Great, I will supply a patch. I assume you would prefer a patch against CVS and not 2.0.18? For the life of me, I cannot find the MINC CVS info. (Have I mentioned lately that the MINC web pages need updating. :)) -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From a.janke at gmail.com Fri Jun 19 01:16:56 2009 From: a.janke at gmail.com (Andrew Janke) Date: Fri, 19 Jun 2009 15:16:56 +1000 Subject: [MINC-development] Small API change suggestion, for C++ compatibility In-Reply-To: <20090618183644.2008100360@76.65.240.2> References: <20090613041210.1989321060@76.65.240.2> <20090618183644.2008100360@76.65.240.2> Message-ID: >>Well I certainly would and am happy to apply it to CVS. > > Great, I will supply a patch. ?I assume you would prefer a patch against > CVS and not 2.0.18? ?For the life of me, I cannot find the MINC CVS > info. ?(Have I mentioned lately that the MINC web pages need updating. :)) See here: http://en.wikibooks.org/wiki/MINC/Tutorials/CVSandPackaging Granted the wikibooks page isn't advertised too well but will be soon on the new BIC webpages once I get to them. export CVSROOT=cvs.bic.mni.mcgill.ca:/private-cvsroot Is what you want. -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From a.janke at gmail.com Mon Jun 22 10:19:11 2009 From: a.janke at gmail.com (Andrew Janke) Date: Tue, 23 Jun 2009 00:19:11 +1000 Subject: [MINC-development] compiler warnings when building in 2.0.18 In-Reply-To: <20090615073344.1887184503@76.65.240.2> References: <20090615073344.1887184503@76.65.240.2> Message-ID: Hi Sean, On Mon, Jun 15, 2009 at 17:33, Sean McBride wrote: > Building MINC 2.0.18 in 64bit I notice several serious/legit warnings: > > libsrc/ParseArgv.c: In function 'ParseArgv': > libsrc/ParseArgv.c:177: warning: cast from pointer to integer of > different size > ... > > I'd offer a patch, but I'm not 100% sure about how this code works. Can't remember if I responded to this directly but the answer is by all means. ParseArvg is a bit of a hairy goat that has been beaten into submission multiple times with 32->64bit changes. We really should have switched to something like popt by now but old habits are hard to break. -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From sean at rogue-research.com Tue Jun 23 13:17:44 2009 From: sean at rogue-research.com (Sean McBride) Date: Tue, 23 Jun 2009 13:17:44 -0400 Subject: [MINC-development] Small API change suggestion, for C++ compatibility In-Reply-To: References: <20090613041210.1989321060@76.65.240.2> <20090618183644.2008100360@76.65.240.2> Message-ID: <20090623171744.1809408006@kingu.local> On 6/19/09 3:16 PM, Andrew Janke said: >>>Well I certainly would and am happy to apply it to CVS. >> >> Great, I will supply a patch. ?I assume you would prefer a patch against >> CVS and not 2.0.18? ?For the life of me, I cannot find the MINC CVS >> info. ?(Have I mentioned lately that the MINC web pages need updating. :)) > >See here: > > http://en.wikibooks.org/wiki/MINC/Tutorials/CVSandPackaging > >Granted the wikibooks page isn't advertised too well but will be soon >on the new BIC webpages once I get to them. > > export CVSROOT=cvs.bic.mni.mcgill.ca:/private-cvsroot > >Is what you want. I've tried: $ export CVSROOT=cvs.bic.mni.mcgill.ca:/private-cvsroot $ cvs co minc2 It prompts for a password. Is there 'anonymous' access? If so, what is the CVS syntax to get the code? (I'm not really familiar with CVS.) -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From sean at rogue-research.com Tue Jun 23 13:33:29 2009 From: sean at rogue-research.com (Sean McBride) Date: Tue, 23 Jun 2009 13:33:29 -0400 Subject: [MINC-development] compiler warnings when building in 2.0.18 In-Reply-To: References: <20090615073344.1887184503@76.65.240.2> Message-ID: <20090623173329.614343435@kingu.local> On 6/23/09 12:19 AM, Andrew Janke said: >> Building MINC 2.0.18 in 64bit I notice several serious/legit warnings: >> >> libsrc/ParseArgv.c: In function 'ParseArgv': >> libsrc/ParseArgv.c:177: warning: cast from pointer to integer of >> different size >> ... >> >> I'd offer a patch, but I'm not 100% sure about how this code works. > >Can't remember if I responded to this directly but the answer is by >all means. ParseArvg is a bit of a hairy goat that has been beaten >into submission multiple times with 32->64bit changes. We really >should have switched to something like popt by now but old habits are >hard to break. It does look hairy. :) I daren't attempt a fix, I just wanted to report it to you. -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From a.janke at gmail.com Tue Jun 23 21:37:05 2009 From: a.janke at gmail.com (Andrew Janke) Date: Wed, 24 Jun 2009 11:37:05 +1000 Subject: [MINC-development] Small API change suggestion, for C++ compatibility In-Reply-To: <20090623171744.1809408006@kingu.local> References: <20090613041210.1989321060@76.65.240.2> <20090618183644.2008100360@76.65.240.2> <20090623171744.1809408006@kingu.local> Message-ID: > I've tried: > > $ export CVSROOT=cvs.bic.mni.mcgill.ca:/private-cvsroot > $ cvs co minc2 > > It prompts for a password. ?Is there 'anonymous' access? ?If so, what is > the CVS syntax to get the code? ?(I'm not really familiar with CVS.) Hrm.. You currently need a BIC account for CVS access. There is no anon access, this is something that I have pressed for for a long time but no consensus has been reached as to where we should shift MINC to. The alternatives are: 1) svn via http or something from the BIC 2) google code 3) launchpad 4) nitrc Currently I am tending towards #4 or failing that #2. Still this doesn't help you! I can tar up a current CVS HEAD and send it to you or organise a BIC account. Pick which one you'd like! -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canberra->Australia +61 (402) 700 883 From sean at rogue-research.com Wed Jun 24 14:20:34 2009 From: sean at rogue-research.com (Sean McBride) Date: Wed, 24 Jun 2009 14:20:34 -0400 Subject: [MINC-development] Small API change suggestion, for C++ compatibility In-Reply-To: References: <20090613041210.1989321060@76.65.240.2> <20090618183644.2008100360@76.65.240.2> <20090623171744.1809408006@kingu.local> Message-ID: <20090624182034.540120260@kingu.local> On 6/24/09 11:37 AM, Andrew Janke said: >I can tar up a current CVS HEAD and send it to you That would be great thanks! -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada