[hugin-ptx] Building hugin etc. on Windows in MSYS2 mingw64
I just finished building a fork of hugin and a fork of libpano13 and unmodified enblend on Windows using MSYS2 / mingw64 I tested barely more than opening an existing project, so there is a good chance some operations won't work because of errors I made in building. I ran into a massive string of problems. The non trivial ones and how I kludged around each are described below. I'd really appreciate some information on how I might have solved or avoided any or all of these problems more cleanly (other than telling me not to use mingw64). If some or all of these don't have great answers, I hope my description will help anyone else who wants to build hugin this way. I was working with a fork of hugin and libpano1, but I'm nearly certain that nothing that went wrong nor any of my kludges would be different if this was not a fork. First I got MSYS2 https://www.msys2.org/ Then I used lots of pacman commands to install lots of packages I expected to need. I didn't make a good list. But it is pretty obvious what is missing when you try CMake and pretty easy to find the name and install the package with pacman. You can't get hugin itself or panotool13 or enblend that way. But I wanted to build those myself anyway. I think building libpano13 is necessary. No pre-built binaries are compatible. But I'm pretty sure you could use pre-built binaries instead of building enblend. I followed online advice to use ninja instead of make. I don't think that caused any of these problems. *Lots of problems were in wxWidgets. * Online discussion of the first wxWidgets problem (described below) gave the opinion that the MSYS mingw64 package for wxWidgets puts things in the wrong place. I'm not an expert, but that seems wrong to me and I think instead CMake looks in the wrong place. The online suggestion for that was rebuild wxWidgets correctly. For most of the other wxWidgets problems, I think the MSYS package for wxWidgets *is *at fault and rebuilding it would be best. I never found online info of those problems. I kludged things to live with the bad wxWidgets rather than sidetrack into building a good one. cmake can't find wxWidgets I followed the instructions here. The line numbers there are obsolete. But correct places are easy to find by searching for MSYS https://forums.wxwidgets.org/viewtopic.php?f=19=47555#p202984 even after it find wxWidgets CMake Error at src/hugin1/CMakeLists.txt:27 (MESSAGE): It is looking for a manifest that I think it should not need and which certainly is not provided by the wxWidgets package. I gave it a different version of the manifest. Like almost all my kludges, I edited a line in CMakeCache.txt and then reran CMake: WINDOWS_DPI_MANIFEST:FILEPATH=C:/msys64/mingw64/include/wx-3.1/wx/msw/amd64.manifest It still can't find other parts of wxWidgets -- wxWidgets DLL path: WXWIDGETS_DLL_PATH-NOTFOUND A large fraction of the things it can't find are in the correct place for MSYS mingw64 which is /msys64/mingw64/bin CMake find functions seem to have lots of built in knowledge of MSYS mingw64, but it doesn't seem to work. If there was a good way to tell it that things are generally in /msys64/mingw64/binI'd like to know that. I had to individually tell it each thing WXWIDGETS_DLL_PATH:PATH=C:/msys64/mingw64/bin /include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17 does not allow dynamic exception specifications 1413 | throw(PreconditionViolation) My understanding of this error is that the vigra package in MSYS is too old and a newer copy would be better. So adding that to the set of things I build myself would be cleaner. BUT instead, I noticed that is fixed in two .hxx files stdconvolution.hxx separableconvolution.hxx In the newer vigra *and *I noticed that the change to those two files would not impact the binaries. It would be wrong to copy all the .hxx files from the newer version without rebuilding the binaries. But copying those two without rebuilding is safe. -- Could not find OPTIONAL package OPENEXR -- Found OPENEXR: C:/msys64/mingw64/lib/libImath.dll.a;C:/msys64/mingw64/lib/libIlmImf.dll.a;C:/msys64/mingw64/lib/libIex.dll.a;C:/msys64/mingw64/lib/libHalf.dll.a;C:/msys64/mingw64/lib/libIlmThread.dll.a;C:/msys64/mingw64/lib/libz.dll.a I never understood that one and I never fixed it, even when I fixed the later OPENEXR problem. I have never understood any of the common cases in trying to use CMake on windows where the message that it found something is right next to the message that it could not. Can anyone tell me what part of hugin won't work as a result of this optional item missing? Also what is the actual thing that is missing? CMake Error at CMakeModules/win_bundle.cmake:107 (MESSAGE): OpenEXR dlls not found in search path That was hard to diagnose and I'm not sure I diagnosed/fixed it correctly. If I diagnosed it correctly, that cmake file thinks things are part of
Re: [hugin-ptx] building hugin on fedora
Since I mentioned my problems with trying to start debugging a debug build of hugin, I'll describe the partial answer I've found so far. Maybe anyone else who would try to debug hugin would already know this stuff. But in case that is not true: I think CodeBlocks was failing because the underlying gdb was unresponsive (haven't verified yet by retrying with CodeBlocks). Using gdb directy, it was unresponsive after displaying a line starting with [ and ending with ] and otherwise blank. After trying other things, I eventually realized the meaning was failure to get a response from some server that it was trying to download debug info from. Aborting the hung gdb and restarting, it used a cache for all the debug symbols it had gotten the first time (before the failure) and got an immediate response from the server that had failed the first time and got through a bunch more before failing again. Third time it finished downloading all those symbols. Now I'm figuring out basics of using gdb (identifying the correct one of hugin's 36 threads to get a meaningful backtrace, setting breakpoints, looking at things). -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/13414418-5c36-494b-b8e6-2cf586daed3an%40googlegroups.com.
Re: [hugin-ptx] building hugin on fedora
On Wed, 2022-01-26 at 14:09 -0800, johnfi...@gmail.com wrote: > On Saturday, January 22, 2022 at 10:39:36 AM UTC-5 johnfi...@gmail.com wrote: > > I ran make -j16 > Meanwhile I ran system monitor to see that about half my cpu capacity was in > use > > Then my system crashed. Seemed to be a display driver crash. Maybe there is > some > problem in building hugin with j16, but more likely it is a display driver > bug. > > > On Saturday, January 22, 2022 at 1:27:25 PM UTC-5 bruno...@gmail.com wrote: > > > > There is definitely something wrong with your graphics setup. The > > standard nouveau driver might not have all the top features, but in my > > experience it is very stable. You shouldn't expect a problem in Hugin > > to crash the whole system like this. > > > > > Just wanted to mention the above crash was something that only happens with > Plasma > System Monitor running. Using KSysGuard instead of Plasma System Monitor, I > get > zero such problems (zero using Nvidia driver, lots of problems using nouveau > driver). It's probably no real help, but just for the record I regularly build hugin rpms on Fedora, and use the nouveau driver. I can't remember the last time I had any problems with a build that weren't my own doing. Cheers, -- Terry Duell -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c6cd25aba174369e4ebc4560e4aabebff320093f.camel%40iinet.net.au.
Re: [hugin-ptx] building hugin on fedora
On Saturday, January 22, 2022 at 10:39:36 AM UTC-5 johnfi...@gmail.com wrote: I ran make -j16 Meanwhile I ran system monitor to see that about half my cpu capacity was in use Then my system crashed. Seemed to be a display driver crash. Maybe there is some problem in building hugin with j16, but more likely it is a display driver bug. On Saturday, January 22, 2022 at 1:27:25 PM UTC-5 bruno...@gmail.com wrote: > > There is definitely something wrong with your graphics setup. The > standard nouveau driver might not have all the top features, but in my > experience it is very stable. You shouldn't expect a problem in Hugin > to crash the whole system like this. > Just wanted to mention the above crash was something that only happens with Plasma System Monitor running. Using KSysGuard instead of Plasma System Monitor, I get zero such problems (zero using Nvidia driver, lots of problems using nouveau driver). So definitely nothing wrong with the hugin build (which builds even faster at -j32 than at -j16). Maybe there is still some problem related to the ancient Nvidia card. But I have seen symptoms of that problem only in two places: recovery from sleep (I no longer use sleep for that reason) and Plasma System Monitor (I no longer use it for that reason). Meanwhile, I'm trying to figure out how to debug a debug build of hugin. I still want to know why magnification to over 2**27 pixels breaks the control panel dialog and indirect evidence is pointing me into the pixmap object wrapped inside the wxBitmap object. From the wxBitmap source code I can't even figure out what object that pixmap even is, much less look into its source code. Long ago, I gave up trying to learn how to use gdb (but I might need to reverse that decision for this). I'm used to debugging with CodeBlocks (which uses gdb under the hood, but hides that from me). I knew in Windows how to get CodeBlocks to debug something that wasn't built in CodeBlocks and for this, I learned the different way to make that work in Linux. Now CodeBlocks seems unable to understand the correspondence between binary positions and source code positions (likely because gdb is failing to do that) so it can't open the source code on break and breakpoints set in source code don't work. The usual causes for that problem don't apply, so solutions I know in CodeBlocks from past projects, don't work. So I'm at a dead end with CodeBlocks debugger. Maybe there is more flexibility in gdb itself. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/b9989d51-3602-43d6-bda2-c4fd54c5a19dn%40googlegroups.com.
Re: [hugin-ptx] building hugin on fedora
On Saturday, January 22, 2022 at 1:27:25 PM UTC-5 bruno...@gmail.com wrote: > The > standard nouveau driver might not have all the top features, but in my > experience it is very stable. > My experience has been very different. Years ago at work, I was using several Centos systems with varying hardware, including different models of display card, but all display cards that used the older (now 340) driver from Nvidia. The nouveau driver crashed a lot on any of those systems. The Nvidia driver was rock solid. Later using Centos at home with similar hardware, nouveau crashed a lot. Nvidia 340 failed 100% on restore from sleep but otherwise was rock solid. When I installed hugin, other packages upgraded, breaking firefox. I couldn't back out changes nor could I get an updated firefox to work. Eventually I trashed the whole install trying. Starting over with Ubuntu, I thought Ubuntu had installed the 340 driver (I should have checked rather than trusting) so I thought I had bad ram. I replaced everything but the graphics card and displays (graphics cards are absurdly expensive right now). Only after Ubuntu continued to crash and then Fedora similarly crash, I finally realized all those crashes are the nouveau driver. A Fedora forum post told me how to get past the problem in newer linux kernels of installing the ancient 340 driver. So I switched back to that (same driver I used for years in Centos). It sometimes recovers from sleep (never did in Centos, so in ordinary use I never enable sleep) and until this hugin activity was solid for ordinary use. It is never easy to rule out other hardware or install issues. But I'm pretty sure the nouveau driver never had stable support for these older architecture Nvidia cards and the Nvidia 340 driver is much better but not perfect. Sorry I confused my video driver issues with hugin build issues. I'd like to solve my mingw64 Windows hugin build issues and/or find out how to cross compile on Linuix for Windows. For the moment, I don't think I have any build problems in Fedora for hugin (thanks apparently to the better dependency list you gave me). -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/7992f565-9f2f-40f4-90c1-4d6ab3c39c33n%40googlegroups.com.
Re: [hugin-ptx] building hugin on fedora
On Sat, 22 Jan 2022 at 15:39, johnfine2017 wrote: > I got build instructions both from > https://wiki.panotools.org/Hugin_Compiling_Fedora > and from a recent post by Bruno suggesting > The list of things to install is very different between those two sources. > Is that first one obsolete? The wiki will be out of date, the list of packages I gave is that used to build the current official fedora Hugin package. > Then my system crashed. Seemed to be a display driver crash. Maybe there is > some problem in building hugin with j16, but more likely it is a display > driver bug. In an otherwise new and powerful system, I have an ancient > graphics card driving two high res displays. The nouveau driver crashes > constantly for this hardware, so I'm not using it. I'm using the 340 driver > from Nvidia, which doesn't crash much. But it does crash. There is definitely something wrong with your graphics setup. The standard nouveau driver might not have all the top features, but in my experience it is very stable. You shouldn't expect a problem in Hugin to crash the whole system like this. All the warnings about gtk window sizes don't seem to cause any problems here, though I have often wondered if there was something to be gained from fixing them. -- Bruno -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAJV99ZiiZgvQBC_aJjOFQxOLXoji5MBccq-yLGaKQmFpVdOh5w%40mail.gmail.com.
[hugin-ptx] building hugin on fedora
I wanted to start this thread, even though I don't have a lot to ask/report yet, because I'll otherwise forget things, and because someone might have some useful feedback on what I have so far. uname -a reports Linux linux 5.15.15-200.fc35.x86_64 #1 SMP Sun Jan 16 17:37:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux I got build instructions both from https://wiki.panotools.org/Hugin_Compiling_Fedora and from a recent post by Bruno suggesting sudo dnf install gcc-c++ libpano13-devel zlib-devel libtiff-devel libjpeg-devel libpng-devel gettext-devel wxGTK3-devel boost-devel freeglut-devel cmake desktop-file-utils OpenEXR-devel exiv2-devel glew-devel python3-devel swig flann-devel perl-Image-ExifTool mesa-libGLU-devel libXmu-devel sqlite-devel vigra-devel perl-podlators fftw-devel lcms2-devel The list of things to install is very different between those two sources. Is that first one obsolete? Getting everything from that first list first, it complained that wxPython doesn't exist, but I got everything else. I didn't try cmake with just those things. Getting Bruno's list next installed 26 packages I hadn't gotten from that first list (some things on Bruno's list that I didn't have yet, plus whatever those depended on that I didn't have). I lost the list of what was extra, because my system crashed before I saved that list. cmake just worked (first time that happened for me since I started trying to build hugin). It failed for me in Windows. It failed for me in Ubuntu (maybe because I was using an obsolete list of packages required, rather than Bruno's list). I ran make -j16 Meanwhile I ran system monitor to see that about half my cpu capacity was in use and about 22% of ram, meaning the 16 jobs in my 16 thread cpu were averaging half speed due to waits on disk reads. That is as expected for this system. It certainly means 16 is NOT too many for my hardware. Then my system crashed. Seemed to be a display driver crash. Maybe there is some problem in building hugin with j16, but more likely it is a display driver bug. In an otherwise new and powerful system, I have an ancient graphics card driving two high res displays. The nouveau driver crashes constantly for this hardware, so I'm not using it. I'm using the 340 driver from Nvidia, which doesn't crash much. But it does crash. Rebooted and built without j16 Next I need to figure out what I need to do (what else to install) to actually use what I just built. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/4cf50afd-06a9-4e6c-be33-c5a794514401n%40googlegroups.com.
Re: [hugin-ptx] Building Hugin on OSX 10.9 Mavericks (doesn't work)
Ciao Gilbert On 30 Jun 2014, at 07:53, B1tstreamAlpha brookemgilb...@gmail.com wrote: Has anyone else here attempted to build Hugin natively on OSX 10.9 Mavericks? I’ve not *built* hugin on Mavericks, but I’m using Matthieus build of RC4 on it with virtually no problems. You can grab it here: http://sourceforge.net/projects/hugin/files/hugin/hugin-2014.0/Hugin-2014.0.0-RC4-build-2.dmg/download The small problems I’m seeing are currently under investigation and I’m preparing bug reports for those... Habi signature.asc Description: Message signed with OpenPGP using GPGMail
[hugin-ptx] Building Hugin on OSX 10.9 Mavericks (doesn't work)
Has anyone else here attempted to build Hugin natively on OSX 10.9 Mavericks? I am having a terrible time of it and before I start spewing compiler outputs, I thought I'd ask if anyone else has already made a successful build. Ok technically I've gotten it to *build* after much pain and few hacks, but I still have a runtime error when loading the dylibs... So either I'm doing something wrong, or perhaps nobody's done a native build on 10.9 yet (and lived to tell about it). So, anyone done it? If so, how? And if not, I'd appreciate some help with my broken build... Thanks -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5fe886c8-bc78-498c-949f-5955b65e3962%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Building Hugin with debugging symbols
On Tue, 10 Jul 2012 15:53:26 +1000, Lukáš Jirkovský l.jirkov...@gmail.com wrote: It should be cmake -DCMAKE_BUILD_TYPE=Debug Yes, you are right. Sorry, I should have checked the CMakeLists.txt for the specific definition and not assumed it would be as per the one example in my rpmbuild spec file. Cheers, -- Regards, Terry Duell -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Building Hugin with debugging symbols
On Tuesday, 10 July 2012 at 7:53:26 +0200, Luk?? Jirkovsk wrote: On 10 July 2012 02:18, Terry Duell tdu...@iinet.net.au wrote: Whoops...that's not right. If building in the topmost dir of a hugin repository, and running cmake at that level; cmake . -DDebug=1 It should be cmake -DCMAKE_BUILD_TYPE=Debug Thanks, but that's not what I'm looking for. That enables debugging code in the source. I'm looking for something that tells the Makefiles to build the object files with debugging symbols (the -g option to gcc) so that I can investigate what's going on with gdb. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua pgpDYDTk6uAQo.pgp Description: PGP signature
Re: [hugin-ptx] Building Hugin with debugging symbols
On 10 July 2012 08:27, Greg 'groggy' Lehey groog...@gmail.com wrote: On Tuesday, 10 July 2012 at 7:53:26 +0200, Luk?? Jirkovsk wrote: On 10 July 2012 02:18, Terry Duell tdu...@iinet.net.au wrote: Whoops...that's not right. If building in the topmost dir of a hugin repository, and running cmake at that level; cmake . -DDebug=1 It should be cmake -DCMAKE_BUILD_TYPE=Debug Thanks, but that's not what I'm looking for. That enables debugging code in the source. I'm looking for something that tells the Makefiles to build the object files with debugging symbols (the -g option to gcc) so that I can investigate what's going on with gdb. Greg This option passes the -g compiler option automatically, so you will get debugging symbols. This is the standard way to create a debug build using CMake. If you really do not want other debug information, just set up CFLAGS CXXFLAGS appropriately before running cmake. Oh, and for both options to work you need to do a clean build (especially there must not be a CMakeCache file before you run cmake). Lukas -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Building Hugin with debugging symbols
As you may have noticed, I'm currently having difficulty with the 64 bit version of Hugin under FreeBSD. I'd like to look around inside with gdb, but I don't do cmake, and I can't work out how to compile with debugging symbols. Can anybody help? It would also be interesting to be able to specify which compiler to use. Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua pgpQKljmWm3Uc.pgp Description: PGP signature
Re: [hugin-ptx] Building Hugin with debugging symbols
Hullo Greg, On Mon, 09 Jul 2012 18:00:30 +1000, Greg 'groggy' Lehey groog...@gmail.com wrote: As you may have noticed, I'm currently having difficulty with the 64 bit version of Hugin under FreeBSD. I'd like to look around inside with gdb, but I don't do cmake, and I can't work out how to compile with debugging symbols. Can anybody help? A quick snoop about makes me think that if you use cmake like this it will include the debug... cmake -DDebug=1 without the of course and prepending with ./ if necessary. I might have this wrong, as I'm no expert on cmake (or anything else for that matter), but this looks to be the way cmake is invoked from within the Fedora rpmbuild spec file. It would also be interesting to be able to specify which compiler to use. Don't know about that one. Cheers, -- Regards, Terry Duell -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Building Hugin with debugging symbols
On Tue, 10 Jul 2012 09:29:23 +1000, Terry Duell tdu...@iinet.net.au wrote: [snip] cmake -DDebug=1 without the of course and prepending with ./ if necessary. Whoops...that's not right. If building in the topmost dir of a hugin repository, and running cmake at that level; cmake . -DDebug=1 Cheers, -- Regards, Terry Duell -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Building Hugin for Windows with Lensfunc
All I'm trying to build the gui_overhaul branch on Windows.. My current problem is that this also includes lensfun. From searching I can find some comments which suggest it can be compiled under Windows, and others which suggest not. Before I try has anybody already done this? Regards Steve -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Building Hugin for Windows with Lensfunc
Steve, I did it earlier using MSVC 2008. iI don't have details with me at the moment but I think that I built the files as static Brian -- View this message in context: http://old.nabble.com/Building-Hugin-for-Windows-with-Lensfunc-tp33877469p33877682.html Sent from the hugin ptx mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] building hugin 2010.2.0 with minGW
Hi all! 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. 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 -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] building hugin 2010.2.0 with minGW
what is collateral? On Thu, 2010-09-23 at 07:03 -0700, kfj wrote: collateral -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] building hugin 2010.2.0 with minGW
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- ptxq=mingwqt_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.
[hugin-ptx] Building Hugin on windows?
Hi! I tried building Hugin following the http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK but failed as the SDK on the wiki has outdated Panotools, so I tried and failed to compile them. What I did was checked out the SVN 1242 and tried got different shades of missing files, most were fixed by running cmake and pointing it to the wxWidgets, some persist. I don't even know if I should be useing cmake to make a sln file. Would anyone help out please? TIA! -- You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Building Hugin
High all, I´m new to this group and sort of dummy in softwaredevelopment. Nevertheless I tried to start building hugin on windows using the sdk. It seems to me that enblend has moved to http://enblend.hg.sourceforge.net/hgweb/enblend Using this adress cloning worked as described in the panotools wiki. The adress still given there will cause a HTTP Error 400: Bad Request message. If what I mentioned is right, I may start building hugin the first time this week end. regards Andreas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
