On September 23, 2010 10:03:32 am kfj wrote: > Having finally managed to build libpano and collateral software using > minGW and msys, I am now considering an attempt to build the latest > hugin version in the same environment. But I feel I should rather ask > before I start if anyone has any helpful hints concerning this, or has > already done so and can warn me of any problems I might encounter.
Congratulations on the libpano build. Please consider updating the wiki. I would recommend adding a completely new page at [0]. For all practical piurpose MinGW is a different platform than MSVC, and I would rename more aptly "Windows" into "Windows/MSVC" and add your insights as "Windows/MinGW". Particularly users of Enblend/Enfuse will benefit from MinGW. AFAIK OpenMP is available with MinGW free of charge like with most other platforms, while on MSVC it is only available with the 1000$+ professional edition. Enblend/Enfuse use OpenMP to harness the power of modern multi-core multi- threaded CPUs. AFAIK yours is the only recent success at building anything related to Hugin with MinGW. More power to you. You may find some information in old threads [1]. It's too early to say but I think that if you get the whole build working on MinGW we should strive to qualify it as a "major supported platform". Yuv [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Supported_Platforms [1] http://groups.google.com/group/hugin-ptx/search?group=hugin- ptx&q=mingw&qt_g=Search+this+group > > Let me add that I'm not familiar with cmake (I have it, though) and > haven't built hugin before, but I'd like to start looking at the code > and feel that I should have ways to build the executables so I can > play with the code and see what happens. I've downloaded > hugin-2010.2.0_rc1.tar.gz as my starting point. > > with regards > KFJ
signature.asc
Description: This is a digitally signed message part.
