Windows installer release 2009.2 ?

[Lars Schimmer-4]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Is there any official release of latest stable hugin available for windows?

The webpage http://hugin.sourceforge.net/ is kinda strange.
In the headline release 2009.2 is announced, under news ony
2009.2.0_beta4 is announced.

Under the download location http://hugin.sourceforge.net/download/ only
windows 0.7.0 (kinda ancient) is noted, even Mac OSx is 0.8.0.
And sources are noted.

For windows only snapshots and unofficial build >0.7.0 are noted, but
the windows bin link follows to http://hugin.huikeshoven.org/ which
tells me "only vista, highly experimental" for >0.8.0.

Is there no stable (general) windows binary release >0.7.0 available at all?

MfG,
Lars Schimmer
- --
- -------------------------------------------------------------
TU Graz, Institut für ComputerGraphik & WissensVisualisierung
Tel: [phone]       E-Mail: l.schimmer@...
Fax: [phone]       PGP-Key-ID: 0x4A9B1723
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrdsLYACgkQmWhuE0qbFyPpqgCeNVVk1zuzLImvhuz0XoEsP4Ep
8QYAnArOFvSIRrlnXo1196ZINIaqdwdo
=xEYi
-----END PGP SIGNATURE-----

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Nicolas Pelletier-4]

I think the information stated here still stands:

http://panospace.wordpress.com/2009/08/11/give-a-man-a-fish/

You can still get less official builds from Ad H.

I don't know what problems with enblend enfuse are still present (or if they are fixed in 4.0) but I think APSift-C should be released with a version without the leaks,and without the "new" problems... but this is from my memory, so may not be right.

I'm running from the latest from Ad H. it crashes big time on windows, but does deliver the output (aka save often).

nick

On Tue, Oct 20, 2009 at 8:44 AM, Lars Schimmer <l.schimmer@...> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Is there any official release of latest stable hugin available for windows?

The webpage http://hugin.sourceforge.net/ is kinda strange.
In the headline release 2009.2 is announced, under news ony
2009.2.0_beta4 is announced.

Under the download location http://hugin.sourceforge.net/download/ only
windows 0.7.0 (kinda ancient) is noted, even Mac OSx is 0.8.0.
And sources are noted.

For windows only snapshots and unofficial build >0.7.0 are noted, but
the windows bin link follows to http://hugin.huikeshoven.org/ which
tells me "only vista, highly experimental" for >0.8.0.

Is there no stable (general) windows binary release >0.7.0 available at all?

MfG,
Lars Schimmer
- --
- -------------------------------------------------------------
TU Graz, Institut für ComputerGraphik & WissensVisualisierung
Tel: [phone]       E-Mail: l.schimmer@...
Fax: [phone]       PGP-Key-ID: 0x4A9B1723
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrdsLYACgkQmWhuE0qbFyPpqgCeNVVk1zuzLImvhuz0XoEsP4Ep
8QYAnArOFvSIRrlnXo1196ZINIaqdwdo
=xEYi
-----END PGP SIGNATURE-----

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Carl von Einem-2]

A friend who uses Vista64 somehow received a link to the Ad H. .exe and
apart from difficulties with CP generators (I think it's about setting
those up in the prefs) hugin seems to work on his machine.

I'll better send him the advice to save often, though... :-)

Carl

Nicolas Pelletier wrote:

> I think the information stated here still stands:
>
> http://panospace.wordpress.com/2009/08/11/give-a-man-a-fish/
>
> <http://panospace.wordpress.com/2009/08/11/give-a-man-a-fish/>You can
> still get less official builds from Ad H.
>
> I don't know what problems with enblend enfuse are still present (or if
> they are fixed in 4.0) but I think APSift-C should be released with a
> version without the leaks,and without the "new" problems... but this is
> from my memory, so may not be right.
>
> I'm running from the latest from Ad H. it crashes big time on windows,
> but does deliver the output (aka save often).

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Yuval Levy-6]

hallo Lars,

Lars Schimmer wrote:
> For windows only snapshots and unofficial build >0.7.0 are noted, but
> the windows bin link follows to http://hugin.huikeshoven.org/ which
> tells me "only vista, highly experimental" for >0.8.0.
>
> Is there no stable (general) windows binary release >0.7.0 available at all?

Nicolas gave you the short answer: No. With a little bit of fiddling you
can make the experimental builds work for you, but they are not of the
same stability / quality as the 0.7.0 and the critical criteria to be
uploaded to SF and distributed as official is real stability, not just
"declared stability" (as in: the project has released them).

