[vtk-developers] cmake: shared/static libs
Berk Geveci
berk.geveci at kitware.com
Thu Nov 29 09:35:13 EST 2001
You are not doing anything wrong and neither is CMake. Python libraries are
_always_ build shared since they are mostly useless static. If you really want
them to be static, let me know and I'll explain how to change CMakeLists.txt
files to do it.
-Berk
Randy Heiland wrote:
> I'm still new to this cmake world, but here's a question...
>
> I built with:
> BUILD_SHARED_LIBS:BOOL=ON
>
> and all went well -- I got shared libs.
>
> Then, for various reasons, I decided I wanted to build static libs, so I edited
> CMakeCache.txt and set:
> BUILD_SHARED_LIBS:BOOL=OFF
>
> and reran 'cmake'. However, it doesn't seem to "undo" all the shared env vars,
> e.g.,
> vtkCommonPython_LIBRARY_TYPE:INTERNAL=SHARED
> etc.
>
> and so, all the generated Makefiles still build shared libs.
>
> Am I doing something wrong?
>
> --Randy
> _______________________________________________
> vtk-developers mailing list
> vtk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/vtk-developers
>
>
More information about the vtk-developers
mailing list