Hi Tom and Ryan
Another note: As it stands, there are a few patches required to 3rd
party libs that go beyond .sln file mods, and actually touch source
code. From what various people have said, and the convention in use for
the do-it-yourself SDK, I understand that the desired option is to
download the unmodified source code of a specific version from a given
library's main repository, then apply hugin-specific patches if needed.
Is there general agreement with this (or at least lack of
disagreement)?
That's the best strategy, IMO, as it allows for flexibility to change/update
the library in the future, and hopefully eliminate the patches once they
become unnecessary (most are minor, I think the closest anything gets to
'major' is just patching the wxWidgets config for third-party libraries)
I also think, that is the most flexible solution for the moment. So
everybody which wish can then easily build "its" SDK.
Currently there are only very few people which build hugin on windows.
When there is a compiled version for windows available this number will
further drop.
Thomas
--
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