Long answer: There are four issues that make a Windows binary installer
complex. Build-time dependencies; Run-time dependencies; the Installer
itself; and last but not least the SDK, that brings them all together.

A Windows binary release must also ship other run-time dependencies
because of the lack of proper package management system on that
platform. On platforms with a package manager, the four issues are taken
automatically care of..

Around the time of the 0.7.0 we had a lucky combination of really stable
dependencies; up to date Installer scripts; and users from the Windows
community willing to go through the pains of a systematic and clean
build (that was myself and Guido. In the end his binaries were uploaded
to SF). Since then things have been wacky. They may improve by the end
of the year.

Current status:

BUILD-TIME DEPENDENCIES

1. Libpano is the critical build-time dependency. Bleeding edge features
require the latest libpano. The current 2.9.15_beta3 is acceptable
(although there have been further fixes committed, so better wait for
the next tarball). In between the repository was broken and either does
not build or may result in faulty Hugin binaries.

2. Other build time dependencies don't improve as fast; tracking their
improvements is not critical. The current SDK (by Guido) should be good
enough to build Hugin. Using slightly older dependencies only affects
marginally the end-user experience and is acceptable.


RUN-TIME DEPENDENCIES

There are two critical run-time dependencies: Enblend, and (optional) a
control point generator.

1. Enblend is the critical run-time dependency. At the time of releasing
Hugin 0.7.0 we were lucky that the Enblend repository was in a stable
state. After that, Enblend 3.2 has been released and there are reports
that it is a regression compared to the pre 3.2 snapshots. To compile an
  Hugin installer Enblend must be present inside the SDK. Unfortunately
the most recent SDK does not have what it take to build Enblend. Joachim
is expanding the SDK to build Enblend from the repository. Enblend is
now in the final stages of polishing / cleaning up bugs ahead of the 4.0
release. There is no guaranteed release date, the stated objective is to
release before year end. No guarantee.

2. There are a bunch of options for the control point generator. The
problem is that all of those that work are covered by some patent (SIFT
or SURF) in some jurisdictions, making their distribution a hot potato.
Although a control point generator is an optional dependency, most
end-user consider it mandatory. The script to compile the 0.7.0
installer had two variations, one with and one without CP generators.
I've expressed the view that in the future it would be good to do the
same as for OSX and release separate Windows binary installers for Hugin
and for the CP generators.

3. Autopano-SIFT-C is the last incarnation of the CP generator
traditionally associated with Hugin. The current status is that the
previous "stable" release (2.5.0) had serious memory leaks and crashed
on large projects. The current development snapshot of 2.5.2 is broken,
and there is no guaranteed date for the fix (Tom said he has no time
before the end of the year). As an interim solution we've branched out
2.5.1 (currently release candidate 2, could be declared final any time).

4. Autopano-SIFT-C is covered by the SIFT patent in some countries. The
patent holder, UBC, allows use for "educational purposes". I do not
recall if also for "non-commercial purposes". The patent is the reason
why popular mainstream Linux distributions such as Debian and Fedora
don't carry Autopano-SIFT-C.

5. A better control points generator is Pano-O-matic. It is covered by
the SURF patent. You can find it on the web, but it is very unlikely
that it will make it into the official Hugin binary distribution. You
can make it work for you if you know what you are doing.

6. We still don't have a patent-free, open sourced control points
generator. Some parts have been produced during Google Summer of Code
2007 and 2008, but work still needs to be done and there is nobody
working on that at the moment, AFAIK.


WINDOWS INSTALLER

Since I added the 0.7.0 installer scripts to Hugin's codebase I changed
platform and the scripts were practically orphaned. All installers
circulating after 0.7.0 are modified versions and until not long ago the
modifications where not even back in the codebase. Allard has committed
his modified version recently. It has not been tested/verified by
anybody else.

All of these issues can be solved. Some of them are related to the
Hugin/Enblend/Libpano/Autopano-SIFT-C codebase. We're solving these. The
new parallel development cycle of Hugin works well, trunk is in better
state than ever and we can branch out regularly quite stable release
codelines. Libpano seems to be going a similar way, with 2.9.15 branched
out as a separate codeline. This bodes well for future stability. Bruno
stabilized an Autopano-SIFT-C interim release and Chris is taking care
of Enblend.

