wxvtk-users Mailing List for wxVTKRenderWindowInteractor (Page 15)
Brought to you by:
malat
Menu
▾
▴
wxvtk-users — wxVTK users
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(7) |
Feb
|
Mar
(2) |
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(13) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(6) |
Jul
(3) |
Aug
(11) |
Sep
|
Oct
(10) |
Nov
(2) |
Dec
(1) |
| 2007 |
Jan
(16) |
Feb
(9) |
Mar
(13) |
Apr
|
May
(7) |
Jun
(8) |
Jul
|
Aug
(14) |
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2008 |
Jan
(20) |
Feb
(1) |
Mar
|
Apr
(20) |
May
(5) |
Jun
(11) |
Jul
|
Aug
(52) |
Sep
(2) |
Oct
(35) |
Nov
(7) |
Dec
(14) |
| 2009 |
Jan
(4) |
Feb
(5) |
Mar
(9) |
Apr
(19) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(5) |
Dec
|
| 2010 |
Jan
(1) |
Feb
(5) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(13) |
| 2012 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
|
From: Mathieu M. <mat...@gm...> - 2006-08-04 04:31:57
|
Hi, Sorry for such a long wait, I kind of lost interest in the project :( This is basically the source from the CVS that has been sitting there for a while. The only real change is the patch from Alexander Nip (Thank you !). I finally decided to give another try at the Modules from CMake and decided it was time to drop support for GTK 1.2.x. What this means is that the project assume you are using GTK 2.x to compile (from CMake prospective), but the code remained the same! So if you know what you are doing you can still compile wxVTKRenderWindowInteractor.cxx. Let me know if this is a problem (I doubt there is still anyone using GTK 1.2.x). As a side note how many of you are using: * VTK 4.4 and before * VTK 5.0 and after Ref: http://sourceforge.net/forum/forum.php?forum_id=598047 Thank you all for your patience ! -- Mathieu |
|
From: Nigel N. <nN...@au...> - 2006-08-03 16:38:54
|
Hi Jonas, I guess you are using a recent CVS version of wxVTKR.W.I., e.g. Module: $RCSfile: wxVTKRenderWindowInteractor.cxx,v $ Language: C++ Date: $Date: 2005/10/18 03:37:00 $ Version: $Revision: 1.22 $ With so many variations of cmake, Vtk, wx and wxVtk, please let us know if you solved your problem (and if so, what steps you took). On the other hand, since wxVTK only adds a single class to a user's project, I simply add the [.cxx,.h] files to my Vtk-based modules and side-step the various potential cmake complexities... > It all compiles but when linking Sample.exe I get a lot of > 'undefined reference' (one of them is 'undefined reference > to 'wxClassInfo::Register()''). If you are interested in a more manual approach, you might start with a simple and robust wxApp, with all settings consistent with your environment; then add the two files, wxVTKRenderWindowInteractor.h wxVTKRenderWindowInteractor.cxx and paste in some of the Sample code. I started this way; things evolved quickly into a fantastic wx+Vtk simulation environment. Nigel ----------------------------------------------------------------------------= ---------=0A= This message is intended for the addressee named and may contain confidentia= l and privileged information. If you are not the intended recipient please= note that any form of distribution, copying or use of this communication or= the information in it is strictly prohibited and may be unlawful. If you r= eceive this message in error, please delete it and notify the sender.=0A= Keep up to date with what's happening in Australian sport.=0A= Visit http://www.ausport.gov.au=0A= ----------------------------------------------------------------------------= --------- |
|
From: Jonas W. <jon...@gm...> - 2006-07-28 22:11:07
|
I'm trying to compile the wxVTK package, but gets a linking error when
linking Sample.exe when running make. This is my configuration:
- VTK 4.4.2 compiled and installed in four different configurations (debug,
debug+static, release and release+static) in /usr/local/
- wxWidgets 2.6.3 alsp compiled and installed in four different
configurations (debug, debug+static, release and release+static) in
/usr/local/
- ccmake version 2.2-patch 3
- All using the latest CygWin in WindowsXP
I get five (one for each sample in wxVTK) warnings when generating in
ccmake:
Warning: Ignoring path found in link libraries for target: Sample, the path
is : /usr/local/lib. Expected a library name or full path to a library name=
.
It all compiles but when linking Sample.exe I get a lot of 'undefined
reference' (one of them is 'undefined reference to
`wxClassInfo::Register()=B4).
I've tried forcing the linker flags to the output of `wx-config --libs=B4 w=
ith
no success:
CMAKE_EXE_LINKER_FLAGS:STRING=3D-L/usr/local/lib -lwx_msw_xrc-2.6 -lwx_msw_=
qa-
2.6 -lwx_msw_html-2.6 -lwx_msw_adv-2.6 -lwx_msw_core-2.6
-lwx_base_xml-2.6-lwx_base_net-
2.6 -lwx_base-2.6
The only progress I could make was to add the linking info directly into
CMakeFiles/Sample.dir/build.make but this isn't nice coding:
bin/Sample.exe: CMakeFiles/Sample.dir/build.make
@echo "Linking CXX executable bin/Sample.exe"
$(CMAKE_COMMAND) -E remove -f bin/Sample.exe
c++ -Wno-deprecated -mwin32 -L/usr/local/lib
-lwx_msw_xrc-2.6-lwx_msw_qa-
2.6 -lwx_msw_html-2.6 -lwx_msw_adv-2.6 -lwx_msw_core-2.6
-lwx_base_xml-2.6-lwx_base_net-
2.6 -lwx_base-2.6 $(Sample_OBJECTS) $(Sample_EXTERNAL_OBJECTS) -o
bin/Sample.exe -L/cygdrive/c/apps/wxVTK/bin -L/usr/lib/w32api
-L/usr/local/lib/vtk -lvtkIO -lvtkHybrid -lvtkCommon -lvtkGraphics
-lvtkRendering -lcomctl32 -lrpcrt4 -lwsock32 -lopengl32 -lglu32
-lvtkGraphics -lvtkImaging -lvtkIO -lvtkFiltering -lvtkCommon -lpthread
-lgdi32 -lm -lvtkDICOMParser -lvtkpng -lvtktiff -lvtkzlib -lvtkjpeg
-lvtkexpat -lvtkftgl -lvtkfreetype -lglu32 -lopengl32
So my final question is; how do i solve the linking problem to wxWidget?
This is the CMakeCache file in the wxVTK directory
---------------------------------------------------------------------
# This is the CMakeCache file.
# For build in directory: /cygdrive/c/apps/wxVTK
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=3DVALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUI's for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.
########################
# EXTERNAL cache entries
########################
//Library is used for debug links only
/cygdrive/c/apps/wxWidgets-2.6.3/build-static-debug_LINK_TYPE:STATIC=3Ddebu=
g
//Library is used for debug links only
/cygdrive/c/apps/wxWidgets-2.6.3
/build-static-release/lib_LINK_TYPE:STATIC=3Doptimized
//Library is used for debug links only
/cygdrive/c/apps/wxWidgets-2.6.3
/build-static-release_LINK_TYPE:STATIC=3Doptimized
//Library is used for both debug and optimized links
/usr/local/lib_LINK_TYPE:STATIC=3Dgeneral
//Path to a program.
CMAKE_AR:FILEPATH=3D/usr/bin/ar
//For backwards compatibility, what version of CMake commands and
// syntax should this version of CMake allow.
CMAKE_BACKWARDS_COMPATIBILITY:STRING=3D2.2
//Build type imported from VTK.
CMAKE_BUILD_TYPE:STRING=3DCMAKE_CXX_FLAGS_RELEASE
//C++ compiler
CMAKE_CXX_COMPILER:STRING=3Dc++
//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=3D
//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=3D-g
//Flags used by the compiler during release minsize builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=3D-Os -DNDEBUG
//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_CXX_FLAGS_RELEASE:STRING=3D-O3 -DNDEBUG
//Flags used by the compiler during Release with Debug Info builds.
//
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=3D-O2 -g
//C compiler
CMAKE_C_COMPILER:STRING=3Dgcc
//Flags for C compiler.
CMAKE_C_FLAGS:STRING=3D
//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=3D-g
//Flags used by the compiler during release minsize builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=3D-Os -DNDEBUG
//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_C_FLAGS_RELEASE:STRING=3D-O3 -DNDEBUG
//Flags used by the compiler during Release with Debug Info builds.
//
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=3D-O2 -g
//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=3D-L/usr/local/lib -lwx_msw_xrc-2.6 -lwx_msw_=
qa-
2.6 -lwx_msw_html-2.6 -lwx_msw_adv-2.6 -lwx_msw_core-2.6
-lwx_base_xml-2.6-lwx_base_net-
2.6 -lwx_base-2.6
//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=3D
//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=3D
//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=3D
//Flags used by the linker during Release with Debug Info builds.
//
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=3D
//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=3D/usr/local
//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=3D/usr/bin/make
//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=3D
//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=3D
//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=3D
//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=3D
//Flags used by the linker during Release with Debug Info builds.
//
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=3D
//Path to a program.
CMAKE_RANLIB:FILEPATH=3D/usr/bin/ranlib
//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=3D
//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=3D
//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=3D
//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=3D
//Flags used by the linker during Release with Debug Info builds.
//
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=3D
//If set, runtime paths are not added when using shared libraries.
//
CMAKE_SKIP_RPATH:BOOL=3DOFF
//If true, cmake will use relative paths in makefiles and projects.
//
CMAKE_USE_RELATIVE_PATHS:BOOL=3DOFF
//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make. This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=3DOFF
//Single output directory for building all executables.
EXECUTABLE_OUTPUT_PATH:PATH=3D/cygdrive/c/apps/wxVTK/bin
//Single output directory for building all libraries.
LIBRARY_OUTPUT_PATH:PATH=3D/cygdrive/c/apps/wxVTK/bin
//The directory containing VTKConfig.cmake. This is either the
// root of the build tree, or PREFIX/lib/vtk for an installation.
// For VTK 4.0, this is the location of UseVTK.cmake. This is
// either the root of the build tree or PREFIX/include/vtk for
// an installation.
VTK_DIR:PATH=3D/usr/local/lib/vtk
//What is the path where the file wx/wx.h can be found
WXWINDOWS_INCLUDE_DIR:PATH=3D/usr/local/include/wx-2.6
//What is the path where the file wx/setup.h can be found
WXWINDOWS_INCLUDE_DIR_SETUPH:PATH=3D/usr/local/lib/wx/include/msw-
ansi-debug-2.6
//What is the path where the file include/wx/wx.h can be found
WXWINDOWS_ROOT_DIR:PATH=3D/usr/local/lib/wx
//Set additional defines for wxWindows
WXWINDOWS_SET_DEFINITIONS:BOOL=3DOFF
//wxWindows shared debug build library
WXWINDOWS_SHARED_DEBUG_LIBRARY:FILEPATH=3D/usr/local/lib
//wxWindows shared release build library
WXWINDOWS_SHARED_LIBRARY:FILEPATH=3D/usr/local/lib
//wxWindows static debug build library
WXWINDOWS_STATIC_DEBUG_LIBRARY:FILEPATH=3D/usr/local/lib
//wxWindows static release build library
WXWINDOWS_STATIC_LIBRARY:FILEPATH=3D/usr/local/lib
//Use shared versions (dll) of wxWindows libraries?
WXWINDOWS_USE_SHARED_LIBS:BOOL=3DON
//Value Computed by CMake
wxVTKSample_BINARY_DIR:STATIC=3D/cygdrive/c/apps/wxVTK
//Value Computed by CMake
wxVTKSample_SOURCE_DIR:STATIC=3D/cygdrive/c/apps/wxVTK
########################
# INTERNAL cache entries
########################
//Advanced flag for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_BUILD_TOOL
CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=3D1
//What is the target build tool cmake is generating for.
CMAKE_BUILD_TOOL:INTERNAL=3D/usr/bin/make
//This is the directory where this CMakeCahe.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=3D/cygdrive/c/apps/wxVTK
//Major version of cmake used to create the current loaded cache
//
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3D2
//Minor version of cmake used to create the current loaded cache
//
CMAKE_CACHE_MINOR_VERSION:INTERNAL=3D2
//Major version of cmake used to create the current loaded cache
//
CMAKE_CACHE_RELEASE_VERSION:INTERNAL=3Dpatch 3
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=3D/usr/bin/cmake
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=3D/usr/bin/ctest
//Advanced flag for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=3D1
//full path to the compiler cmake found
CMAKE_CXX_COMPILER_FULLPATH:INTERNAL=3D/usr/bin/c++
CMAKE_CXX_COMPILER_WORKS:INTERNAL=3D1
//Advanced flag for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=3D1
//full path to the compiler cmake found
CMAKE_C_COMPILER_FULLPATH:INTERNAL=3D/usr/bin/gcc
CMAKE_C_COMPILER_WORKS:INTERNAL=3D1
//Advanced flag for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=3D1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=3D/usr/bin/ccmake
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=3D1
//Modified flag for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
//
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
//
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=3D1
//Name of generator.
CMAKE_GENERATOR:INTERNAL=3DUnix Makefiles
//Start directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=3D/cygdrive/c/apps/wxVTK
//Advanced flag for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
//
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
//
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
//
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=3D1
//number of local generators
CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=3D1
//Advanced flag for variable: CMAKE_RANLIB
CMAKE_RANLIB-ADVANCED:INTERNAL=3D1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=3D/usr/share/cmake-2.2.3
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
//
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
//
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
//
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=3D1
//Result of TRY_RUN
CMAKE_SIZEOF_VOID_P:INTERNAL=3D4
//Advanced flag for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=3D1
//uname command
CMAKE_UNAME:INTERNAL=3D/usr/bin/uname
//Advanced flag for variable: CMAKE_USE_RELATIVE_PATHS
CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: EXECUTABLE_OUTPUT_PATH
EXECUTABLE_OUTPUT_PATH-ADVANCED:INTERNAL=3D1
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_VOID_P:INTERNAL=3DTRUE
//Advanced flag for variable: LIBRARY_OUTPUT_PATH
LIBRARY_OUTPUT_PATH-ADVANCED:INTERNAL=3D1
//Path to an executable
Sample_CMAKE_PATH:INTERNAL=3D/cygdrive/c/apps/wxVTK
//Path to an executable
SplitSample_CMAKE_PATH:INTERNAL=3D/cygdrive/c/apps/wxVTK
//Modified flag for variable: VTK_DIR
VTK_DIR-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_INCLUDE_DIR
WXWINDOWS_INCLUDE_DIR-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_INCLUDE_DIR
WXWINDOWS_INCLUDE_DIR-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_INCLUDE_DIR_SETUPH
WXWINDOWS_INCLUDE_DIR_SETUPH-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_INCLUDE_DIR_SETUPH
WXWINDOWS_INCLUDE_DIR_SETUPH-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_ROOT_DIR
WXWINDOWS_ROOT_DIR-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_ROOT_DIR
WXWINDOWS_ROOT_DIR-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_SET_DEFINITIONS
WXWINDOWS_SET_DEFINITIONS-ADVANCED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_SHARED_DEBUG_LIBRARY
WXWINDOWS_SHARED_DEBUG_LIBRARY-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_SHARED_DEBUG_LIBRARY
WXWINDOWS_SHARED_DEBUG_LIBRARY-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_SHARED_LIBRARY
WXWINDOWS_SHARED_LIBRARY-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_SHARED_LIBRARY
WXWINDOWS_SHARED_LIBRARY-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_STATIC_DEBUG_LIBRARY
WXWINDOWS_STATIC_DEBUG_LIBRARY-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_STATIC_DEBUG_LIBRARY
WXWINDOWS_STATIC_DEBUG_LIBRARY-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_STATIC_LIBRARY
WXWINDOWS_STATIC_LIBRARY-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_STATIC_LIBRARY
WXWINDOWS_STATIC_LIBRARY-MODIFIED:INTERNAL=3D1
//Advanced flag for variable: WXWINDOWS_USE_SHARED_LIBS
WXWINDOWS_USE_SHARED_LIBS-ADVANCED:INTERNAL=3D1
//Modified flag for variable: WXWINDOWS_USE_SHARED_LIBS
WXWINDOWS_USE_SHARED_LIBS-MODIFIED:INTERNAL=3D1
//Path to an executable
wxImagePlaneWidget_CMAKE_PATH:INTERNAL=3D/cygdrive/c/apps/wxVTK
//Path to an executable
wxImageViewer_CMAKE_PATH:INTERNAL=3D/cygdrive/c/apps/wxVTK
//Path to an executable
wxMedical3_CMAKE_PATH:INTERNAL=3D/cygdrive/c/apps/wxVTK
-------------------------
|
|
From: Andres M. <mun...@gm...> - 2006-07-19 14:03:59
|
Hello everyone,
I posted this question on the VTK-Users list and was directed here.
Has any one experienced something similar using wxVTK on their Mac?
I'm using wxWidgets 2.6.3, VTK 5.0.
Regards,
Andres E. Munarriz Soto
>> Hello everyone,
>> I'm trying to read DICOM images using the vtkDICOMImageReader and
>> display it in a wxWidgets window. Everything seems to be working
>> ok except that the image isn't displayed at all. If I call the
>> viewer->Render() method a new window is opened but the image isn't
>> displayed either. I'm running MacOSX 10.4. I believe the code is
>> fine.
>> The following snippet is used to construct the wxWidget frame to
>> display the file (or series)
>>
>> ImageFrame::ImageFrame(wxMDIParentFrame *pp_Parent, const
>> wxString& p_strTitle, const wxPoint& p_Pos, const wxSize& p_Size,
>> const long p_lStyle):wxMDIChildFrame(pp_Parent, -1, p_strTitle,
>> p_Pos, p_Size, p_lStyle | wxNO_FULL_REPAINT_ON_RESIZE)
>> {
>> vtk_interactor = new wxVTKRenderWindowInteractor(
>> this, MDI_VTK_MINI_WINDOW);
>> vtk_interactor->UseCaptureMouseOn();
>> viewer = vtkImageViewer2::New();
>> viewer->SetupInteractor(vtk_interactor);
>> viewer->SetColorWindow(WINDOW_VALUE);
>> viewer->SetColorLevel(LEVEL_VALUE);
>> }
>> bool ImageFrame::OpenSeries(wxString path)
>> {
>> atImage = fachade->srvOpenSeries(path);
>> viewer->SetInput(atImage);
>> viewer->SetupInteractor(vtk_interactor);
>> // viewer->Update();
>> // viewer->Render();
>> return (atImage != NULL);
>> }
>>
>> the Fachada object returns a vtkImageData* after calling the
>> ImageProcessingCore OpenSeries method.
>>
>> vtkImageData* ImageProcessingCore::OpenSeries(const char* path){
>> reader->SetDirectoryName(path);
>> reader->Update(); return reader->GetOutput();
>> }
>> Thanks for your help in advance,
>> Andres E. Munarriz Soto
>> ---------------------------------------------------------------------
>> ---
>> _______________________________________________
>> This is the private VTK discussion list. Please keep messages on-
>> topic. Check the FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtkusers
>
|
|
From: Andres M. <mun...@gm...> - 2006-07-18 21:48:18
|
>> Hello everyone,
>> I'm trying to read DICOM images using the vtkDICOMImageReader and
>> display it in a wxWidgets window. Everything seems to be working
>> ok except that the image isn't displayed at all. If I call the
>> viewer->Render() method a new window is opened but the image isn't
>> displayed either. I'm running MacOSX 10.4. I believe the code is
>> fine.
>> The following snippet is used to construct the wxWidget frame to
>> display the file (or series)
>> ImageFrame::ImageFrame(wxMDIParentFrame *pp_Parent, const
>> wxString& p_strTitle, const wxPoint& p_Pos, const wxSize& p_Size,
>> const long p_lStyle):wxMDIChildFrame(pp_Parent, -1, p_strTitle,
>> p_Pos, p_Size, p_lStyle | wxNO_FULL_REPAINT_ON_RESIZE)
>> {
>> vtk_interactor = new wxVTKRenderWindowInteractor(
>> this, MDI_VTK_MINI_WINDOW);
>> vtk_interactor->UseCaptureMouseOn();
>> viewer = vtkImageViewer2::New();
>> viewer->SetupInteractor(vtk_interactor);
>> viewer->SetColorWindow(WINDOW_VALUE);
>> viewer->SetColorLevel(LEVEL_VALUE);
>> }
>> bool ImageFrame::OpenSeries(wxString path)
>> {
>> atImage = fachade->srvOpenSeries(path);
>> viewer->SetInput(atImage);
>> viewer->SetupInteractor(vtk_interactor);
>> // viewer->Update();
>> // viewer->Render();
>> return (atImage != NULL);
>> }
>> the Fachada object returns a vtkImageData* after calling the
>> ImageProcessingCore OpenSeries method.
>> vtkImageData* ImageProcessingCore::OpenSeries(const char* path){
>> reader->SetDirectoryName(path);
>> reader->Update(); return reader->GetOutput(); } thanks for
>> your help in advance,
>> Andres E. Munarriz Soto
>> ---------------------------------------------------------------------
>> ---
>> _______________________________________________
>> This is the private VTK discussion list. Please keep messages on-
>> topic. Check the FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtkusers
>
|
|
From: Zhiyong X. <zy...@ya...> - 2006-06-12 20:29:31
|
I still have trouble to compile sample code of wxVTK. It seems the include directory were not set in Visual C++ project file although cmake has wxWindows_Inlcude_dir correctly (but library not found). Here are what I used in my system: 1) wxWidget: version 2.6.3. Windows version. I downloaded wxMSW-2.6.3-Setup-1.exe and use visual c++ .NET to compile it. I have tried the cmake file provided in ftp://biolpc22.york.ac.uk/pub/contrib/cmake/. It not works for me. 2) wxVTK: I have tried version 0.8 and not works. I also tried latest version in CVS. which are: FindwxWidgets.cmake 1.8 and UseConfig.cmake 1.7. CMakeLists.txt 1.19. 3) vtk 5.0. Any help on this issue are appreaciated. Thanks Sean Mathieu Malaterre <mat...@gm...> wrote: I am pretty sure I saw this in the past... and I am pretty sure I fixed it. Could you try the CVS version of wxVTK. Instructions are here: http://sf.net/projects/wxvtk which seems to be now right now :( HTH Mathieu On 6/6/06, Zhiyong Xie wrote: > I tried to compile wxVTK using Visual C++ .Net. I got an error: > > error C2039: 'OnSize' : is not a member of 'wxWindow' > c:\wxWidgets-2.6.3\include\wx\msw\window.h(48) : see declaration of > 'wxWindow' > > > I use wxWidget-2.6.3 and VTK 4.2. Does anybody had meet same problem before? > > > After I comment the line wxWindow::OnSize(event); in > wxVTKRenderWindowInteractor.cxx > > it was compiled and worked fine. However, when I click exit, it crashed and > gave an information for > referencing memory at "0x000000e0" that could not be read. Does anyone know > how to fix it? > > > Thanks > > Sean > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > > > -- Mathieu __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Mathieu M. <mat...@gm...> - 2006-06-09 18:48:33
|
Very nice for looking into that issue. I remember this 'magic' --sync option in the past help me find out a couple of bug in the wxGTK code. Could you please open an issue in the bug tracker at: http://sourceforge.net/tracker/?group_id=114757 And if possible enclose the cvs dif: $ cvs -q -u3 -p diff Thanks Mathieu On 6/8/06, Alexander Nip <ale...@gm...> wrote: > Dear All, > > I would like to report what appears to be a race condition and a work > around, just in case I am not alone. I apologize if this has been > covered previously. > > I compiled the CVS version wxVTK on Fedora 4 and linked it dynamically > to the latest versions of VTK and wxGTK. When I executed any of the > sample programs, I would get the following X error and the program would > exit normally: > > The program 'Sample' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadWindow (invalid Window parameter)'. > (Details: serial 7 error_code 3 request_code 2 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() > function.) > > However, everything worked just fine as soon as I used the "--sync" > option. So I couldn't really get a useful backtrace from gdb. I did a > little bit of debugging and found that the OnPaint method was fired > prematurely (Skipping the first call and everything would work fine with > or without the --sync switch). I did a bit of web searching and > eventually solved the problem by sticking the following line right > before the Render() call in the OnPaint() method: > > this->SetCurrent(); > > Does this lead to other side effects? At least all Sample programs are > now working normally for me. > > > Alex > > > > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > -- Mathieu |
|
From: Alexander N. <ale...@gm...> - 2006-06-08 18:21:35
|
Dear All,
I would like to report what appears to be a race condition and a work
around, just in case I am not alone. I apologize if this has been
covered previously.
I compiled the CVS version wxVTK on Fedora 4 and linked it dynamically
to the latest versions of VTK and wxGTK. When I executed any of the
sample programs, I would get the following X error and the program would
exit normally:
The program 'Sample' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 7 error_code 3 request_code 2 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
However, everything worked just fine as soon as I used the "--sync"
option. So I couldn't really get a useful backtrace from gdb. I did a
little bit of debugging and found that the OnPaint method was fired
prematurely (Skipping the first call and everything would work fine with
or without the --sync switch). I did a bit of web searching and
eventually solved the problem by sticking the following line right
before the Render() call in the OnPaint() method:
this->SetCurrent();
Does this lead to other side effects? At least all Sample programs are
now working normally for me.
Alex
|
|
From: Mathieu M. <mat...@gm...> - 2006-06-07 20:23:48
|
I am pretty sure I saw this in the past... and I am pretty sure I fixed it. Could you try the CVS version of wxVTK. Instructions are here: http://sf.net/projects/wxvtk which seems to be now right now :( HTH Mathieu On 6/6/06, Zhiyong Xie <zy...@ya...> wrote: > I tried to compile wxVTK using Visual C++ .Net. I got an error: > > error C2039: 'OnSize' : is not a member of 'wxWindow' > c:\wxWidgets-2.6.3\include\wx\msw\window.h(48) : see declaration of > 'wxWindow' > > > I use wxWidget-2.6.3 and VTK 4.2. Does anybody had meet same problem before? > > > After I comment the line wxWindow::OnSize(event); in > wxVTKRenderWindowInteractor.cxx > > it was compiled and worked fine. However, when I click exit, it crashed and > gave an information for > referencing memory at "0x000000e0" that could not be read. Does anyone know > how to fix it? > > > Thanks > > Sean > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > > > -- Mathieu |
|
From: Nigel N. <nN...@au...> - 2006-06-07 19:03:29
|
Hi Sean,=0D=0A
=0D=0A
> I tried to compile wxVTK using Visual C++ .Net. I got an error:=0D=0A
>=0D=0A
> error C2039: 'OnSize' : is not a member of 'wxWindow'=0D=0A
> c:\wxWidgets-2.6.3\include\wx\msw\window.h(48) :=0D=0A
> see declaration of 'wxWindow'=0D=0A
=0D=0A
=0D=0A
The demo code with wxVTK is a great starting point you can use to get up=0D=
=0A
and running. Given that you are using such an olde version of Vtk with a=
=0D=0A
recent wxWidgets, you might need to adjust a few lines here and there...=0D=
=0A
=0D=0A
=0D=0A
> I use wxWidget-2.6.3 and VTK 4.2. Does anybody had meet same problem be=
fore?=0D=0A
>=0D=0A
> After I comment the line wxWindow::OnSize(event); in=0D=0A
> wxVTKRenderWindowInteractor.cxx it was compiled and worked fine.=0D=0A
> However, when I click exit, it crashed and gave an information for=0D=0A
> referencing memory at "0x000000e0" that could not be read.=0D=0A
> Does anyone know how to fix it?=0D=0A
=0D=0A
I fiddled with the cleanup code to make this go away. See the note=0D=0A
in the change log for wxVtk version 0.6 (9 July 2003)=0D=0A
=0D=0A
> Also, commented out pRenderer->Delete(). This kills the process,=0D=0A
> but I get same problem with the MFC version. (Vtk: Dec 14 2002) =0D=0A
> =0D=0A
> void MyFrame::DestroyVTK()=0D=0A
> {=0D=0A
> if (pRenderer) { =0D=0A
> // pRenderer->Delete(); ! Note: skip this line =0D=0A
> } =0D=0A
> ...=0D=0A
> }=0D=0A
=0D=0A
Nigel=0D=0A
=0D=0A
=0D=0A
-------------------------------------------------------------------------=
------------=0A
This message is intended for the addressee named and may contain confiden=
tial and privileged information. If you are not the intended recipient p=
lease note that any form of distribution, copying or use of this communic=
ation or the information in it is strictly prohibited and may be unlawful=
. If you receive this message in error, please delete it and notify the =
sender.=0A
Keep up to date with what's happening in Australian sport.=0A
Visit http://www.ausport.gov.au=0A
-------------------------------------------------------------------------=
------------=0A
=0D=0A
|
|
From: Zhiyong X. <zy...@ya...> - 2006-06-06 14:09:25
|
I tried to compile wxVTK using Visual C++ .Net. I got an error:
error C2039: 'OnSize' : is not a member of 'wxWindow'
c:\wxWidgets-2.6.3\include\wx\msw\window.h(48) : see declaration of 'wxWindow'
I use wxWidget-2.6.3 and VTK 4.2. Does anybody had meet same problem before?
After I comment the line wxWindow::OnSize(event); in wxVTKRenderWindowInteractor.cxx
it was compiled and worked fine. However, when I click exit, it crashed and gave an information for
referencing memory at "0x000000e0" that could not be read. Does anyone know how to fix it?
Thanks
Sean
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com |
|
From: Nigel N. <nn...@gm...> - 2006-05-06 15:52:06
|
Dear Mathieu, The MacFolks are heading for the runway; I'll let you know when they get some air-speed. Maybe some screenshots for wxVTK gallery... thanks again for wxVTK, Nigel On 5/6/06, Mathieu Malaterre <mat...@gm...> wrote: > I would not suggest GTK. Mac user are Mac users, they want there > Cocoa/Carbon apps :-P > Anyway I'd suggest Carbon, it is fairly more mature (in wxWidgets) and > should work out of the box. Make sure to have VTK5 since you wont be able to > have two renderwindow otherwise (in VTK44 + Carbon you could only get one > renderwindow). > > What happen when you compile the sample against a monolitithic > wxwdiget/carbon ? > > HTH > Mathieu > > > On 5/5/06, Nigel Nunn < nn...@gm...> wrote: > > > > Some Mac users are keen to try our simulator's wxVTK GUI. So far > > we've only built it on WinXP with VC++ 2003. Is anyone using wxVTK > > on a Mac? How do you suggest we start a Mac version of our app... > > Carbon, Cocoa or Gtk? > > thanks, > > Nigel > > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > > -- > Mathieu |
|
From: Mathieu M. <mat...@gm...> - 2006-05-05 17:38:13
|
I would not suggest GTK. Mac user are Mac users, they want there Cocoa/Carbon apps :-P Anyway I'd suggest Carbon, it is fairly more mature (in wxWidgets) and should work out of the box. Make sure to have VTK5 since you wont be able t= o have two renderwindow otherwise (in VTK44 + Carbon you could only get one renderwindow). What happen when you compile the sample against a monolitithic wxwdiget/carbon ? HTH Mathieu On 5/5/06, Nigel Nunn <nn...@gm...> wrote: > > Some Mac users are keen to try our simulator's wxVTK GUI. So far > we've only built it on WinXP with VC++ 2003. Is anyone using wxVTK on > a Mac? How do you suggest we start a Mac version of our app... > Carbon, Cocoa or Gtk? > thanks, > Nigel > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmdlnk&kid=120709&bid&3057&dat=121642 > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > -- Mathieu |
|
From: Nigel N. <nn...@gm...> - 2006-05-05 14:39:32
|
Some Mac users are keen to try our simulator's wxVTK GUI. So far we've only built it on WinXP with VC++ 2003. Is anyone using wxVTK on a Mac? How do you suggest we start a Mac version of our app... Carbon, Cocoa or Gtk? thanks, Nigel |
|
From: Nigel N. <nn...@gm...> - 2006-05-05 13:57:50
|
Hi Laurent,
VC++ has a .bat file for setting its command line paths. If you start
a console window and type:
vcvars32.bat
this should set the paths VC needs.
Another way to build wxWidgets is simply to adjust the flags in
setup.h, open the .sln solution file in Visual Studio, select DEBUG or
RELEASE, then choose [Rebuild Solution]. If you want a single
monolithic library, try adding:
MONOLITHIC=3D1
in the setup.h file.
Nigel
|
|
From: Laurent V. M. <L.V...@ul...> - 2006-05-05 12:27:49
|
<html> <body> Hello, <br><br> <br> I'm trying to build wxwidgets 2.6.3 under winXP and VC NET 7.1. I found the messages on the wxvtk users mailing about the compilation of wxwidgets running nmake.<br> I've downloaded the bat script from <br> <pre>Jan Woetzel=20 </pre>and launched it.<br> After a few path manipulation (dll, nmake wasn't in the path too, ..), i found an error which i can not resolve. Here the message, i added to the path the directory where stdio.h is included (C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include) but it still doesn't work.<br><br> c:\wxWidgets-2.6.3\src\regex\regcustom.h(32) : fatal error C1083: Impossible d'o<br> uvrir le fichier include : 'stdio.h' : No such file or directory<br> NMAKE : fatal error U1077: 'cl'=E1: code retour '0x2'<br><br> Do you have encountered such problem?<br> Do you have any suggestion?<br><br> thanks for your reply.<br><br> Best regards,<br><br> Laurent Van Miegroet<br> <x-sigsep><p></x-sigsep> <div align=3D"center"><font face=3D"arial" size=3D2> ____________________________________________________________________________= ______________________<br> <br> </div> <b>Laurent Van Miegroet</b> <br> Boursier Doctorant, Ir <br> LTAS - Service d'Ing=E9nierie des V=E9hicules Terrestres <br> Universit=E9 de Li=E8ge <br> Institut de M=E9canique et de G=E9nie Civil, B=E2t. B52 <br> Chemin des Chevreuils, 1 <br> B-4000 Li=E8ge, Belgique <br> T=E9l : +32.4.366.92.70 <br> Fax: +32.4.366.91.59 <br> E-Mail : <a href=3D"mailto:L.V...@UL...">L.V...@UL...</a> <br> URL: <a href=3D"http://www.ingveh.ulg.ac.be">www.ingveh.ulg.ac.be</a> <br> </font></body> </html> |
|
From: Oliver F. <o....@ac...> - 2005-11-25 06:35:49
|
I got the examples running... The problem was indeed that the library types
were mixed up. If I'm using only static libraries, everything works with no
worries. I've just one more question:
If I build the wxImagePlaneWidget with the header file
#include "vtkTestUtilities.h"
included I get the following error:
Compiling...
wxImagePlaneWidget.cxx
C:\VTK\Common\Testing\Cxx\vtkTestUtilities.h(19) : error C2011:
'vtkTestUtilities' : 'struct' type redefinition
C:\VTK\Rendering\vtkTesting.h(30) : see declaration of
'vtkTestUtilities'
If I just comment this line everything works fine.
What is this header fore? How can I get rid of the error message?
Thanks,
Oli
-----Original Message-----
From: wxv...@li...
[mailto:wxv...@li...] On Behalf Of Mathieu
Malaterre
Sent: Friday, 25 November 2005 5:23 AM
To: Oliver Frank
Cc: 'Jan Woetzel'; wxv...@li...
Subject: [wxVTK] Re: WX 2.6.2 Find script
Oliver,
I believe this is in the README file (Q2), mixing configuration is
tricky on Win32 (static and shared)
Happy Thanksgiving,
Mathieu
Oliver Frank wrote:
> Thanks guys!
>
> I got monolithical libraries and cmake is setting up the files with no
> worries...
>
> I opened the generated wxVTKSample.sln with Visual Studio and tried to
> comile it. Unfortunately I got the output attached and have no clue
> what's going wrong...
>
> Any help is very appreciated!
>
> Cheers,
> Oli
>
> ------ Build started: Project: wxImageViewer, Configuration: Debug
> Win32
> ------
>
> Compiling...
> wxVTKRenderWindowInteractor.cxx
> c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) :
> warning
> C4275: non dll-interface class 'wxWindow' used as base for
> dll-interface class 'wxVTKRenderWindowInteractor'
> C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see
> declaration of 'wxWindow'
> c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83)
> : see declaration of 'wxVTKRenderWindowInteractor'
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) :
> warning
> C4273: 'ms_classInfo' : inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : error
> C2491: 'wxVTKRenderWindowInteractor::ms_classInfo' : definition of
> dllimport static data member not allowed
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::GetClassInfo' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::wxCreateObject' : inconsistent
> dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) :
> warning
> C4273: 'sm_eventTable' : inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error
> C2491: 'wxVTKRenderWindowInteractor::sm_eventTable' : definition of
> dllimport static data member not allowed
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::GetEventTable' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) :
> warning
> C4273: 'sm_eventHashTable' : inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error
> C2491: 'wxVTKRenderWindowInteractor::sm_eventHashTable' : definition
> of dllimport static data member not allowed
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::GetEventHashTable' : inconsistent
> dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) :
> warning
> C4273: 'sm_eventTableEntries' : inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error
> C2491: 'wxVTKRenderWindowInteractor::sm_eventTableEntries' :
> definition of dllimport static data member not allowed
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(105) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' :
> inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(108) :
> warning
> C4355: 'this' : used in base member initializer list
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(130) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' :
> inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(133) :
> warning
> C4355: 'this' : used in base member initializer list
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(147) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::~wxVTKRenderWindowInteractor' :
> inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(151) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::New' : inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(157) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::Initialize' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(167) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::Enable' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(178) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::Disable' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(189) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::Start' : inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(196) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::UpdateSize' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(211) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::CreateTimer' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(221) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::DestroyTimer' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(227) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnTimer' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(241) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::GetHandle' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(300) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnPaint' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(318) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnEraseBackground' : inconsistent
> dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(324) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnSize' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(327) :
> error
> C2039: 'OnSize' : is not a member of 'wxWindow'
> C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see
> declaration of 'wxWindow'
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(346) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnMotion' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(364) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnEnter' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(384) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnLeave' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(404) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnKeyDown' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(433) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnKeyUp' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(461) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnButtonDown' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(517) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::OnButtonUp' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(574) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::Render' : inconsistent dll
> linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(611) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::SetRenderWhenDisabled' :
> inconsistent dll linkage
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(628) :
> warning
> C4800: 'int' : forcing value to bool 'true' or 'false' (performance
> warning)
> \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(636) :
> warning
> C4273: 'wxVTKRenderWindowInteractor::SetStereo' : inconsistent dll
> linkage wxImageViewer.cxx
> C:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) :
> warning
> C4275: non dll-interface class 'wxWindow' used as base for
> dll-interface class 'wxVTKRenderWindowInteractor'
> C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see
> declaration of 'wxWindow'
> C:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83)
> : see declaration of 'wxVTKRenderWindowInteractor'
> C:\VTK\Common\Testing\Cxx\vtkTestUtilities.h(19) : error C2011:
> 'vtkTestUtilities' : 'struct' type redefinition
> C:\VTK\Rendering\vtkTesting.h(30) : see declaration of
> 'vtkTestUtilities'
> Generating Code...
>
> Build log was saved at
> "file://c:\wxWidgets-2.6.2\wxVTK\Bin\wxImageViewer.dir\Debug\BuildLog.htm"
> wxImageViewer - 6 error(s), 39 warning(s)
>
>
>
> -----Original Message-----
> From: Jan Woetzel [mailto:jw...@mi...]
> Sent: Saturday, 19 November 2005 3:15 AM
> To: Mathieu Malaterre
> Cc: Oliver Frank; wxv...@li...; Jan Woetzel
> Subject: WX 2.6.2 Find script
>
>
> Mathieu,
> yes, I adapted our Findscript for WX 2.6.2, see
> http://www.mip.informatik.uni-kiel.de/~jw/cmake/
>
> Linux works flawless relying on "wx-config".
>
> On Windows we still prefer the monolithic build.
> You can create a monolithic WX 2.6.2 build this way:
> Go to wxWidgets2.62./build/msw and call
>
> nmake -f makefile.vc BUILD=debug SHARED=0 USE_OPENGL=1 MONOLITHIC=1
>
> See:
> http://www.mip.informatik.uni-kiel.de/~jw/wx/
>
>
> There is initial support for non-monolithic build in the find script,
> and it work here, too.
> But it is a quickhack because those many "small" WX libs are listed
> explicitly.
> The script is not yet search for each lib or verify its result with a
> try compile.
>
> So the easy solutions is:
> 1. compile WX monolithic with nmake
> 2. use my Find script.
>
> Works for me with Linux and Windows XP / VS2003 and static WX
> libraries in
> Debug+Release.
>
> Best,
> Jan.
>
>
>
> Mathieu Malaterre wrote:
>
>
>>Jan,
>>
>> By any chance did you update your FindwxWidgets ?
>> Is seems there is no more a central monolithic library like
>>wxmsw24.lib in 2.6.2
>>
>> Thanks for your comment.
>>
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wxvtk-users mailing list
Wxv...@li...
https://lists.sourceforge.net/lists/listinfo/wxvtk-users
|
|
From: Oliver F. <o....@ac...> - 2005-11-25 06:24:29
|
Thanks, that helped me... The standard configuration built the vtk libraries
as shared dll's...
Oli
-----Original Message-----
From: wxv...@li...
[mailto:wxv...@li...] On Behalf Of Nigel Nunn
Sent: Friday, 25 November 2005 12:03 PM
To: wxv...@li...
Cc: o....@ac...
Subject: RE: [wxVTK] WX 2.6.2 Find script
Hi Oliver,
"inconsistent dll linkage" usually implies that some libs have been built as
"dynamic link libraries" (thus run-time linking), while others have been
built for static (compile-time linking).
The other common problem is having some libs built for one threading model
while the executable is built for another.
Are you familiar with setting VC++ project "Properties"?
To check, right-click each project in the "Solution Explorer"
panel, then select [Properties]. In the tabbed dialog, choose
[C/C+]
[Code generation] -- Runtime Library
Make sure all projects have consistent settings (for both debug and release
builds).
good luck!
Nigel
-----Original Message-----
From: wxv...@li...
[mailto:wxv...@li...]On Behalf Of Oliver Frank
Sent: Thursday, 24 November 2005 4:12 PM
To: 'Jan Woetzel'; 'Mathieu Malaterre'
Cc: wxv...@li...
Subject: [wxVTK] RE: WX 2.6.2 Find script
Thanks guys!
I got monolithical libraries and cmake is setting up the files with no
worries...
I opened the generated wxVTKSample.sln with Visual Studio and tried to
comile it. Unfortunately I got the output attached and have no clue what's
going wrong...
Any help is very appreciated!
Cheers,
Oli
------ Build started: Project: wxImageViewer,
Configuration: Debug Win32 ------
Compiling...
wxVTKRenderWindowInteractor.cxx
c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) :
warning C4275: non dll-interface class 'wxWindow' used as base
for dll-interface class 'wxVTKRenderWindowInteractor'
[snip]
-----Original Message-----
From: Jan Woetzel [mailto:jw...@mi...]
Sent: Saturday, 19 November 2005 3:15 AM
To: Mathieu Malaterre
Cc: Oliver Frank; wxv...@li...; Jan Woetzel
Subject: WX 2.6.2 Find script
Mathieu,
yes, I adapted our Findscript for WX 2.6.2, see
http://www.mip.informatik.uni-kiel.de/~jw/cmake/
Linux works flawless relying on "wx-config".
On Windows we still prefer the monolithic build.
You can create a monolithic WX 2.6.2 build this way:
Go to wxWidgets2.62./build/msw and call
nmake -f makefile.vc BUILD=debug SHARED=0 USE_OPENGL=1 MONOLITHIC=1
See:
http://www.mip.informatik.uni-kiel.de/~jw/wx/
There is initial support for non-monolithic build in the find
script, and it work here, too. But it is a quickhack because
those many "small" WX libs are listed explicitly. The script
is not yet search for each lib or verify its result with a
try compile.
So the easy solutions is:
1. compile WX monolithic with nmake
2. use my Find script.
Works for me with Linux and Windows XP / VS2003 and static WX
libraries in Debug+Release.
Best,
Jan.
Mathieu Malaterre wrote:
> Jan,
>
> By any chance did you update your FindwxWidgets ?
> Is seems there is no more a central monolithic library
> like wxmsw24.lib in 2.6.2
>
> Thanks for your comment.
|
|
From: Nigel N. <nN...@au...> - 2005-11-25 01:06:46
|
Hi Oliver,
"inconsistent dll linkage" usually implies that some libs have=20
been built as "dynamic link libraries" (thus run-time linking),=20
while others have been built for static (compile-time linking).
The other common problem is having some libs built for one=20
threading model while the executable is built for another. =20
Are you familiar with setting VC++ project "Properties"?
To check, right-click each project in the "Solution Explorer"=20
panel, then select [Properties]. In the tabbed dialog, choose
[C/C+]=20
[Code generation] -- Runtime Library
Make sure all projects have consistent settings (for both debug=20
and release builds).
good luck!
Nigel
-----Original Message-----
From: wxv...@li...
[mailto:wxv...@li...]On Behalf Of Oliver
Frank
Sent: Thursday, 24 November 2005 4:12 PM
To: 'Jan Woetzel'; 'Mathieu Malaterre'
Cc: wxv...@li...
Subject: [wxVTK] RE: WX 2.6.2 Find script
Thanks guys!=20
I got monolithical libraries and cmake is setting up the files=20
with no worries...
I opened the generated wxVTKSample.sln with Visual Studio and=20
tried to comile it. Unfortunately I got the output attached and=20
have no clue what's going wrong...
Any help is very appreciated!
Cheers,
Oli
------ Build started: Project: wxImageViewer,=20
Configuration: Debug Win32 ------
Compiling...
wxVTKRenderWindowInteractor.cxx
c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) :=20
warning C4275: non dll-interface class 'wxWindow' used as base=20
for dll-interface class 'wxVTKRenderWindowInteractor'
[snip]
-----Original Message-----
From: Jan Woetzel [mailto:jw...@mi...]=20
Sent: Saturday, 19 November 2005 3:15 AM
To: Mathieu Malaterre
Cc: Oliver Frank; wxv...@li...; Jan Woetzel
Subject: WX 2.6.2 Find script
Mathieu,
yes, I adapted our Findscript for WX 2.6.2, see
http://www.mip.informatik.uni-kiel.de/~jw/cmake/
Linux works flawless relying on "wx-config".
On Windows we still prefer the monolithic build.
You can create a monolithic WX 2.6.2 build this way:
Go to wxWidgets2.62./build/msw and call
nmake -f makefile.vc BUILD=3Ddebug SHARED=3D0 USE_OPENGL=3D1 =
MONOLITHIC=3D1
See:
http://www.mip.informatik.uni-kiel.de/~jw/wx/
There is initial support for non-monolithic build in the find=20
script, and it work here, too. But it is a quickhack because=20
those many "small" WX libs are listed explicitly. The script=20
is not yet search for each lib or verify its result with a=20
try compile.
So the easy solutions is:
1. compile WX monolithic with nmake
2. use my Find script.
Works for me with Linux and Windows XP / VS2003 and static WX=20
libraries in Debug+Release.
Best,
Jan.
Mathieu Malaterre wrote:
> Jan,
>
> By any chance did you update your FindwxWidgets ?
> Is seems there is no more a central monolithic library=20
> like wxmsw24.lib in 2.6.2
>
> Thanks for your comment.
|
|
From: Mathieu M. <mat...@ki...> - 2005-11-24 18:24:12
|
Oliver, I believe this is in the README file (Q2), mixing configuration is tricky on Win32 (static and shared) Happy Thanksgiving, Mathieu Oliver Frank wrote: > Thanks guys! > > I got monolithical libraries and cmake is setting up the files with no > worries... > > I opened the generated wxVTKSample.sln with Visual Studio and tried to > comile it. Unfortunately I got the output attached and have no clue what's > going wrong... > > Any help is very appreciated! > > Cheers, > Oli > > ------ Build started: Project: wxImageViewer, Configuration: Debug Win32 > ------ > > Compiling... > wxVTKRenderWindowInteractor.cxx > c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : warning > C4275: non dll-interface class 'wxWindow' used as base for dll-interface > class 'wxVTKRenderWindowInteractor' > C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see declaration of > 'wxWindow' > c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : see > declaration of 'wxVTKRenderWindowInteractor' > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : warning > C4273: 'ms_classInfo' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : error > C2491: 'wxVTKRenderWindowInteractor::ms_classInfo' : definition of dllimport > static data member not allowed > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : warning > C4273: 'wxVTKRenderWindowInteractor::GetClassInfo' : inconsistent dll > linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : warning > C4273: 'wxVTKRenderWindowInteractor::wxCreateObject' : inconsistent dll > linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning > C4273: 'sm_eventTable' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error > C2491: 'wxVTKRenderWindowInteractor::sm_eventTable' : definition of > dllimport static data member not allowed > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning > C4273: 'wxVTKRenderWindowInteractor::GetEventTable' : inconsistent dll > linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning > C4273: 'sm_eventHashTable' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error > C2491: 'wxVTKRenderWindowInteractor::sm_eventHashTable' : definition of > dllimport static data member not allowed > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning > C4273: 'wxVTKRenderWindowInteractor::GetEventHashTable' : inconsistent dll > linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning > C4273: 'sm_eventTableEntries' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error > C2491: 'wxVTKRenderWindowInteractor::sm_eventTableEntries' : definition of > dllimport static data member not allowed > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(105) : warning > C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' : > inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(108) : warning > C4355: 'this' : used in base member initializer list > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(130) : warning > C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' : > inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(133) : warning > C4355: 'this' : used in base member initializer list > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(147) : warning > C4273: 'wxVTKRenderWindowInteractor::~wxVTKRenderWindowInteractor' : > inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(151) : warning > C4273: 'wxVTKRenderWindowInteractor::New' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(157) : warning > C4273: 'wxVTKRenderWindowInteractor::Initialize' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(167) : warning > C4273: 'wxVTKRenderWindowInteractor::Enable' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(178) : warning > C4273: 'wxVTKRenderWindowInteractor::Disable' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(189) : warning > C4273: 'wxVTKRenderWindowInteractor::Start' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(196) : warning > C4273: 'wxVTKRenderWindowInteractor::UpdateSize' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(211) : warning > C4273: 'wxVTKRenderWindowInteractor::CreateTimer' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(221) : warning > C4273: 'wxVTKRenderWindowInteractor::DestroyTimer' : inconsistent dll > linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(227) : warning > C4273: 'wxVTKRenderWindowInteractor::OnTimer' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(241) : warning > C4273: 'wxVTKRenderWindowInteractor::GetHandle' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(300) : warning > C4273: 'wxVTKRenderWindowInteractor::OnPaint' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(318) : warning > C4273: 'wxVTKRenderWindowInteractor::OnEraseBackground' : inconsistent dll > linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(324) : warning > C4273: 'wxVTKRenderWindowInteractor::OnSize' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(327) : error > C2039: 'OnSize' : is not a member of 'wxWindow' > C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see declaration of > 'wxWindow' > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(346) : warning > C4273: 'wxVTKRenderWindowInteractor::OnMotion' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(364) : warning > C4273: 'wxVTKRenderWindowInteractor::OnEnter' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(384) : warning > C4273: 'wxVTKRenderWindowInteractor::OnLeave' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(404) : warning > C4273: 'wxVTKRenderWindowInteractor::OnKeyDown' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(433) : warning > C4273: 'wxVTKRenderWindowInteractor::OnKeyUp' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(461) : warning > C4273: 'wxVTKRenderWindowInteractor::OnButtonDown' : inconsistent dll > linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(517) : warning > C4273: 'wxVTKRenderWindowInteractor::OnButtonUp' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(574) : warning > C4273: 'wxVTKRenderWindowInteractor::Render' : inconsistent dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(611) : warning > C4273: 'wxVTKRenderWindowInteractor::SetRenderWhenDisabled' : inconsistent > dll linkage > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(628) : warning > C4800: 'int' : forcing value to bool 'true' or 'false' (performance warning) > \wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(636) : warning > C4273: 'wxVTKRenderWindowInteractor::SetStereo' : inconsistent dll linkage > wxImageViewer.cxx > C:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : warning > C4275: non dll-interface class 'wxWindow' used as base for dll-interface > class 'wxVTKRenderWindowInteractor' > C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see declaration of > 'wxWindow' > C:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : see > declaration of 'wxVTKRenderWindowInteractor' > C:\VTK\Common\Testing\Cxx\vtkTestUtilities.h(19) : error C2011: > 'vtkTestUtilities' : 'struct' type redefinition > C:\VTK\Rendering\vtkTesting.h(30) : see declaration of > 'vtkTestUtilities' > Generating Code... > > Build log was saved at > "file://c:\wxWidgets-2.6.2\wxVTK\Bin\wxImageViewer.dir\Debug\BuildLog.htm" > wxImageViewer - 6 error(s), 39 warning(s) > > > > -----Original Message----- > From: Jan Woetzel [mailto:jw...@mi...] > Sent: Saturday, 19 November 2005 3:15 AM > To: Mathieu Malaterre > Cc: Oliver Frank; wxv...@li...; Jan Woetzel > Subject: WX 2.6.2 Find script > > > Mathieu, > yes, I adapted our Findscript for WX 2.6.2, see > http://www.mip.informatik.uni-kiel.de/~jw/cmake/ > > Linux works flawless relying on "wx-config". > > On Windows we still prefer the monolithic build. > You can create a monolithic WX 2.6.2 build this way: > Go to wxWidgets2.62./build/msw and call > > nmake -f makefile.vc BUILD=debug SHARED=0 USE_OPENGL=1 MONOLITHIC=1 > > See: > http://www.mip.informatik.uni-kiel.de/~jw/wx/ > > > There is initial support for non-monolithic build in the find script, and it > work here, too. > But it is a quickhack because those many "small" WX libs are listed > explicitly. > The script is not yet search for each lib or verify its result with a try > compile. > > So the easy solutions is: > 1. compile WX monolithic with nmake > 2. use my Find script. > > Works for me with Linux and Windows XP / VS2003 and static WX libraries in > Debug+Release. > > Best, > Jan. > > > > Mathieu Malaterre wrote: > > >>Jan, >> >> By any chance did you update your FindwxWidgets ? >> Is seems there is no more a central monolithic library like >>wxmsw24.lib in 2.6.2 >> >> Thanks for your comment. >> > > > |
|
From: Oliver F. <o....@ac...> - 2005-11-24 05:12:39
|
Thanks guys!
I got monolithical libraries and cmake is setting up the files with no
worries...
I opened the generated wxVTKSample.sln with Visual Studio and tried to
comile it. Unfortunately I got the output attached and have no clue what's
going wrong...
Any help is very appreciated!
Cheers,
Oli
------ Build started: Project: wxImageViewer, Configuration: Debug Win32
------
Compiling...
wxVTKRenderWindowInteractor.cxx
c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : warning
C4275: non dll-interface class 'wxWindow' used as base for dll-interface
class 'wxVTKRenderWindowInteractor'
C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see declaration of
'wxWindow'
c:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : see
declaration of 'wxVTKRenderWindowInteractor'
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : warning
C4273: 'ms_classInfo' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : error
C2491: 'wxVTKRenderWindowInteractor::ms_classInfo' : definition of dllimport
static data member not allowed
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : warning
C4273: 'wxVTKRenderWindowInteractor::GetClassInfo' : inconsistent dll
linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(66) : warning
C4273: 'wxVTKRenderWindowInteractor::wxCreateObject' : inconsistent dll
linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'sm_eventTable' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error
C2491: 'wxVTKRenderWindowInteractor::sm_eventTable' : definition of
dllimport static data member not allowed
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'wxVTKRenderWindowInteractor::GetEventTable' : inconsistent dll
linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'sm_eventHashTable' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error
C2491: 'wxVTKRenderWindowInteractor::sm_eventHashTable' : definition of
dllimport static data member not allowed
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'wxVTKRenderWindowInteractor::GetEventHashTable' : inconsistent dll
linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : warning
C4273: 'sm_eventTableEntries' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(73) : error
C2491: 'wxVTKRenderWindowInteractor::sm_eventTableEntries' : definition of
dllimport static data member not allowed
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(105) : warning
C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' :
inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(108) : warning
C4355: 'this' : used in base member initializer list
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(130) : warning
C4273: 'wxVTKRenderWindowInteractor::wxVTKRenderWindowInteractor' :
inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(133) : warning
C4355: 'this' : used in base member initializer list
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(147) : warning
C4273: 'wxVTKRenderWindowInteractor::~wxVTKRenderWindowInteractor' :
inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(151) : warning
C4273: 'wxVTKRenderWindowInteractor::New' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(157) : warning
C4273: 'wxVTKRenderWindowInteractor::Initialize' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(167) : warning
C4273: 'wxVTKRenderWindowInteractor::Enable' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(178) : warning
C4273: 'wxVTKRenderWindowInteractor::Disable' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(189) : warning
C4273: 'wxVTKRenderWindowInteractor::Start' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(196) : warning
C4273: 'wxVTKRenderWindowInteractor::UpdateSize' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(211) : warning
C4273: 'wxVTKRenderWindowInteractor::CreateTimer' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(221) : warning
C4273: 'wxVTKRenderWindowInteractor::DestroyTimer' : inconsistent dll
linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(227) : warning
C4273: 'wxVTKRenderWindowInteractor::OnTimer' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(241) : warning
C4273: 'wxVTKRenderWindowInteractor::GetHandle' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(300) : warning
C4273: 'wxVTKRenderWindowInteractor::OnPaint' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(318) : warning
C4273: 'wxVTKRenderWindowInteractor::OnEraseBackground' : inconsistent dll
linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(324) : warning
C4273: 'wxVTKRenderWindowInteractor::OnSize' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(327) : error
C2039: 'OnSize' : is not a member of 'wxWindow'
C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see declaration of
'wxWindow'
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(346) : warning
C4273: 'wxVTKRenderWindowInteractor::OnMotion' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(364) : warning
C4273: 'wxVTKRenderWindowInteractor::OnEnter' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(384) : warning
C4273: 'wxVTKRenderWindowInteractor::OnLeave' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(404) : warning
C4273: 'wxVTKRenderWindowInteractor::OnKeyDown' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(433) : warning
C4273: 'wxVTKRenderWindowInteractor::OnKeyUp' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(461) : warning
C4273: 'wxVTKRenderWindowInteractor::OnButtonDown' : inconsistent dll
linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(517) : warning
C4273: 'wxVTKRenderWindowInteractor::OnButtonUp' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(574) : warning
C4273: 'wxVTKRenderWindowInteractor::Render' : inconsistent dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(611) : warning
C4273: 'wxVTKRenderWindowInteractor::SetRenderWhenDisabled' : inconsistent
dll linkage
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(628) : warning
C4800: 'int' : forcing value to bool 'true' or 'false' (performance warning)
\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.cxx(636) : warning
C4273: 'wxVTKRenderWindowInteractor::SetStereo' : inconsistent dll linkage
wxImageViewer.cxx
C:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : warning
C4275: non dll-interface class 'wxWindow' used as base for dll-interface
class 'wxVTKRenderWindowInteractor'
C:\wxWidgets-2.6.2\include\wx\msw\window.h(48) : see declaration of
'wxWindow'
C:\wxWidgets-2.6.2\wxVTK\src\wxVTKRenderWindowInteractor.h(83) : see
declaration of 'wxVTKRenderWindowInteractor'
C:\VTK\Common\Testing\Cxx\vtkTestUtilities.h(19) : error C2011:
'vtkTestUtilities' : 'struct' type redefinition
C:\VTK\Rendering\vtkTesting.h(30) : see declaration of
'vtkTestUtilities'
Generating Code...
Build log was saved at
"file://c:\wxWidgets-2.6.2\wxVTK\Bin\wxImageViewer.dir\Debug\BuildLog.htm"
wxImageViewer - 6 error(s), 39 warning(s)
-----Original Message-----
From: Jan Woetzel [mailto:jw...@mi...]
Sent: Saturday, 19 November 2005 3:15 AM
To: Mathieu Malaterre
Cc: Oliver Frank; wxv...@li...; Jan Woetzel
Subject: WX 2.6.2 Find script
Mathieu,
yes, I adapted our Findscript for WX 2.6.2, see
http://www.mip.informatik.uni-kiel.de/~jw/cmake/
Linux works flawless relying on "wx-config".
On Windows we still prefer the monolithic build.
You can create a monolithic WX 2.6.2 build this way:
Go to wxWidgets2.62./build/msw and call
nmake -f makefile.vc BUILD=debug SHARED=0 USE_OPENGL=1 MONOLITHIC=1
See:
http://www.mip.informatik.uni-kiel.de/~jw/wx/
There is initial support for non-monolithic build in the find script, and it
work here, too.
But it is a quickhack because those many "small" WX libs are listed
explicitly.
The script is not yet search for each lib or verify its result with a try
compile.
So the easy solutions is:
1. compile WX monolithic with nmake
2. use my Find script.
Works for me with Linux and Windows XP / VS2003 and static WX libraries in
Debug+Release.
Best,
Jan.
Mathieu Malaterre wrote:
> Jan,
>
> By any chance did you update your FindwxWidgets ?
> Is seems there is no more a central monolithic library like
> wxmsw24.lib in 2.6.2
>
> Thanks for your comment.
>
--
Dipl.-Ing. Jan Woetzel
--------------------------------------------------
University of Kiel
Institute of Computer Science and Applied Mathematics
Hermann-Rodewald-Str. 3 [room 310]
24098 Kiel/Germany
--------------------------------------------------
Phone +49-431-880-4477
Fax +49-431-880-4054
Mob. +49-179-2937346
--------------------------------------------------
Url www.mip.informatik.uni-kiel.de/~jw
Email jw...@mi...
|
|
From: Jan W. <jw...@mi...> - 2005-11-18 16:15:20
|
Mathieu, yes, I adapted our Findscript for WX 2.6.2, see http://www.mip.informatik.uni-kiel.de/~jw/cmake/ Linux works flawless relying on "wx-config". On Windows we still prefer the monolithic build. You can create a monolithic WX 2.6.2 build this way: Go to wxWidgets2.62./build/msw and call nmake -f makefile.vc BUILD=debug SHARED=0 USE_OPENGL=1 MONOLITHIC=1 See: http://www.mip.informatik.uni-kiel.de/~jw/wx/ There is initial support for non-monolithic build in the find script, and it work here, too. But it is a quickhack because those many "small" WX libs are listed explicitly. The script is not yet search for each lib or verify its result with a try compile. So the easy solutions is: 1. compile WX monolithic with nmake 2. use my Find script. Works for me with Linux and Windows XP / VS2003 and static WX libraries in Debug+Release. Best, Jan. Mathieu Malaterre wrote: > Jan, > > By any chance did you update your FindwxWidgets ? > Is seems there is no more a central monolithic library like > wxmsw24.lib in 2.6.2 > > Thanks for your comment. > -- Dipl.-Ing. Jan Woetzel -------------------------------------------------- University of Kiel Institute of Computer Science and Applied Mathematics Hermann-Rodewald-Str. 3 [room 310] 24098 Kiel/Germany -------------------------------------------------- Phone +49-431-880-4477 Fax +49-431-880-4054 Mob. +49-179-2937346 -------------------------------------------------- Url www.mip.informatik.uni-kiel.de/~jw Email jw...@mi... |
|
From: Mathieu M. <mat...@ki...> - 2005-11-18 15:15:57
|
Jan, By any chance did you update your FindwxWidgets ? Is seems there is no more a central monolithic library like wxmsw24.lib in 2.6.2 Thanks for your comment. Mathieu Ps: Oliver, please CC the ML as this might be usefull for other users, thanks. Oliver Frank wrote: > Mathieu, > > Thanks a lot for your help! > > Ok, I found some files: > > wxbase26d.lib > wxbase26d_net.lib > wxbase26d_odbc.lib > wxbase26d_xml.lib > wxexpatd.lib > wxjpegd.lib > wxmsw26d_adv.lib > wxmsw26d_core.lib > wxmsw26d_dbgrid.lib > wxmsw26d_gl.lib > wxmsw26d_html.lib > wxmsw26d_media.lib > wxmsw26d_qa.lib > wxmsw26d_xrc.lib > wxpngd.lib > wxregexd.lib > wxtiffd.lib > wxzlibd.lib > > (only the static debug versions...) > > Which one is the static library to include? (WXWINDOWS_STATIC_DEBUG_LIBRARY > in cmake) > > Cheers, > Ollie > > -----Original Message----- > From: wxv...@li... > [mailto:wxv...@li...] On Behalf Of Mathieu > Malaterre > Sent: Friday, 18 November 2005 1:35 AM > To: Oliver Frank > Cc: wxv...@li... > Subject: [wxVTK] Re: [vtkusers] VTK and wxWindows > > Oliver, > > Ok I am getting a bit rusty with wxWidgets installation on Windows. > But you should have the library somewhere on your system. Then when cmake > complain you need to browse until you find them. The name of the lib should > look like this: > > wx26*.lib > > (I believe they now put the full version of the lib in the name). > > Mathieu > Ps: I don't have a windows box right now. hopefully another wxVTK user is > more windows friendly than I am :) > > Oliver Frank wrote: > >>Mathieu, >> >>Thank you. I've posted it there already. >>I've opened the msw build project that comes with the wxWidgets-2.6.2 >>windows distribution and compiled it with Visual .Net 7 2003? >> >>In wx/msw/setup.h is an option wxUSE_GLCANVAS which I changed to 1 but >>didn't make any difference... Do I have to install any OpenGl stuff first? >>Sorry I'm new to OpenGl, VTK, wxWindows... >> >>Regards, >>Oliver >> >>-----Original Message----- >>From: Mathieu Malaterre [mailto:mat...@ki...] >>Sent: Thursday, 17 November 2005 2:17 AM >>To: Oliver Frank >>Cc: vtk...@vt... >>Subject: Re: [vtkusers] VTK and wxWindows >> >>Oliver, >> >> Could we follow the discussion on wxVTK ML ? >> -> http://sourceforge.net/projects/wxvtk >> >> In particular how did you built wxWidgets ? >> >>Thanks >>Mathieu >> >>Oliver Frank wrote: >> >> >>>Dear all, >>> >>>I'm trying to use VTK with wxWindows. I found a package wxVTK which is >>>meant to support that. I'm struggling with cmake issues... >>> >>>In the root CMakeLists.txt is an entry like the following >>> >>>#--------------------------------------------------------------------- >>>-------- >>>SET(WXWINDOWS_USE_GL 1) >>>#When http://www.cmake.org/pipermail/cmake/2003-September/004263.html >>>#will be solved VTK + wxWindows would hopefully fully collaborate ! >>>FIND_PACKAGE(wxWindows) >>>#INCLUDE(${wxVTKSample_SOURCE_DIR}/Modules/FindwxWindows.cmake) >>>IF ( CMAKE_WX_CAN_COMPILE ) >>> >>>When using the line FIND_PACKAGE(wxWindows) i get the following error >>>(using Visual Studio .NET 7 2003): >>>CMake Error: No static wxWindows lib found, but >> >>WXWINDOWS_USE_SHARED_LIBS=. >> >> >>>When using the FindwxWindows.cmake with >>>INCLUDE(${wxVTKSample_SOURCE_DIR}/Modules/FindwxWindows.cmake) >>>I get a similar error... It can't set the WXWINDOWS_STATIC_LIBRARY >>> >>>Apparently cmake is not able to detect the wx libraries either way... >>> >>>So I started to look for them manually on my system (Windows XP) (hint >> >>>from the FindwxWindows.cmake file about the names i have to look for: >> >>>wx, wxmsw, wxd, wxmswd, wx23_2, wx22_9, wxmsw240, wx23_2d, wx22_9d, >>>wxmsw240d) but can't find them... I guess I must have done anything >>>wrong when compiled wxWindows? >>> >>>Any help is very appreciated, >>>Thank, >>>Oli >>> >>> >>> >>> >>> >>>---------------------------------------------------------------------- >>>-- >>> >>>_______________________________________________ >>>This is the private VTK discussion list. >>>Please keep messages on-topic. Check the FAQ at: >>>http://www.vtk.org/Wiki/VTK_FAQ Follow this link to subscribe/unsubscribe: >>>http://www.vtk.org/mailman/listinfo/vtkusers >> >> >> >> >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam for All > Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > > > |
|
From: Mathieu M. <mat...@ki...> - 2005-11-17 14:38:59
|
Oliver, Ok I am getting a bit rusty with wxWidgets installation on Windows. But you should have the library somewhere on your system. Then when cmake complain you need to browse until you find them. The name of the lib should look like this: wx26*.lib (I believe they now put the full version of the lib in the name). Mathieu Ps: I don't have a windows box right now. hopefully another wxVTK user is more windows friendly than I am :) Oliver Frank wrote: > Mathieu, > > Thank you. I've posted it there already. > I've opened the msw build project that comes with the wxWidgets-2.6.2 > windows distribution and compiled it with Visual .Net 7 2003? > > In wx/msw/setup.h is an option wxUSE_GLCANVAS which I changed to 1 but > didn't make any difference... Do I have to install any OpenGl stuff first? > Sorry I'm new to OpenGl, VTK, wxWindows... > > Regards, > Oliver > > -----Original Message----- > From: Mathieu Malaterre [mailto:mat...@ki...] > Sent: Thursday, 17 November 2005 2:17 AM > To: Oliver Frank > Cc: vtk...@vt... > Subject: Re: [vtkusers] VTK and wxWindows > > Oliver, > > Could we follow the discussion on wxVTK ML ? > -> http://sourceforge.net/projects/wxvtk > > In particular how did you built wxWidgets ? > > Thanks > Mathieu > > Oliver Frank wrote: > >>Dear all, >> >>I'm trying to use VTK with wxWindows. I found a package wxVTK which is >>meant to support that. I'm struggling with cmake issues... >> >>In the root CMakeLists.txt is an entry like the following >> >>#--------------------------------------------------------------------- >>-------- >>SET(WXWINDOWS_USE_GL 1) >>#When http://www.cmake.org/pipermail/cmake/2003-September/004263.html >>#will be solved VTK + wxWindows would hopefully fully collaborate ! >>FIND_PACKAGE(wxWindows) >>#INCLUDE(${wxVTKSample_SOURCE_DIR}/Modules/FindwxWindows.cmake) >>IF ( CMAKE_WX_CAN_COMPILE ) >> >>When using the line FIND_PACKAGE(wxWindows) i get the following error >>(using Visual Studio .NET 7 2003): >>CMake Error: No static wxWindows lib found, but > > WXWINDOWS_USE_SHARED_LIBS=. > >> >>When using the FindwxWindows.cmake with >>INCLUDE(${wxVTKSample_SOURCE_DIR}/Modules/FindwxWindows.cmake) >>I get a similar error... It can't set the WXWINDOWS_STATIC_LIBRARY >> >>Apparently cmake is not able to detect the wx libraries either way... >> >>So I started to look for them manually on my system (Windows XP) (hint >>from the FindwxWindows.cmake file about the names i have to look for: >>wx, wxmsw, wxd, wxmswd, wx23_2, wx22_9, wxmsw240, wx23_2d, wx22_9d, >>wxmsw240d) but can't find them... I guess I must have done anything >>wrong when compiled wxWindows? >> >>Any help is very appreciated, >>Thank, >>Oli >> >> >> >> >> >>---------------------------------------------------------------------- >>-- >> >>_______________________________________________ >>This is the private VTK discussion list. >>Please keep messages on-topic. Check the FAQ at: >>http://www.vtk.org/Wiki/VTK_FAQ Follow this link to subscribe/unsubscribe: >>http://www.vtk.org/mailman/listinfo/vtkusers > > > > > |
|
From: Oliver F. <o....@ac...> - 2005-11-16 03:22:56
|
Dear all, I'm trying to use wxVTK-0.8. I'm struggling with cmake issues... Versions: CMake 2.2 wxWindows 2.6.2 VTK 4.4 In the root CMakeLists.txt is an entry like the following #--------------------------------------------------------------------------- -- SET(WXWINDOWS_USE_GL 1) #When http://www.cmake.org/pipermail/cmake/2003-September/004263.html <BLOCKED::BLOCKED::http://www.cmake.org/pipermail/cmake/2003-September/00426 3.html> #will be solved VTK + wxWindows would hopefully fully collaborate ! FIND_PACKAGE(wxWindows) #INCLUDE(${wxVTKSample_SOURCE_DIR}/Modules/FindwxWindows.cmake) IF ( CMAKE_WX_CAN_COMPILE ) When using the line FIND_PACKAGE(wxWindows) i get the following error (using Visual Studio .NET 7 2003): CMake Error: No static wxWindows lib found, but WXWINDOWS_USE_SHARED_LIBS=. When using the FindwxWindows.cmake with INCLUDE(${wxVTKSample_SOURCE_DIR}/Modules/FindwxWindows.cmake) I get a similar error... It can't set the WXWINDOWS_STATIC_LIBRARY Apparently cmake is not able to detect the wx libraries either way... So I started to look for them manually on my system (Windows XP) (hint from the FindwxWindows.cmake file about the names i have to look for: wx, wxmsw, wxd, wxmswd, wx23_2, wx22_9, wxmsw240, wx23_2d, wx22_9d, wxmsw240d) but can't find them... I guess I must have done something wrong when compiled wxWindows? Any help is very appreciated, Thank, Oli |
4 messages has been excluded from this view by a project administrator.
