[vtk-developers] Re: Python & VTK
Utkarsh Ayachit
utkarsh.ayachit at kitware.com
Tue Aug 2 11:12:15 EDT 2005
Andrew,
1) Brad/Prabhu are discussing the way Python wrappers are installed in
another thread on the developers list. As Brad said, the vtk*Python.dll
end up in lib rather than bin because:
"... looks like there are actually no CMake install rules for VTK's
Python wrappers. Instead the python setup.py convention is used. I
understand the need to follow the python convention, but this is the
only part of VTK that is not installed by the CMake INSTALL target..."
* Also, as Prabhu suggested, I have fixed the scrtips for the paths to
be prepended so that there will be no conflicts with the installed dlls
while building the tests. So, you will no longer have to change the PATH
to point to the build dir. (could you verify that this is working).
2) I will try to find out why the VTKExamples build is failing. May be
someone on the list knows the reason.
Utkarsh
Andrew Maclean wrote:
>Nearly there! All your changes today seem to work.
>
>
>However there are two little things:
>
>1) Was there any comment back on why vtk*Python.dll ended up in the
>C:\Program Files\VTK\lib\vtk?
>My theory: If you use python instead of vtkpython you need the dlls'so I
>guess they were dumped for convenience in the lib directory. However since
>all other dlls end up in the bin directory, perhaps they should go there.
>
>2) There is still a little problem:
>------ Build started: Project: VTKExamplesTarget, Configuration: Release
>Win32 ------
>
>Building Custom Rule C:/vtk/build/VTK-build/VTKExamples
>Internal cmake changing into directory: C:/vtk/build/VTK-build/Examples/All
>Microsoft (R) Development Environment Version 7.10.3077.
>Copyright (C) Microsoft Corp 1984-2001. All rights reserved.
>Invalid solution configuration
>Usage:
>devenv [solutionfile | projectfile | anyfile.ext] [switches]
>You can invoke devenv with a first argument to specify a solution file or
>project file. You can also invoke devenv with a first argument that is any
>other kind of file that you just want to open in an editor. When you supply
>a
>project file, the IDE opens it in the context of a solution by looking for a
>.sln file with the same base name as the project file in the same
>directory as the project file. If no such .sln file exists, then the IDE
>looks for a single .sln file that references the project. If no such single
>.sln file exists, then the IDE creates an unsaved solution with a default
>.sln
>file name that has the same base name as the project file.
>Command line builds:
>devenv solutionfile.sln /build solutionconfig [ /project projectnameorfile
>[ /projectconfig name ] ]
>Available command line switches:
>/build build the specified solution configuration
>/project specifies the project to build instead of solution must specify
>/build to use /project
>/projectconfig specifies project configuration to build must specify
>/project to use /projectconfig
>/out write build output to specified file
>/rebuild like /build but forces a clean first
>/clean clean up build outputs
>/deploy build the specified solution configuration and then deploy it
>/run run the specified solution configuration
>/runexit run the specified solution configuration and then terminate
>/command executes the specified internal command line after startup
>/mditabs use tabbed documents interface
>/mdi use MDI interface
>/fn use specified font name
>/fs use specified font size
>/LCID use specified language ID
>/noVSIP disables VSIP developers license key for VSIP testing
>/safemode only default environment and services load for stability
>/resetskippkgs allow VsPackages once flagged for loading failures to load
>again
>/migratesettings migrate some user settings from another version
>Product-specific switches:
>/debugexe Open the specified executable to be debugged. The remainder of
>the command line is passed to this executable as its arguments.
>/useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables instead
>of IDE paths for VC++ builds.
>To attach the debugger from the command line, use: vs7jit.exe -p <pid>
>
>Regards
> Andrew
>
>
>___________________________________________
>Andrew J. P. Maclean
>Centre for Autonomous Systems
>The Rose Street Building J04
>The University of Sydney 2006 NSW
>AUSTRALIA
>Ph: +61 2 9351 3283
>Fax: +61 2 9351 7474
>URL: http://www.cas.edu.au/
>___________________________________________
>
>
>
>
>
More information about the vtk-developers
mailing list