Some of them are platform specific and are left to volunteers on that
platform. Harry has been the driving force behind OSX. We have not had a
driving force behind Windows since 0.7.0. Some Windows users are
contributing valuable code (Thomas), build (Allard, Ad, Joachim), SDK
(Guido, Ryan), and testing (too many to name, and sorry if I forgot
somebody contributing code, build, SDK work). But nobody is really
taking it all the way to a proper and clean binary release. It's a lot
of work, not to be underestimated. It takes more time than just syncing
the repositories and building; and for those like me who have access to
multiple platforms, it is time taken from other priorities.

I hope this is shed some light on the situation...

> - -------------------------------------------------------------
> TU Graz, Institut für ComputerGraphik & WissensVisualisierung

... at such an institute you should have students / assistants /
professors with the skill to build Windows code?

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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[RizThon]

FYI I'm on Win XP Pro SP3 and I use Version 2009.1.0.4240 Ad Huikeshoven. I made several panoramas with it and it never crashed (but I most probably don't use all the features).
If I remember correctly I tried one of the new "highly experimental alpha" and it crashed really fast, so I went back to the first non alpha.
HTH

On Wed, Oct 21, 2009 at 04:03, Yuval Levy <google@...> wrote:

hallo Lars,

Lars Schimmer wrote:
> For windows only snapshots and unofficial build >0.7.0 are noted, but
> the windows bin link follows to http://hugin.huikeshoven.org/ which
> tells me "only vista, highly experimental" for >0.8.0.
>
> Is there no stable (general) windows binary release >0.7.0 available at all?

Nicolas gave you the short answer: No. With a little bit of fiddling you
can make the experimental builds work for you, but they are not of the
same stability / quality as the 0.7.0 and the critical criteria to be
uploaded to SF and distributed as official is real stability, not just
"declared stability" (as in: the project has released them).

Long answer: There are four issues that make a Windows binary installer
complex. Build-time dependencies; Run-time dependencies; the Installer
itself; and last but not least the SDK, that brings them all together.

A Windows binary release must also ship other run-time dependencies
because of the lack of proper package management system on that
platform. On platforms with a package manager, the four issues are taken
automatically care of..

Around the time of the 0.7.0 we had a lucky combination of really stable
dependencies; up to date Installer scripts; and users from the Windows
community willing to go through the pains of a systematic and clean
build (that was myself and Guido. In the end his binaries were uploaded
to SF). Since then things have been wacky. They may improve by the end
of the year.

Current status:

BUILD-TIME DEPENDENCIES

1. Libpano is the critical build-time dependency. Bleeding edge features
require the latest libpano. The current 2.9.15_beta3 is acceptable
(although there have been further fixes committed, so better wait for
the next tarball). In between the repository was broken and either does
not build or may result in faulty Hugin binaries.

2. Other build time dependencies don't improve as fast; tracking their
improvements is not critical. The current SDK (by Guido) should be good
enough to build Hugin. Using slightly older dependencies only affects
marginally the end-user experience and is acceptable.


RUN-TIME DEPENDENCIES

There are two critical run-time dependencies: Enblend, and (optional) a
control point generator.

1. Enblend is the critical run-time dependency. At the time of releasing
Hugin 0.7.0 we were lucky that the Enblend repository was in a stable
state. After that, Enblend 3.2 has been released and there are reports
that it is a regression compared to the pre 3.2 snapshots. To compile an
 Hugin installer Enblend must be present inside the SDK. Unfortunately
the most recent SDK does not have what it take to build Enblend. Joachim
is expanding the SDK to build Enblend from the repository. Enblend is
now in the final stages of polishing / cleaning up bugs ahead of the 4.0
release. There is no guaranteed release date, the stated objective is to
release before year end. No guarantee.

2. There are a bunch of options for the control point generator. The
problem is that all of those that work are covered by some patent (SIFT
or SURF) in some jurisdictions, making their distribution a hot potato.
Although a control point generator is an optional dependency, most
end-user consider it mandatory. The script to compile the 0.7.0
installer had two variations, one with and one without CP generators.
I've expressed the view that in the future it would be good to do the
same as for OSX and release separate Windows binary installers for Hugin
and for the CP generators.

3. Autopano-SIFT-C is the last incarnation of the CP generator
traditionally associated with Hugin. The current status is that the
previous "stable" release (2.5.0) had serious memory leaks and crashed
on large projects. The current development snapshot of 2.5.2 is broken,
and there is no guaranteed date for the fix (Tom said he has no time
before the end of the year). As an interim solution we've branched out
2.5.1 (currently release candidate 2, could be declared final any time).

