[hugin-ptx] Re: Building hugin etc. on Windows in MSYS2 mingw64
On Monday, March 14, 2022 at 9:17:34 PM UTC-4 johnfi...@gmail.com wrote: > > Reviewing it, I now understand > > Actually, I was even more wrong that time. I'm gradually understanding more about this problem, but still don't know the basic cause. When wxUSE_TASKBARBUTTON is defined as 0, you can't use those classes. But why that symbol is defined as 0 in msys2/mingw64, I don't understand. For now, I think the right answer is to test that symbol before using those classes. -- 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/f6a7344d-33b3-48a2-b2be-f86e7e1d87c1n%40googlegroups.com.
[hugin-ptx] Re: Building hugin etc. on Windows in MSYS2 mingw64
src/hugin1/hugin/huginApp.cpp:382:5: error: 'wxTaskBarJumpList' was not declared in this scope src/hugin1/ptbatcher/BatchFrame.cpp:1291:9: error: 'wxTaskBarButton' was not declared in this scope I seriously misunderstood the situation when I kludged past the above problem earlier. Reviewing it, I now understand those two hugin files are including the wrong variant of taskbarbutton.h There is one in wx-3.1/wx/ and another in wx-3.1/wx/msw There are other .h files that similarly have those two variants and for those .h files other hugin source files correctly decide to use wx/msw instead of wx/ during this build. I don't yet understand why this isn't a problem for everyone building hugin in Windows. Obviously it is not that common a problem. But I don't yet see a reason that it would be specific to msys2. I'll research it more some other time, unless someone answers this before then. -- 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/b9bd06a5-4d52-4c5a-a8db-069e8a4b32c3n%40googlegroups.com.
[hugin-ptx] Re: building hugin on fedora
All those warning messages distracted me from what should have been obvious: In my Fedora system, I hadn't installed enblend With that fixed, I seem to have things working with the hugin executable I just built. Are all those warnings normal? Or are they something that should be investigated? The system hang seems to be unrelated to either those warnings or the missing enblend. Probably more random issues with that 340 driver. Probably I ought to buy a newer display card. I mainly use open office calc and firefox on Fedora (I prefer to use hugin on Windows where I currently can't build it). The nouveaux driver had problems like this all the time using just calc and firefox. The nVidia driver never has problems in calc and firefox. It messes up on operations like restoring after sleep. Before starting this hugin experimentation, I never had any crashes using the 340 driver that weren't on mode changes. So maybe something else is going on. But likely not a hugin issue. On Saturday, January 22, 2022 at 11:25:07 AM UTC-5 johnfi...@gmail.com wrote: > I ran the hugin I built. I did not do the LD_LIBRARY_PATH thing Bruno > suggested in the other thread, because my system does have the lib64 setup > (lib is 64 bit) and because ldd indicated hugin had access to all the .so > files it needed without that. I'll investigate whether something else > needs that after I reboot Linux (I'm typing this on windows before > rebooting a hung Linux machine). > > hugin initially seemed to be working. I loaded a project I had stitched > (with poor results, but no specific malfunctions) using the Windows binary > release of hugin. > Is there some problem in moving a hugin project from Windows to Fedora > and/or from the released hugin build to latest (today) from mercurial? > > When I stitched that, it gave the usual prompts (overwrite the previous > result files, etc.) then flashed a bunch of things on screen, then hung my > system (I think kdm is hung). > The log file (on a fileserver, so I can see before rebooting linux) ends > with: > Blending exposure layer 0... > execvp(enblend, -f2658x5011, --compression=LZW, -o, 20220115_155306 - > 20220115_155319_exposure_.tif, --, 20220115_155306 - > 20220115_155319_exposure_layers_.tif) failed with error 2! > > The konsole window I ran it from scrolled through lots of error messages, > the still visible ones are variants on these: > (PTBatcherGUI:4786): Gtk-WARNINGS **: 10:58:16.593: for_size smaller than > min_size (0 < 14) while measuring gadget (node check, owner GtkCheckButton) > (PTBatcherGUI:4786): Gtk-WARNINGS **: 10:58:16.593: Negative content > height -2 (allocation 0, extents 1,1) while allocating gadget (node check, > owner GtkCheckButton) > > The batch processor window is up with a status of failed. Other windows > opened by the stitch action, closed right before the system hung. > > -- 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/1d0605e1-a44f-4ea8-a06d-95d52ecf5465n%40googlegroups.com.
[hugin-ptx] Re: building hugin on fedora
I ran the hugin I built. I did not do the LD_LIBRARY_PATH thing Bruno suggested in the other thread, because my system does have the lib64 setup (lib is 64 bit) and because ldd indicated hugin had access to all the .so files it needed without that. I'll investigate whether something else needs that after I reboot Linux (I'm typing this on windows before rebooting a hung Linux machine). hugin initially seemed to be working. I loaded a project I had stitched (with poor results, but no specific malfunctions) using the Windows binary release of hugin. Is there some problem in moving a hugin project from Windows to Fedora and/or from the released hugin build to latest (today) from mercurial? When I stitched that, it gave the usual prompts (overwrite the previous result files, etc.) then flashed a bunch of things on screen, then hung my system (I think kdm is hung). The log file (on a fileserver, so I can see before rebooting linux) ends with: Blending exposure layer 0... execvp(enblend, -f2658x5011, --compression=LZW, -o, 20220115_155306 - 20220115_155319_exposure_.tif, --, 20220115_155306 - 20220115_155319_exposure_layers_.tif) failed with error 2! The konsole window I ran it from scrolled through lots of error messages, the still visible ones are variants on these: (PTBatcherGUI:4786): Gtk-WARNINGS **: 10:58:16.593: for_size smaller than min_size (0 < 14) while measuring gadget (node check, owner GtkCheckButton) (PTBatcherGUI:4786): Gtk-WARNINGS **: 10:58:16.593: Negative content height -2 (allocation 0, extents 1,1) while allocating gadget (node check, owner GtkCheckButton) The batch processor window is up with a status of failed. Other windows opened by the stitch action, closed right before the system hung. -- 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/c39c2494-4f68-46db-a27b-98654bcfeb40n%40googlegroups.com.
[hugin-ptx] Re: Building Hugin on OSX 10.9 Mavericks (doesn't work)
Hello, are you using the xcode workspace or the cmake build ? I know I built it on 10.9 with xcode and it ran fine, but it was more than 6 months ago and I remember it was not an easy build. What kind of errors are you having ? On Monday, June 30, 2014 7:53:12 AM UTC+2, B1tstreamAlpha wrote: 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/6f2acb1c-f925-4040-9fdd-5495512680f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Building Hugin for Windows with Lensfunc
A big thanks to Thomas, who had already updated the wiki for this: http:wiki.panotools.org/Hugin_SDK_(MSVC_2010)#Lensfun_library 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] Re: building hugin 2010.2.0 with minGW
On September 24, 2010 08:45:13 am Bart van Andel wrote: Does building libpano13 using the mingw-cross-env cross building environment [0] count? I've successfully built APSC for Windows from a Ubuntu virtual machine last week. This required only very little manual intervention: of course it counts, you genious! Please head over to [0] and add your findings as a new platform. Would mingw-cross-env be the right name for it? is it 32bit? 64bit? both? Describe what is needed to get the platform going too. Once completed, your process will enable Linux-based contributors to produce Windows binaries. It is no guarantee that a Linux-based contributor will actually want to spend the time on this, but at least it will be possible. Yuv [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Supported_Platforms libpano13: - enable PPM support for MINGW target, to prevent linker errors later on. This should probably go into Makefile.am, but I edited the already generated Makefile.in instead, which was faster. Is there a reason why PPM support was disabled in the first place? - sys_win.h includes WINDOWSX.H (all uppercase), but the file is called windowsx.h (all lowercase) when using mingw-cross-env. Not sure if this is specific to mingw-cross-env. - some tweaks specific to mingw-cross-env for file naming and usage of tools, handled by mingw-cross-env. APSC: - manually edited the order of inclusion of libraries, since I couldn't get (the cross build) GCC to work with the automatically generated, but improper order. I don't know of any way to correct the order using CMake? Of is there a GCC option I missed to instruct the linker to search for symbols in all libs provided on the command line? The PPM tweak for libpano13 is on its way into the mingw-cross-env sources and will work with the current libpano13 release, the other tweaks were already included. Probably it should be fixed in libpano13 itself though, and maybe also the uppercase/lowercase fix, is it's not mingw-cross-env specific. [0] http://mingw-cross-env.nongnu.org/#packages -- Bart signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: building hugin 2010.2.0 with minGW
On September 24, 2010 10:13:27 am kfj wrote: Alternatively, I tried to compile the libilm code without threading, may be OK for the exercise, but for all practical purpose please do not distribute binaries castrated this way. Users care about performance. Not that it really matters, but as car marketers know very well, users find it cool to brag about the horse power and top speed of their cars even if they lack the skill and the nerve to harness that power and it does not make any difference on their way to grocery shopping and back. Yuv signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: building hugin 2010.2.0 with minGW
On Sep 25, 9:28 pm, Yuval Levy goo...@levy.ch wrote: On September 24, 2010 10:13:27 am kfj wrote: Alternatively, I tried to compile the libilm code without threading, may be OK for the exercise, but for all practical purpose please do not distribute binaries castrated this way. ha ha, distribute! Now that's quite probably not going to happen in the near future. I haven't even got the libraries together, and I'm not sure if I'll get to a point when I can even start up the build. I thought I could maybe get some core thing going to expand from there, but even that failed so far. I might yet yield to the MSVC lure... So don't worry, and I certainly wouldn't want to produce crippleware, much less distribute it ;) 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
[hugin-ptx] Re: building hugin 2010.2.0 with minGW
On 24 sep, 04:17, Yuval Levy goo...@levy.ch wrote: On September 23, 2010 10:03:32 am kfj wrote: Having finally managed to build libpano and collateral software using minGW and msys, [...] AFAIK yours is the only recent success at building anything related to Hugin with MinGW. More power to you. Does building libpano13 using the mingw-cross-env cross building environment [0] count? I've successfully built APSC for Windows from a Ubuntu virtual machine last week. This required only very little manual intervention: libpano13: - enable PPM support for MINGW target, to prevent linker errors later on. This should probably go into Makefile.am, but I edited the already generated Makefile.in instead, which was faster. Is there a reason why PPM support was disabled in the first place? - sys_win.h includes WINDOWSX.H (all uppercase), but the file is called windowsx.h (all lowercase) when using mingw-cross-env. Not sure if this is specific to mingw-cross-env. - some tweaks specific to mingw-cross-env for file naming and usage of tools, handled by mingw-cross-env. APSC: - manually edited the order of inclusion of libraries, since I couldn't get (the cross build) GCC to work with the automatically generated, but improper order. I don't know of any way to correct the order using CMake? Of is there a GCC option I missed to instruct the linker to search for symbols in all libs provided on the command line? The PPM tweak for libpano13 is on its way into the mingw-cross-env sources and will work with the current libpano13 release, the other tweaks were already included. Probably it should be fixed in libpano13 itself though, and maybe also the uppercase/lowercase fix, is it's not mingw-cross-env specific. [0] http://mingw-cross-env.nongnu.org/#packages -- Bart -- 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] Re: building hugin 2010.2.0 with minGW
I have started trying to get everything together I need for my hugin/ minGW attempt. This worked fine until I came to try and compile the OpenEXR code [typically this was the last biggish packet on the list]. This code seems to depend on another library, ilmbase. Now ilmbase won't compile until it has POSIX threads. I downloaded pthreads-w32 and tried to coax the libilm configure into accepting pthread-w32's output, but to no avail. I keeps telling me that checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... no checking whether pthreads work with -pthreads... no checking whether pthreads work with -mthreads... no checking for the pthreads library -lpthread... no checking whether pthreads work with --thread-safe... no checking whether pthreads work with -mt... no checking for pthread-config... no configure: error: POSIX thread support required and fails. My coaxing went so that I made some links from pthread- w32's output to where I think libilm should expect to find them: ln pthreadGC2.dll /usr/local/lib/pthread.dll ln libpthreadGC2.a /usr/local/lib/libpthread.a for good measure, I also put links into the other /lib and /bin directories, but to no avail... Alternatively, I tried to compile the libilm code without threading, by configuring it like: ./configure --enable-threading=no --disable-posix-sem which at least makes the configure run through, but then subsequently the make fails. Has anyone been there? and then done what? momentarily stalled 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
[hugin-ptx] Re: building hugin 2010.2.0 with minGW
On Sep 23, 4:25 pm, Dale Beams drbe...@hotmail.com wrote: what is collateral? let me quote from Wiktionary http://en.wiktionary.org/wiki/collateral [...] Adjective collateral (not comparable) 1. parallel, along the same vein, side by side. 2. Corresponding; accompanying, concomitant. 3. being aside from the main subject; tangential, subordinate, ancillary. Although not a direct cause, empire-building was certainly a collateral incitement for the war. 4. (family) of an indirect ancestral relationship, as opposed to lineal descendency. Uncles, aunts, cousins, nephews and nieces are collateral relatives. [quotations ▼] * 1885, Richard Burton, The Book of the Thousand Nights and a Night, volume 5, The pure blood all descends from five collateral lines called Al-Khamsah (the Cinque). [...] I thought the term fitting to describe the set of programs that are part of the libpano package which aren't libpano in the strict sense (which would be libpano13.a or pano13.dll or such) - so I'm referring to PTblender.exe PTmasker.exe PTroller.exe PTuncrop.exe PTcrop.exe PTmender.exe PTtiff2psd.exe panoinfo.exe PTinfo.exe PToptimizer.exe PTtiffdump.exe 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
[hugin-ptx] Re: Building Hugin
Hi Andreas, anbue wrote: It seems to me that enblend has moved to http://enblend.hg.sourceforge.net/hgweb/enblend I do not recall if the Windows instructions still point to the old CVS repository; or they point to the old Hg repository. We moved the project from CVS to Hg. Then Sourceforge moved it again when it made it possible to have multiple Hg repositories per project. Actually what you are looking for is http://enblend.hg.sourceforge.net/hgweb/enblend/enblend please use that one, and be so kind to update the wiki. Also note that we're adding a CMake build. It should be easier to build with that on Windows. Please try it - the steps are very similar to the steps described for Hugin with CMake. I may start building hugin the first time this week end. if this is an exercise and you want to build your skill slowly but surely, start with a slightly older version - I would recommend a released tarball. You're more likely to succeed at first; and if you bump into problems you can solve them by looking at the wiki's page history. Once you've dipped your toes this way, you can move to build the bleeding edge with more confidence. good luck! Yuv --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
