Windows SDK + trunk = ?

[Oskar Sander]

Hi Brian,

How far off is the SDK for building hugin from trunk? I suppose enblend does not need to be built as described here [1] as there is a released (or RC) 4.0 now, right?

[1] http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK
 
Cheers

2009/12/13 brian_ims <im...@netspace.net.au>

I am not a C/C+ programmer but have managed to build a windows version using
SVN 4782 following the SDK and various other pointers given in this forum
and I can confirm that with the introduction of the autocrop button a
previously viewable button has essentially disappeared from my screen. If
Bruno is corrrect the culprit is the 'show control points' button and
presumably this needs shortening

Cheers

Brian

[brian_ims]

Oskar,

As I stated I am not a C/C+ programmer, make files cause my eyes to
glazeover and I don't understand subversion/trunks etc (but I have been
writing fortran for the best part of 35 years and still am). This was my
first attempt to build Hugin. I used the precompiled SDK and just followed
the instructions for building, downloading adding the compiled GLUT as
described some time ago, picking up the missing GLUT references manually
when running cmake and also putting glut.dll in the bin folder that is
produced by visual studio. I also had to rename a couple of the files in the
enblend folder (eg readme to readme.txt - I had copied enblend 4 into the
enblend3.2 folder by mistake some time ago and am not sure now if I had
overwritten some files or not)

I have no idea how to create installer files

Cheers

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

--
View this message in context: http://old.nabble.com/Windows-SDK-%2B-trunk-%3D---tp26832030p26841055.html
Sent from the hugin ptx mailing list archive at Nabble.com.

[Guido Kohlmeyer]

Dear all,

It seems the right way to build hugin as described by Brian.
So far as I know my SDK is outdated since some months, but lacks mainly
of a missing glut component which can be easily added as described in an
old post by me.
To build an installation package was not my task for long time. I only
built the 0.7.0 release package with a patched iss file from repository.
I suppose there are some other guys around who are more familiar with
current state of building an installation.

Guido

Am 18.12.09 10:32, schrieb brian_ims:

[Oskar Sander]

Cheers, please bear with my newbie questions:

I'm running through the procedure of [1], adding the tools and adding glut.  Starting with checking out HEAD from trunk (4847).

Now I'm running through the cmakesetup of [1],  however having pointed out the wxWidgets-2.8.9\lib\vc_lib  there are still some WX dependencies missing.  Are these redundant or should I change the wxWidget version included in the SDK?.   (The missing references are for example:  WX_dbgrid, WX_dbgridd,WX_mono,WX_odbc)

Also, I find no CMAKE_BUILD_TYPE, HUGIN_BUILDER and HUGIN_BUILDATE - Am I doing something wrong or has this changed since the instructions were written?

Finally, I thought that cmakesetup would trace all dependencies in the project, and that these paths would show up in the variables "advance values" option, but for example pano13.lib  does not.  How come? Is this dynamic linking? 


Cheers
/O

[1] http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK

2009/12/20 Guido Kohlmeyer <d...@gekko-design.de>

--
/O

[Steeve]

Oskar

At som e point in 2009 I had to change from wxWidget 2.8.9 to 2.8.10..
I assume I just downloaded this from the internet.

What are you actually trying to build? when you get; "The missing

references are for example: WX_dbgrid, WX_dbgridd,WX_mono,WX_odbc"

this was not a problem for me building Hugin, but I have seen this on
other projects..

The fields HUGIN_BUILDER and HUGIN_BUILDATE are just text fields for
the person doing the build and the date, they will appear in the
'about' screen. So I use my name, and the date I got code..
I have never had to set CMAKE_BUILD_TYPE? in the most recent build I
did, it was 'RelWithDebInfo'

The panotools library in the SDK is now out of date, and you'll need
to download and build the latest version of this.

Hope this is some help to you...

Regards
Stephen

> > >> hugin-ptx+...@googlegroups.com<hugin-ptx%2Bunsubscribe@googlegroups­.com>

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

> > hugin-ptx+...@googlegroups.com<hugin-ptx%2Bunsubscribe@googlegroups­.com>

> > For more options, visit this group at
> >http://groups.google.com/group/hugin-ptx
>
> --

> /O- Hide quoted text -
>
> - Show quoted text -

[Oskar Sander]

Thanks Steve,

That helps.  I'm still at the stage running Cmakesetup as described in the SDK wiki.   So the Not_found messages are from cmake, I have not yet started building.

But with your comment I realized that I'm working of an old version of the SDK that contained wxW 2.8.9.  I'll redo with the proper version.

Cheers

2010/1/4 Steeve <smb...@googlemail.com>

--
/O