[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found
Thanks Guido Installing CMake 2.6.3 did the trick. Thank you very much for setting up this build environment. I know how much work it took! -- Tom --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found
But now another problem. The install script is failing because there
is no enblend in my build.
There now seems to be conditional code in cmake_install.cmake for
various components, such as enblend; however it doesn't seem to
work. Here is the block for enblend:
IF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
FILE(INSTALL DESTINATION ${CMAKE_INSTALL_PREFIX}/doc/enblend TYPE
FILE FILES
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/AUTHORS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/ChangeLog
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/COPYING
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/NEWS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README_WINDOWS.txt
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/TODO
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/VIGRA_LICENSE
)
ENDIF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
That DIR-NOTFOUND suggests that something higher up in the script
generating chain is not doing its job.
Either CMake support for installing is not good enough, or we aren't
using it right. Or both.
BTW where am I supposed to get enblend, and how integrate it in the
build? Could I do somethng similar for autopano-sift-c?
-- Tom
On Feb 26, 9:14 am, Tom Sharpless tksharpl...@gmail.com wrote:
Thanks Guido
Installing CMake 2.6.3 did the trick.
Thank you very much for setting up this build environment. I know how
much work it took!
-- Tom
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found
Hi Tom,
enblend is the second pitfall to trip into. I included it not in the
SDK, but I know this was a fault.
You can download it here:
http://downloads.sourceforge.net/enblend/enblend-enfuse-3.2.zip
Decompress it to SDK's directory, that the application is in directory
enblend-enfuse-3.2.
Autopano-sift-C is missing too, but the install script will work without
it. You can simply use the version 2.5.0 that was already included in
hugin 0.7.0 distribution.
Guido
Tom Sharpless schrieb:
PS I guess the faulty script is hugin/CMakeModules/win-bundle.cmake.
On Feb 26, 1:18 pm, Tom Sharpless tksharpl...@gmail.com wrote:
But now another problem. The install script is failing because there
is no enblend in my build.
There now seems to be conditional code in cmake_install.cmake for
various components, such as enblend; however it doesn't seem to
work. Here is the block for enblend:
IF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
FILE(INSTALL DESTINATION ${CMAKE_INSTALL_PREFIX}/doc/enblend TYPE
FILE FILES
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/AUTHORS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/ChangeLog
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/COPYING
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/NEWS
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README_WINDOWS.txt
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/TODO
J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/VIGRA_LICENSE
)
ENDIF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT}
STREQUAL Unspecified)
That DIR-NOTFOUND suggests that something higher up in the script
generating chain is not doing its job.
Either CMake support for installing is not good enough, or we aren't
using it right. Or both.
BTW where am I supposed to get enblend, and how integrate it in the
build? Could I do somethng similar for autopano-sift-c?
-- Tom
On Feb 26, 9:14 am, Tom Sharpless tksharpl...@gmail.com wrote:
Thanks Guido
Installing CMake 2.6.3 did the trick.
Thank you very much for setting up this build environment. I know how
much work it took!
-- Tom
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found
Dear Tom, please use CMake 2.6.3 which has an updated script to find wxWidgets. The script in CMake 2.6.2 searched for only some of the libraries, but in the SDK the Unicode libs are only available. In the new CMake version the script will find all varaints of libs. Additionally the old script has problems to find the libs, if they are generated using the Visual Studio GUI, becuase some files are not created, which are build if you use the command line approach. Nevertheless, currently I prepare a detailed description to build the Hugin SDK with Visual C++ 2008. I hope that this information will be available on panotools wiki until this weekend. Guido With Guido's new SDK and the current Hugin svn, I get a basic cmakesetup configuration error: wxWidgets not found; plus a lot of consequential ones if I try to fix by hand -- and if I do that until cmakesetup says OK, the wxWidgets include directory is still not in the MSVC projects, so hugin1 etct won't build. I always use a separate build tree, so as to keep the source tree clean. Both are rooted in the same directory that contains the SDK. Does anybody know what is wrong? Thanks, -- Tom --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found
Dear Tom,
I should be sufficient to copy the attached file to directory
CMakeInstallDir\share\cmake-2.6\Modules and to rename it to
FindwxWidgets.cmake
Guido
With Guido's new SDK and the current Hugin svn, I get a basic
cmakesetup configuration error: wxWidgets not found; plus a lot of
consequential ones if I try to fix by hand -- and if I do that until
cmakesetup says OK, the wxWidgets include directory is still not in
the MSVC projects, so hugin1 etct won't build.
I always use a separate build tree, so as to keep the source tree
clean. Both are rooted in the same directory that contains the SDK.
Does anybody know what is wrong?
Thanks, -- Tom
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
# - Find a wxWidgets (a.k.a., wxWindows) installation.
# This module finds if wxWidgets is installed and selects a default
# configuration to use. wxWidgets is a modular library. To specify the
# modules that you will use, you need to name them as components to
# the package:
#
# FIND_PACKAGE(wxWidgets COMPONENTS base core ...)
#
# There are two search branches: a windows style and a unix style. For
# windows, the following variables are searched for and set to
# defaults in case of multiple choices. Change them if the defaults
# are not desired (i.e., these are the only variables you should
# change to select a configuration):
#
# wxWidgets_ROOT_DIR - Base wxWidgets directory
#(e.g., C:/wxWidgets-2.6.3).
# wxWidgets_LIB_DIR - Path to wxWidgets libraries
#(e.g., C:/wxWidgets-2.6.3/lib/vc_lib).
# wxWidgets_CONFIGURATION - Configuration to use
#(e.g., msw, mswd, mswu, mswunivud, etc.)
#
# For unix style it uses the wx-config utility. You can select between
# debug/release, unicode/ansi, universal/non-universal, and
# static/shared in the QtDialog or ccmake interfaces by turning ON/OFF
# the following variables:
#
# wxWidgets_USE_DEBUG
# wxWidgets_USE_UNICODE
# wxWidgets_USE_UNIVERSAL
# wxWidgets_USE_STATIC
#
# The following are set after the configuration is done for both
# windows and unix style:
#
# wxWidgets_FOUND- Set to TRUE if wxWidgets was found.
# wxWidgets_INCLUDE_DIRS - Include directories for WIN32
# i.e., where to find wx/wx.h and
# wx/setup.h; possibly empty for unices.
# wxWidgets_LIBRARIES- Path to the wxWidgets libraries.
# wxWidgets_LIBRARY_DIRS - compile time link dirs, useful for
# rpath on UNIX. Typically an empty string
# in WIN32 environment.
# wxWidgets_DEFINITIONS - Contains defines required to compile/link
# against WX, e.g. -DWXUSINGDLL
# wxWidgets_CXX_FLAGS- Include dirs and ompiler flags for
# unices, empty on WIN32. Esentially
# `wx-config --cxxflags`.
# wxWidgets_USE_FILE - Convenience include file.
#
# Sample usage:
# FIND_PACKAGE(wxWidgets COMPONENTS base core gl net)
# IF(wxWidgets_FOUND)
# INCLUDE(${wxWidgets_USE_FILE})
# # and for each of your dependant executable/library targets:
# TARGET_LINK_LIBRARIES(YourTarget ${wxWidgets_LIBRARIES})
# ENDIF(wxWidgets_FOUND)
#
# If wxWidgets is required (i.e., not an optional part):
# FIND_PACKAGE(wxWidgets REQUIRED base core gl net)
# INCLUDE(${wxWidgets_USE_FILE})
# # and for each of your dependant executable/library targets:
# TARGET_LINK_LIBRARIES(YourTarget ${wxWidgets_LIBRARIES})
#
# FIXME: check this and provide a correct sample usage...
#Remember to connect back to the upper text.
# Sample usage with monolithic wx build:
#
# FIND_PACKAGE(wxWidgets COMPONENTS mono)
# ...
# NOTES
#
# This module has been tested on the WIN32 platform with wxWidgets
# 2.6.2, 2.6.3, and 2.5.3. However, it has been designed to
# easily extend support to all possible builds, e.g., static/shared,
# debug/release, unicode, universal, multilib/monolithic, etc..
#
# If you want to use the module and your build type is not supported
# out-of-the-box, please contact me to exchange information on how
# your system is setup and I'll try to add support for it.
#
# AUTHOR
#
# Miguel A. Figueroa-Villanueva (miguelf at ieee dot org).
# Jan Woetzel (jw at mip.informatik.uni-kiel.de).
#
# Based on previous works of:
# Jan Woetzel (FindwxWindows.cmake),
#
