Hi Kornel, thanks for the tips. I got it running now even after
rolling back the insertions in the ptcommon and ptblender files.
Just the _FILE_ thing still needs my manual fiddling.

See also below

> What is your compiler, maybe we could do it compiler-dependent

I work with Visual C++ express edition 2008 and whatever is the
default compiler for that.
>
> > In fftn.c, the following line of code produced 'not found' errors
> > # include __FILE__
>
> How is it possible, that _FILE_ does not expand to a valid path on your 
> system?

I don't know, but it seems to be a more common problem given the
commented line of code there

>
> This Debug-folder was new to me. Somehow I start to think, that even cmake is 
> very platform independent.
> Don't have here appropiate windows machine, so cannot help much.
>
> You may try add this library in tools/CMakeLists.txt
>
> line 18++:
>         if(WIN32)
>                 list(APPEND commands panoinfo)
>                 list(APPEND _common_libs ../Debug/pano13.lib)
>         endif()
>

I think this problem has already been solved in 1098 so this is no
longer necessary
>
> Here I would add tools/compat_win32/getopt.c to the list of sources ov pano13 
> lib
>
> like (from line 46 on):
>         IF(WIN32)
>                 SET(wxWidgets_ROOT_DIR ${SOURCE_BASE_DIR}/wxWidgets-2.8.10)
>                 ADD_DEFINITIONS(-D__Win__)
>                 FIND_PACKAGE(wxWidgets REQUIRED)
>                 SET(win_c  tools/compat_win32/getopt.c)
>         ENDIF(WIN32)
>
That works! Thanks, allard
--~--~---------~--~----~------------~-------~--~----~
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@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

Reply via email to