4. Autopano-SIFT-C is covered by the SIFT patent in some countries. The
patent holder, UBC, allows use for "educational purposes". I do not
recall if also for "non-commercial purposes". The patent is the reason
why popular mainstream Linux distributions such as Debian and Fedora
don't carry Autopano-SIFT-C.

5. A better control points generator is Pano-O-matic. It is covered by
the SURF patent. You can find it on the web, but it is very unlikely
that it will make it into the official Hugin binary distribution. You
can make it work for you if you know what you are doing.

6. We still don't have a patent-free, open sourced control points
generator. Some parts have been produced during Google Summer of Code
2007 and 2008, but work still needs to be done and there is nobody
working on that at the moment, AFAIK.


WINDOWS INSTALLER

Since I added the 0.7.0 installer scripts to Hugin's codebase I changed
platform and the scripts were practically orphaned. All installers
circulating after 0.7.0 are modified versions and until not long ago the
modifications where not even back in the codebase. Allard has committed
his modified version recently. It has not been tested/verified by
anybody else.

All of these issues can be solved. Some of them are related to the
Hugin/Enblend/Libpano/Autopano-SIFT-C codebase. We're solving these. The
new parallel development cycle of Hugin works well, trunk is in better
state than ever and we can branch out regularly quite stable release
codelines. Libpano seems to be going a similar way, with 2.9.15 branched
out as a separate codeline. This bodes well for future stability. Bruno
stabilized an Autopano-SIFT-C interim release and Chris is taking care
of Enblend.

Some of them are platform specific and are left to volunteers on that
platform. Harry has been the driving force behind OSX. We have not had a
driving force behind Windows since 0.7.0. Some Windows users are
contributing valuable code (Thomas), build (Allard, Ad, Joachim), SDK
(Guido, Ryan), and testing (too many to name, and sorry if I forgot
somebody contributing code, build, SDK work). But nobody is really
taking it all the way to a proper and clean binary release. It's a lot
of work, not to be underestimated. It takes more time than just syncing
the repositories and building; and for those like me who have access to
multiple platforms, it is time taken from other priorities.

I hope this is shed some light on the situation...

> - -------------------------------------------------------------
> TU Graz, Institut für ComputerGraphik & WissensVisualisierung

... at such an institute you should have students / assistants /
professors with the skill to build Windows code?

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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Nicolas Pelletier-4]

"5. A better control points generator is Pano-O-matic. It is covered by
the SURF patent. You can find it on the web, but it is very unlikely
that it will make it into the official Hugin binary distribution. You
can make it work for you if you know what you are doing."

That was new to me. I tried it (we need a 64 bit version of this to use up all CPU and don't get into memory problems) and for the first time in months, I had 2 bad control points... not 200 or 2000...

This will be a keeper. As for the windows version... I'll continue my setup and see if\how I can help.

nick

On Tue, Oct 20, 2009 at 8:32 PM, RizThon <rizthon@...> wrote:

FYI I'm on Win XP Pro SP3 and I use Version 2009.1.0.4240 Ad Huikeshoven. I made several panoramas with it and it never crashed (but I most probably don't use all the features).
If I remember correctly I tried one of the new "highly experimental alpha" and it crashed really fast, so I went back to the first non alpha.
HTH

On Wed, Oct 21, 2009 at 04:03, Yuval Levy <google@...> wrote:

hallo Lars,

Lars Schimmer wrote:
> For windows only snapshots and unofficial build >0.7.0 are noted, but
> the windows bin link follows to http://hugin.huikeshoven.org/ which
> tells me "only vista, highly experimental" for >0.8.0.
>
> Is there no stable (general) windows binary release >0.7.0 available at all?

Nicolas gave you the short answer: No. With a little bit of fiddling you
can make the experimental builds work for you, but they are not of the
same stability / quality as the 0.7.0 and the critical criteria to be
uploaded to SF and distributed as official is real stability, not just
"declared stability" (as in: the project has released them).

Long answer: There are four issues that make a Windows binary installer
complex. Build-time dependencies; Run-time dependencies; the Installer
itself; and last but not least the SDK, that brings them all together.

A Windows binary release must also ship other run-time dependencies
because of the lack of proper package management system on that
platform. On platforms with a package manager, the four issues are taken
automatically care of..

Around the time of the 0.7.0 we had a lucky combination of really stable
dependencies; up to date Installer scripts; and users from the Windows
community willing to go through the pains of a systematic and clean
build (that was myself and Guido. In the end his binaries were uploaded
to SF). Since then things have been wacky. They may improve by the end
of the year.

