Hi Yuv,
Thanks for that - my Sourceforge user id is "glastonbury". I noticed the
chatter re Hg, and I'm set up ready to pull a copy of the repo when it's
ready. Like you other developers, I too have limited time (most of mine
is happily sucked up by a 2.5yr old son :-) ), but I'll do what I can to
get it going.
I note that there are no official Win32 (let alone x64) builds for 0.8.0
and 2010.0. Is there a reason for this other than lack of someone to
produce them? Would it make sense for me to (attempt to) produce them?
I was interested to read that the idea worked on in the past for the Win
SDK is based around a script that downloads 3rd party source/binaries as
needed. I'll see what I can find in the Wiki, but notably I'd be
interested to know which scripting system was being suggested - perhaps
NSIS is a good choice?
The other issue that I've mentioned before is that of producing x64 and
Win32 builds from one source tree/SDK. It seems to me that the hugin
CMake stuff will differentiate between debug and release libs (at least
for some 3rd party dependencies), but not for 32 vs 64 bit - it
generally seems to look for and generate link info for "somelib.lib" and
"somelibd.lib", but not "somelib32.lib", "somelib32d.lib",
"somelib64.lib" and "somelib64d.lib". Ideally, I'd like to be able to
freely choose between any combo of x64/Win32 and Debug/Release within
Visual Studio, and have the build process work. Is there a CMake master
in the project who might be able to comment on this?
Thanks,
Tom
On 16/05/2010 9:59 PM, Yuv wrote:
On May 14, 7:25 am, Tom Glastonbury<[email protected]> wrote:
I'd like to hear from any active developers/admins at the Sourceforge
project about the possibility of getting the changes mentioned in my
original post checked in, and updating the SDK instructions on the
wiki.
Hi Tom,
I'm sorry nobody got back to you yet - we're all in our spare time
here, so replies tend to take some time.
Thank you for your contribution. Yes, the windows build (and
specifically the 64bit one) could use some love and attention and your
time and effort are appreciated.
Thomas Modes has committed some of your changes to the codebase. If
you post your Sourceforge user name here, I'll add you to the
project's contributors so that you can make your changes directly.
We're currently transitioning from a Subversion-based repository to a
Mercurial-based one - you'll be pushing your changes to Mercurial.
For the SDK, there have been on and off discussions with previous
win32 and win64 contributors to maintain and update a set of scripts
to build it. We even opened an Hg repository for this, but... well...
look at it yourself: http://hugin.hg.sourceforge.net/hgweb/hugin/windowsSDK/
Ideally there should be there a batch script to download the necessary
source or binary files to the right location and put together the SDK.
Bits and pieces are spread in the past three years of archives of this
mailing list. Pieces are in the Hugin main repo. Pieces are in the
Wiki and its history. And pieces are missing.
For the Wiki, account opening is self-service and you're welcome to
edit what you deem necessary. It has a natural tendency to become
obsolete as documentation does not always have the high priority it
deserves and contributor's time is limited.
Again, thank you for your effort, and welcome to the team if you want
to join the active team of builders / developers.
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 [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
