Re: hugin-2009.4 win32 (cygming) build available - please test

T. Modes wrote:
> Hi Yuv
> 
> some weeks again, you wrote (http://groups.google.com/group/hugin-ptx/
> msg/06ce8acea695ef21):
> 
>>> Finally copy glut32.dll to hugin/bin-folder.
>> the current policy for the windows binary is to avoid DLHell and link
>> statically. This should not be too difficult to fix.
> 
> But now it's:
>> Using a prebuilt
>> glut32.dll should be fine.
> 
> Has the policy changed since August?

the policy has not changed. "Should be fine" only means that it does not 
make sense to make life difficult at the moment.

Should be fine to solve the problem at hand.

Once the problem at hand is solved, look at the next steps. One of the 
next steps may be to move to static builds.

I can only recommend the static build policy, but if Ryan (or anyone 
else) decides to go the dynamic linking way, they are free to do so.

As long as it does not stand in the way of the officially supported way 
of building Hugin (CMake / MSVC / static) I won't stand in their 
effort's way.

Currently mingw is not an officially supported way of building Hugin. 
This does not mean that it is forbidden, it only means that if the mingw 
build breaks, it's tough luck for those dependent on it (while if the 
MSVC build breaks, it is a show stopper).

The static linking policy has consequences on what is checked into trunk 
with regard to the CMake build. If the changes for Windows dynamic 
linking are conflicting with the choices in trunk, they can be 
maintained as a separate set of patches, or even branched out as 
separate SVN codeline.

It also has consequences on support. I am less inclined to deal with 
support requests ensuing from missing DLL problems and reserve myself 
the right to mark such bug reports as invalid and close them.

In short: policy is not about allowed and forbidden; it is about 
supported and unsupported; and about priorities in case of trade offs.

As you can see from this thread, even if mingw is not officially 
supported, it gets attention.

You may wonder about my personal priorities (giving support to Ryan's 
unsupported effort while people are waiting for the RC3 release).

In terms of my personal priorities, mingw has much less priority than 
MSVC; but a person that is mostly self-sufficient and moves forward 
proactively has higher priority than passive consumers. And when mixing 
the two, people are more important than code.

Policies are easier to change than attitudes. I welcome people with 
Ryan's attitude, and in my choice of how to allocate my time I am more 
inclined to help him than to fix and release RC3.

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