Current status:

BUILD-TIME DEPENDENCIES

1. Libpano is the critical build-time dependency. Bleeding edge features
require the latest libpano. The current 2.9.15_beta3 is acceptable
(although there have been further fixes committed, so better wait for
the next tarball). In between the repository was broken and either does
not build or may result in faulty Hugin binaries.

2. Other build time dependencies don't improve as fast; tracking their
improvements is not critical. The current SDK (by Guido) should be good
enough to build Hugin. Using slightly older dependencies only affects
marginally the end-user experience and is acceptable.


RUN-TIME DEPENDENCIES

There are two critical run-time dependencies: Enblend, and (optional) a
control point generator.

1. Enblend is the critical run-time dependency. At the time of releasing
Hugin 0.7.0 we were lucky that the Enblend repository was in a stable
state. After that, Enblend 3.2 has been released and there are reports
that it is a regression compared to the pre 3.2 snapshots. To compile an
 Hugin installer Enblend must be present inside the SDK. Unfortunately
the most recent SDK does not have what it take to build Enblend. Joachim
is expanding the SDK to build Enblend from the repository. Enblend is
now in the final stages of polishing / cleaning up bugs ahead of the 4.0
release. There is no guaranteed release date, the stated objective is to
release before year end. No guarantee.

2. There are a bunch of options for the control point generator. The
problem is that all of those that work are covered by some patent (SIFT
or SURF) in some jurisdictions, making their distribution a hot potato.
Although a control point generator is an optional dependency, most
end-user consider it mandatory. The script to compile the 0.7.0
installer had two variations, one with and one without CP generators.
I've expressed the view that in the future it would be good to do the
same as for OSX and release separate Windows binary installers for Hugin
and for the CP generators.

3. Autopano-SIFT-C is the last incarnation of the CP generator
traditionally associated with Hugin. The current status is that the
previous "stable" release (2.5.0) had serious memory leaks and crashed
on large projects. The current development snapshot of 2.5.2 is broken,
and there is no guaranteed date for the fix (Tom said he has no time
before the end of the year). As an interim solution we've branched out
2.5.1 (currently release candidate 2, could be declared final any time).

4. Autopano-SIFT-C is covered by the SIFT patent in some countries. The
patent holder, UBC, allows use for "educational purposes". I do not
recall if also for "non-commercial purposes". The patent is the reason
why popular mainstream Linux distributions such as Debian and Fedora
don't carry Autopano-SIFT-C.

5. A better control points generator is Pano-O-matic. It is covered by
the SURF patent. You can find it on the web, but it is very unlikely
that it will make it into the official Hugin binary distribution. You
can make it work for you if you know what you are doing.

6. We still don't have a patent-free, open sourced control points
generator. Some parts have been produced during Google Summer of Code
2007 and 2008, but work still needs to be done and there is nobody
working on that at the moment, AFAIK.


WINDOWS INSTALLER

Since I added the 0.7.0 installer scripts to Hugin's codebase I changed
platform and the scripts were practically orphaned. All installers
circulating after 0.7.0 are modified versions and until not long ago the
modifications where not even back in the codebase. Allard has committed
his modified version recently. It has not been tested/verified by
anybody else.

All of these issues can be solved. Some of them are related to the
Hugin/Enblend/Libpano/Autopano-SIFT-C codebase. We're solving these. The
new parallel development cycle of Hugin works well, trunk is in better
state than ever and we can branch out regularly quite stable release
codelines. Libpano seems to be going a similar way, with 2.9.15 branched
out as a separate codeline. This bodes well for future stability. Bruno
stabilized an Autopano-SIFT-C interim release and Chris is taking care
of Enblend.

Some of them are platform specific and are left to volunteers on that
platform. Harry has been the driving force behind OSX. We have not had a
driving force behind Windows since 0.7.0. Some Windows users are
contributing valuable code (Thomas), build (Allard, Ad, Joachim), SDK
(Guido, Ryan), and testing (too many to name, and sorry if I forgot
somebody contributing code, build, SDK work). But nobody is really
taking it all the way to a proper and clean binary release. It's a lot
of work, not to be underestimated. It takes more time than just syncing
the repositories and building; and for those like me who have access to
multiple platforms, it is time taken from other priorities.

I hope this is shed some light on the situation...

> - -------------------------------------------------------------
> TU Graz, Institut für ComputerGraphik & WissensVisualisierung

