From: Kent W. <nor...@ui...> - 2004-01-08 00:04:39
|
If you look at ITK http://www.itk.org -- ITK hijacks just the vnl parts of VXL. 2 things: 1) I'd start from the current CVS version of ITK and 2) while there are no patches or changes to vnl to fit it into ITK, you will have to extract it from the ITK build environment. The vnl stuff is in Insight/Utilities/vxl. It's set up to configure with CMake, so it should build easily on windows. On Wed, 2004-01-07 at 11:04, Simon Perkins wrote: > On Wed, 2004-01-07 at 09:14, Wheeler, Frederick W (Research) wrote: > > A few months ago I took a stab at compiling VXL with mingw. I found that > > VXL would need a lot of defined(__MINGW32__) additions near existing > > defined(__CYGWIN__) statements. vpl has trouble because the mingw > > environment is not POSIX enough, but that should be easy to fix up. > > If it makes any difference, we're really only interested in the VNL > parts of VXL at the moment. Has anyone packaged up VNL for windows? > > Cheers, > > Sy > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > Vxl-users mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-users |