[hugin-ptx] Re: Mac Build
Hi Niklas,
Am Freitag, 27. Mai 2016 22:15:57 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas,
>
> yes, argv has size of 1 when opened via Finder
> and with your change it works perfectly in both cases.
> Great work! (Attached patch contains that and the color-change)
>
> Thanks for testing.
I did some more cleanup and committed the changes.
I added also a longer comment to the mac specific part, explaining it a
little bit.
Thomas
PS: You have a PM
> Niklas
>
>
> Am Freitag, 27. Mai 2016 16:57:34 UTC+2 schrieb T. Modes:
>>
>> Hi Niklas,
>>
>> Am Donnerstag, 26. Mai 2016 22:42:05 UTC+2 schrieb Niklas Mischkulnig:
>>>
>>> What does OSXStoreOpenFiles do? With this code added, MacOpenFiles
>>> never gets called,
>>>
>>
>> It should prevent the call to MacOpenFiles when we parsed all options
>> already in OnInit.
>> What command line options gets PTBatcherGUI when you open it in finder
>> with a project? Is it empty (except argv[0])?
>>
>> Does it works when we add an if(argc>1) like
>> #ifdef __WXMAC__
>> if(argc>1)
>> {
>> wxArrayString emptyFiles;
>> OSXStoreOpenFiles(emptyFiles);
>> }
>> #endif
>>
>> see also attached patch.
>>
>> Thomas
>>
>
--
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/8319f81d-d557-42a5-ae14-0cbd144104e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Hi Thomas,
yes, argv has size of 1 when opened via Finder
and with your change it works perfectly in both cases.
Great work! (Attached patch contains that and the color-change)
Niklas
Am Freitag, 27. Mai 2016 16:57:34 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Donnerstag, 26. Mai 2016 22:42:05 UTC+2 schrieb Niklas Mischkulnig:
>>
>> What does OSXStoreOpenFiles do? With this code added, MacOpenFiles never
>> gets called,
>>
>
> It should prevent the call to MacOpenFiles when we parsed all options
> already in OnInit.
> What command line options gets PTBatcherGUI when you open it in finder
> with a project? Is it empty (except argv[0])?
>
> Does it works when we add an if(argc>1) like
> #ifdef __WXMAC__
> if(argc>1)
> {
> wxArrayString emptyFiles;
> OSXStoreOpenFiles(emptyFiles);
> }
> #endif
>
> see also attached patch.
>
> Thomas
>
--
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/b2742bf2-a3a2-4811-ab74-78c506bec726%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/hugin/GLViewer.cpp b/src/hugin1/hugin/GLViewer.cpp
--- a/src/hugin1/hugin/GLViewer.cpp
+++ b/src/hugin1/hugin/GLViewer.cpp
@@ -386,7 +386,11 @@
// we should use the window background colour outside the panorama
// FIXME shouldn't this work on textured backrounds?
+#if defined __WXMAC__ && wxCHECK_VERSION(3,1,0)
+wxColour col(128,128,128);
+#else
wxColour col = wxSystemSettings::GetColour(wxSYS_COLOUR_APPWORKSPACE);
+#endif
m_renderer->SetBackground(col.Red(), col.Green(), col.Blue());
if (m_visualization_state->RequireRecalculateViewport())
{
diff --git a/src/hugin1/ptbatcher/PTBatcherGUI.cpp b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
--- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
@@ -396,6 +396,13 @@
{
m_frame->RunBatch();
}
+#ifdef __WXMAC__
+if (argc > 1)
+{
+wxArrayString emptyFiles;
+OSXStoreOpenFiles(emptyFiles);
+};
+#endif
return true;
}
[hugin-ptx] Re: Mac Build
Hi Niklas,
Am Donnerstag, 26. Mai 2016 22:42:05 UTC+2 schrieb Niklas Mischkulnig:
>
> What does OSXStoreOpenFiles do? With this code added, MacOpenFiles never
> gets called,
>
It should prevent the call to MacOpenFiles when we parsed all options
already in OnInit.
What command line options gets PTBatcherGUI when you open it in finder with
a project? Is it empty (except argv[0])?
Does it works when we add an if(argc>1) like
#ifdef __WXMAC__
if(argc>1)
{
wxArrayString emptyFiles;
OSXStoreOpenFiles(emptyFiles);
}
#endif
see also attached patch.
Thomas
--
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/21cb1d55-8024-47ea-ae55-b05289bfc213%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# HG changeset patch
# Parent 5422e269f546cdad9d305767a1e608420d10bcf3
[mq]: ptbatcher_log.diff
diff --git a/src/hugin1/ptbatcher/PTBatcherGUI.cpp b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
--- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
@@ -167,7 +167,13 @@
};
wxCmdLineParser parser(cmdLineDesc, argc, argv);
-switch ( parser.Parse() )
+for (int i = 0; i < argc; ++i)
+{
+wxString s;
+s << "argv " << i << ": " << argv[i];
+wxLogMessage(s);
+};
+switch (parser.Parse())
{
case -1: // -h or --help was given, and help displayed so exit
return false;
@@ -221,7 +227,7 @@
}
};
-#ifdef __WXMAC__
+#if 0 //def __WXMAC__
// see PTBatcherGUI::MacOpenFile for explanation
m_macFileNameToOpenOnStart = wxT("");
wxYield();
@@ -267,6 +273,9 @@
while (parser.GetParamCount() > count)
{
wxString param = parser.GetParam(count);
+wxString s;
+s << "Param " << count << ": " << param;
+wxLogMessage(s);
count++;
if (!projectSpecified) //next parameter must be new script file
{
@@ -396,6 +405,13 @@
{
m_frame->RunBatch();
}
+#ifdef __WXMAC__
+if (argc > 1)
+{
+wxArrayString emptyFiles;
+OSXStoreOpenFiles(emptyFiles);
+};
+#endif
return true;
}
[hugin-ptx] Re: Mac Build
Hi Thomas, What does OSXStoreOpenFiles do? With this code added, MacOpenFiles never gets called, also not via Finder; that of course means that it doesn't get called either when Hugin opens it, so that is now works if opened by Hugin, but not if opened by Finder. Niklas #ifdef __WXMAC__ wxArrayString emptyFiles; OSXStoreOpenFiles(emptyFiles); #endif Am Donnerstag, 26. Mai 2016 21:48:00 UTC+2 schrieb T. Modes: > > Hello, > > Am Donnerstag, 26. Mai 2016 21:28:13 UTC+2 schrieb Niklas Mischkulnig: >> >> Hello, >> >>> >> Does it then works? Does it also works when starting from finder? >>> >> >> From Hugin, it makes no difference but it still works perfectly with >> Finder. >> >> (I don't know if it's important, but MacOpenFiles gets always called >> after the first text >> in the log window appears.) >> > > That's strange. > You should get the filename 2 times First with args .. and then with > param prefix. > Are you sure that all was correctly rebuild? > > I searched in the code of wxWidgets and added some more code (beside > commented out in my last mail). > Could you apply the attached code and try again? (Please check that it is > correctly applied.) > Thanks. > > Thomas > -- 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/e1a835b6-d6bf-4c65-90e3-5f4aa5198844%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Hello,
Am Donnerstag, 26. Mai 2016 21:28:13 UTC+2 schrieb Niklas Mischkulnig:
>
> Hello,
>
>>
> Does it then works? Does it also works when starting from finder?
>>
>
> From Hugin, it makes no difference but it still works perfectly with
> Finder.
>
> (I don't know if it's important, but MacOpenFiles gets always called after
> the first text
> in the log window appears.)
>
That's strange.
You should get the filename 2 times First with args .. and then with param
prefix.
Are you sure that all was correctly rebuild?
I searched in the code of wxWidgets and added some more code (beside
commented out in my last mail).
Could you apply the attached code and try again? (Please check that it is
correctly applied.)
Thanks.
Thomas
--
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/2b7573e8-7448-4256-8458-ccab70848c95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# HG changeset patch
# Parent 5422e269f546cdad9d305767a1e608420d10bcf3
diff --git a/src/hugin1/ptbatcher/PTBatcherGUI.cpp b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
--- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
@@ -167,6 +167,12 @@
};
wxCmdLineParser parser(cmdLineDesc, argc, argv);
+for (int i = 0; i < argc; ++i)
+{
+wxString s;
+s << "argv " << i << ": " << argv[i];
+wxLogMessage(s);
+};
switch ( parser.Parse() )
{
case -1: // -h or --help was given, and help displayed so exit
@@ -221,7 +227,7 @@
}
};
-#ifdef __WXMAC__
+#if 0 //def __WXMAC__
// see PTBatcherGUI::MacOpenFile for explanation
m_macFileNameToOpenOnStart = wxT("");
wxYield();
@@ -267,6 +273,9 @@
while (parser.GetParamCount() > count)
{
wxString param = parser.GetParam(count);
+wxString s;
+s << "Param " << count << ": " << param;
+wxLogMessage(s);
count++;
if (!projectSpecified) //next parameter must be new script file
{
@@ -396,6 +405,10 @@
{
m_frame->RunBatch();
}
+#ifdef __WXMAC__
+wxArrayString emptyFiles;
+OSXStoreOpenFiles(emptyFiles);
+#endif
return true;
}
[hugin-ptx] Re: Mac Build
Hello, > Does it then works? Does it also works when starting from finder? > >From Hugin, it makes no difference but it still works perfectly with Finder. (I don't know if it's important, but MacOpenFiles gets always called after the first text in the log window appears.) Niklas -- 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/0ad93a66-ab79-4826-b66d-6c4c2bc72638%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Hi Niklas,
Am Donnerstag, 26. Mai 2016 20:19:38 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas,
>
> PTBatcher opens the specified project correctly but when it starts
> stitching, MacOpenFiles get called with the prefix. There are two
> possibilities:
>
I have an idea number 3:
comment out lines 224-234 in PTBatcherGUI.cpp
#if 0 // def __WXMAC__
// see PTBatcherGUI::MacOpenFile for explanation
m_macFileNameToOpenOnStart = wxT("");
wxYield();
if(!m_macFileNameToOpenOnStart.IsEmpty())
{
wxFileName fn(m_macFileNameToOpenOnStart);
m_frame->AddToList(fn.GetFullPath());
}
else
#endif
Does it then works? Does it also works when starting from finder?
Thomas
--
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/ad0f2bbe-8894-4d34-b8ff-f40ca60507aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Hi Thomas, PTBatcher opens the specified project correctly but when it starts stitching, MacOpenFiles get called with the prefix. There are two possibilities: 1. a hack in MacOpenFiles to not add files without a extension or 2.(the better one) Why does it get called at all? Note that it doesn't make any difference either if Hugin calls PTG or if I call it via bash with the same command as hugin ( /Users/niklas/development/cmake/build/src/hugin1/ptbatcher/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI -b -v "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto" "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692" ) Niklas argv 0: /Users/niklas/development/cmake/build/src/hugin1/ptbatcher/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI argv 1: -b argv 2: -v argv 3: /Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto argv 4: /Users/niklas/Desktop/pano/DSC_5691 - DSC_5692 Am Mittwoch, 25. Mai 2016 17:53:42 UTC+2 schrieb T. Modes: > > Hi Niklas, > > Am Dienstag, 24. Mai 2016 20:45:57 UTC+2 schrieb Niklas Mischkulnig: >> >> Thomas, I rolled back to wxWidgets 3.0. >> Can I hardcode wxColour col(128,128,128) (dark grey, how it looked >> previously) >> because that color isn't available via wxSYS_COLOUR_?*?*? in 3.1? >> > Yes, no problem, if you like. Maybe wrapping into #if defined __WXMAC__ && > wxCHECK_VERSION(3,1,0) > >> >> When I call it like this, the log windows opens, the cursor turns into a >> watch and I can't do anything, because it tries to stitch the >> first (=invalid) project file(see below), code in repository calls >> PTBatcherGUI this way. >> PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI -b -v >> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692" >> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto" >> > > I changed the order in Hugin back. So it's in sync with Windows and Linux > again. I was still wondering why it worked on Mac with the false order. > > >> >> This way(arguments swapped), it gets added once correctly and the second >> entry has the prefix as the projectfile and "first image - last image" as >> output prefix: >> PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI -b -v >> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto" >> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692" >> >> If you checked already the call from hugin, we have to go a step further > and debug it in PTBatcherGUI. Could you apply the attached patch and then > call PTBatcherGUI from Hugin. This should print a window with the > parameters PTBatcherGUI gets. Maybe this shed some light on the issue. > > Thomas > -- 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/c26a817d-438c-45cf-89be-4aa3293f237a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Hi Niklas,
Am Dienstag, 24. Mai 2016 20:45:57 UTC+2 schrieb Niklas Mischkulnig:
>
> Thomas, I rolled back to wxWidgets 3.0.
> Can I hardcode wxColour col(128,128,128) (dark grey, how it looked
> previously)
> because that color isn't available via wxSYS_COLOUR_?*?*? in 3.1?
>
Yes, no problem, if you like. Maybe wrapping into #if defined __WXMAC__ &&
wxCHECK_VERSION(3,1,0)
>
> When I call it like this, the log windows opens, the cursor turns into a
> watch and I can't do anything, because it tries to stitch the
> first (=invalid) project file(see below), code in repository calls
> PTBatcherGUI this way.
> PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI -b -v
> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692"
> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto"
>
I changed the order in Hugin back. So it's in sync with Windows and Linux
again. I was still wondering why it worked on Mac with the false order.
>
> This way(arguments swapped), it gets added once correctly and the second
> entry has the prefix as the projectfile and "first image - last image" as
> output prefix:
> PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI -b -v
> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto"
> "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692"
>
> If you checked already the call from hugin, we have to go a step further
and debug it in PTBatcherGUI. Could you apply the attached patch and then
call PTBatcherGUI from Hugin. This should print a window with the
parameters PTBatcherGUI gets. Maybe this shed some light on the issue.
Thomas
--
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/7d1ac7dc-92aa-4664-a10c-b61757d57e91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# HG changeset patch
# Parent 5422e269f546cdad9d305767a1e608420d10bcf3
diff --git a/src/hugin1/ptbatcher/PTBatcherGUI.cpp b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
--- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
@@ -167,6 +167,12 @@
};
wxCmdLineParser parser(cmdLineDesc, argc, argv);
+for (int i = 0; i < argc; ++i)
+{
+wxString s;
+s << "argv " << i << ": " << argv[i];
+wxLogMessage(s);
+};
switch ( parser.Parse() )
{
case -1: // -h or --help was given, and help displayed so exit
@@ -267,6 +273,9 @@
while (parser.GetParamCount() > count)
{
wxString param = parser.GetParam(count);
+wxString s;
+s << "Param " << count << ": " << param;
+wxLogMessage(s);
count++;
if (!projectSpecified) //next parameter must be new script file
{
[hugin-ptx] Re: Mac Build
Hello, https://drive.google.com/uc?export=download=0B_seRjFxxDleN2V2VDVnS0hoSXc Christian, please test if it runs. Everything should work fine as long as you don't open PTBatcherGUI via Hugin's "Stitch Panorama..." button. Thomas, I rolled back to wxWidgets 3.0. Can I hardcode wxColour col(128,128,128) (dark grey, how it looked previously) because that color isn't available via wxSYS_COLOUR_?*?*? in 3.1? When I call it like this, the log windows opens, the cursor turns into a watch and I can't do anything, because it tries to stitch the first (=invalid) project file(see below), code in repository calls PTBatcherGUI this way. PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI -b -v "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692" "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto" This way(arguments swapped), it gets added once correctly and the second entry has the prefix as the projectfile and "first image - last image" as output prefix: PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI -b -v "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692.pto" "/Users/niklas/Desktop/pano/DSC_5691 - DSC_5692" Niklas Am Montag, 23. Mai 2016 10:11:11 UTC+2 schrieb Christian Krüger: > > Hi guys, > > I was really happy that I found this thread and that you guys are putting > serious effort into getting Hugin to run on Mac (I have tried to compile > myself but ran into problem after problem). > > I downloaded your pack but it requires 10.11 and I have only 10.10 :-( > > Do you guys also have a version that runs on 10.10? That would be really > great! > > Cheers > Christian > -- 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/e9ef5c8e-abbf-451d-ac0a-9fe5a2813087%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Hi guys, I was really happy that I found this thread and that you guys are putting serious effort into getting Hugin to run on Mac (I have tried to compile myself but ran into problem after problem). I downloaded your pack but it requires 10.11 and I have only 10.10 :-( Do you guys also have a version that runs on 10.10? That would be really great! Cheers Christian -- 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/10c37b42-2bdd-42ef-84a5-c15a44ac2caa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: Mac Build
On 28.04.2016 23:36, Sukima wrote: > I don't wish to detract this thread to much from finding a stable build > for Mac users but when that task is complete it leaves a burning > question: How does the Hugin community prevent such a tragedy in the > future? I think that there is only one way: participation. The sources of the development version of Hugin are freely available and can be compiled by any user on any operating system she or he are interested in. I, for example, do nightly builds for several Ubuntu versions. So whenever something breaks these builds, I can speak up. And I get plenty of help from other builders and Thomas, the main developer, in these cases. This results in much less problems showing up when a release happens. These nightly builds are scripted and run with no interaction required every night. Of course, when something breaks I have to interfere. And as my are targeted towards the Ubuntu crowd, the actual building and distribution is automated, curtsey of the invaluable launchpad.net infrastructure. However, if anyone is interested in the scripts, they are available at https://stefanpe...@bitbucket.org/stefanpeter/nightly4hugin.git Producing nightly builds for your operating system of choice has another benefit: There are much more users involved in beta testing when nightly builds are available. So the overall quality of Hugin increases by following the opensource mantra "release early, release often". Of course, nightly builds of the development version may be broken from time to time. So if you plan to offer these for your operating system of choice, make sure there is a fall back option in the form of a stable version that can be installed. And please communicate this fact to your end users. Regards Stefan Peter -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? (See https://en.wikipedia.org/wiki/Posting_style for details) -- 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/57262280.9010003%40swissonline.ch. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
I want to thank everyone who is contributing to the mac build endeavour. I've made a few attempts to compile from source over the pas year or so, and while I may have come close I never ended up with a functional application. I'm not a software engineer, and haven't built mac apps, so this isn't really very surprising. I've checked back every few months, and was delighted to find this thread. Reading through it made me very very grateful for your collective efforts. It is easy to forget how advances in open source software are made by individual people from all over the world, one patch at a time, on threads like this one. I'm not sure if or how I can be of assistance other than by breaking stuff, and if that's the case, want to express my sincere gratitude for having stuff to break in the first place. Much respect to you all. On Friday, April 1, 2016 at 11:45:28 PM UTC-7, Niklas Mischkulnig wrote: > > Why hasn't there been a Mac build on sourceforge for over one year (there > isn't a windows build for the 2016.0.0 yet)? > -- 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/7e3c1689-a43a-4571-92ce-18b1a8426fae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: Mac Build
Yes a really really big thanks to Niklas for the work to get this compiled and to Thomas for doing the debugging. Don't give up you two. We Mac users are relying on you. Don JohnstonSent from my Samsung device Original message From: "T. Modes" <thomas.mo...@gmx.de> Date: 2016-04-29 9:04 AM (GMT-06:00) To: hugin and other free panoramic software <hugin-ptx@googlegroups.com> Subject: [hugin-ptx] Re: Mac Build Hi Sukima, Am Donnerstag, 28. April 2016 23:36:47 UTC+2 schrieb Sukima:I don't wish to detract this thread to much from finding a stable build for Mac users but when that task is complete it leaves a burning question: How does the Hugin community prevent such a tragedy in the future? If there was a way to keep the source up-to-date then building a release binary would not be difficult as there are enough developers out there with XCode. It's vice versa. The source code was still working at Mac OS. But nobody of the many Mac OS users was able and willing (until now) to build it. There are some minor glitches which can be easily solved if someone build on Mac OS. Thomas -- 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/bae3d91b-80f1-4d31-b0e1-549c89065688%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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/hlbi8fenmi5ft5rkjkyo8fbi.1461974688585%40email.android.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Hi Sukima, Am Donnerstag, 28. April 2016 23:36:47 UTC+2 schrieb Sukima: > > I don't wish to detract this thread to much from finding a stable build > for Mac users but when that task is complete it leaves a burning question: > How does the Hugin community prevent such a tragedy in the future? > > If there was a way to keep the source up-to-date then building a release > binary would not be difficult as there are enough developers out there with > XCode. > It's vice versa. The source code was still working at Mac OS. But nobody of the many Mac OS users was able and willing (until now) to build it. There are some minor glitches which can be easily solved if someone build on Mac OS. Thomas -- 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/bae3d91b-80f1-4d31-b0e1-549c89065688%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
I don't wish to detract this thread to much from finding a stable build for Mac users but when that task is complete it leaves a burning question: How does the Hugin community prevent such a tragedy in the future? If there was a way to keep the source up-to-date then building a release binary would not be difficult as there are enough developers out there with XCode. But changing the code of something that a) uses open-gl which has a long history of destroying any sanity one might have had (mainly from graphics card drivers that are near impossible manage; see Lunis's reaction to Nvidia on that point) and b) does math on digital photography which is best left to the realm of PHDs, Adobe employees, and Gods! That diatribe aside, I'd love to see how the Mac specific source code can be kept up-to-date with the Hugin core so binaries can easily be made and mirrors can be uploaded to. Thoughts, ideas? BTW thank you so much for taking it on to make a Mac build of 2016. The old version is almost unusable on El Capitain. and I've yet to get a working linux virtualbox running well enough to manage the intensity needed by a panorama stitcher! On Saturday, April 2, 2016 at 2:45:28 AM UTC-4, Niklas Mischkulnig wrote: > > Why hasn't there been a Mac build on sourceforge for over one year (there > isn't a windows build for the 2016.0.0 yet)? > -- 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/7f12356c-5a26-42a4-8882-6edf07e9cc2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Niklas and everyone, Thank you so much for working on this! I'm testing the April 18 build downloaded from Google Drive... same problem as others with embedded color profiles. (I stripped profiles out of my images so I could continue to test.) I am so happy to be using something besides 2014.0.0. I will post back with other issues if I encounter any. Thanks again for taking this on, Dale -- 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/92385579-54cc-4fb9-b094-942cd6a8ee83%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Mac Build
Here is a (hopefully working) build (version 2016) . Please test it and tell me if something crashes (there might still be a wrong dylib install path lurking in a dark corner :D ). https://www.dropbox.com/s/oi6etuyobwkxwbb/Hugin.zip?dl=1 Am Samstag, 2. April 2016 08:45:28 UTC+2 schrieb Niklas Mischkulnig: > > Why hasn't there been a Mac build on sourceforge for over one year (there > isn't a windows build for the 2016.0.0 yet)? > -- 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/b54aec89-34a4-4cbd-a43e-5f7722dfb213%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: mac build: not yet, still having problems
Hi Steve, Thanks for replying. You can get the up-to-date code from the hugin svn: svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk hugin. My modified XCode project is not in SVN yet as that svn XCode project is working for 0.7. I might overwrite it as that 0.7 doesn't work anyway anymore. I could also mail you the XCode project. I have the issue as mentioned in my previous post, that is with celeste and new stuff from gsoc 2008, but without PTBatcher and PTBatcherGui. PTBatcher and PTBatcherGui really want to run wx-config which is undesired behaviour in an Xcode project (but can be implemented). I made PTBatcher and PTBatcherGui my second goal in life, but wanted to get the Xcode project running with celeste to start with. So, do you want me to mail the XCode project? Harry 2008/10/31 stwf [EMAIL PROTECTED] Hi I'd like to take a look. Is the hugin project checked in now? Is there anywhere I can get the up to date code and try and recreate the problem? 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: mac build: not yet, still having problems
Hi I'd like to take a look. Is the hugin project checked in now? Is there anywhere I can get the up to date code and try and recreate the problem? 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