... at such an institute you should have students / assistants /
professors with the skill to build Windows code?

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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[allard-3]

Hi Lars & other windows users,

Yuv explained most if it pretty well, we're working on it but we could
use more help. I'm pretty close to bringing out a package that
combines some new hugin/libpano/autopanosift-c code with an old
version of Enblend, but I am doing it in a very sparse amount of spare
time, and on top of that I don't really know what I'm doing most of
the time. If that 'intermediate' solution turns out to work well we
can release it and Windows users will finally have an official version
with all the great new features. But I have thought before that I was
only a few days away, so it might take longer than you hope.

The control points generator patent issue is not specific to Windows.
The fact that you don't want to distribute things separately but in an
installer package complicates it, that's all.



--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[allard-3]

Yuv & others,

what i've built just now is a set of Windows binaries based on
hugin tarball 2009.2 release
libpano svn 1098 (=beta3 + small changes)
autopano sift c 2.5.1 RC1
enblend binaries from hugin 0.7 release

I could spend a bit more time on modifying the installscript and
bringing this out as a windows package release candidate. It would
need to be tested of course, but it wouldn't make sense for me or
others to spend time on it if
a) There is a obvious reason why this combination or parts of it won't
be stable for most users. I'm not keeping up well enough to be aware
of all the possible problems.
b) There is no consensus that it's a good idea to bring out such an
'intermediate' release that will bridge the time it takes to get new
stable versions of all the codebases (hugin, apsc, libpano, enblend)
for windows. If it's not going to show up in the big green square on
the hugin SF page I don't see much advantage over e.g. Ad's snapshots
and I won't pursue it any further.
--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Yuval Levy-6]

Hi Allard,

thank you for your effort.

allard wrote:
> what i've built just now is a set of Windows binaries based on
> hugin tarball 2009.2 release
> libpano svn 1098 (=beta3 + small changes)
> autopano sift c 2.5.1 RC1
> enblend binaries from hugin 0.7 release
>
> I could spend a bit more time on modifying the installscript

please do. make it two install scripts: separate autopano-SIFT-C from
the rest.

Looking back at my 0.7.0 script it was a mistake to try to make a single
installer with *everything* - and I had even planned a larger Mammoth
with Bruno's compiled Panotools-Scripts (Perl is not available by
default on Windows) and Jim's Photoshop plug-ins.

I ended up with a maintenance nightmare of two fully blown installer
scripts (the second was the "no patents" one).

Much better to make modular installers that try to be aware of each other.


> a) There is a obvious reason why this combination or parts of it won't
> be stable for most users. I'm not keeping up well enough to be aware
> of all the possible problems.

if you split autopano-sift-C from the rest, it makes sense to me.


> b) There is no consensus that it's a good idea to bring out such an
> 'intermediate' release that will bridge the time it takes to get new
> stable versions of all the codebases

that's the mistake: it's like waiting for Sun, Moon, and Earth to be
aligned for an eclipse.

'intermediate' release is a good idea. waiting to get new stable
versions of *all* the codebases not.

after the 'intermediate' release is out, the better idea IMO is to
continue *incrementally*

I currently see at least two increments:

- from my limited tests on Windows, the current pre-release 4 of
enblend/enfuse performs better to or equal than any 3.x. there will be
changes to the script to accomodate enblend 4.x and such an incremental
release would help to iron them out.

- 2009.4 is already near completition. waiting for the tarball to be
finished before starting preparing the installer is a mistake. Harry has
the ideal strategy with his OSX builds. He follows closely all tarballs
(including betas and rcs) so that the OSX version is ready for release
almost concurrently with the tarball final release.


> If it's not going to show up in the big green square on
> the hugin SF page I don't see much advantage over e.g. Ad's snapshots
> and I won't pursue it any further.

agree. IIRC I added the necessary permissions for you on SF. You have
all the tools to make it happen (upload the file and declare it release
for Windows).

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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Bruno Postle]

On Wed 21-Oct-2009 at 00:11 -0700, allard wrote:
>
>what i've built just now is a set of Windows binaries based on
>hugin tarball 2009.2 release
>libpano svn 1098 (=beta3 + small changes)

This is probably ok but Hugin 2009.2.0 (and 2009.4.0) should be fine
with the 2.9.14 libpano13.

>autopano sift c 2.5.1 RC1

Please can you use rc2, the only difference is that rc1 reports the
wrong version, which is just the sort of thing we don't want to
confuse people with.

--
Bruno

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to hugin-ptx+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---