FW: [Vxl-users] PKG_CONFIG

[Ian S. <ian...@st...>]

> -----Original Message-----
> From: Ian Scott [mailto:ian...@st...]
> Sent: Tuesday, February 10, 2004 10:54 AM
> To: 'du...@we...'
> Subject: RE: [Vxl-users] PKG_CONFIG
> 
> 
> 
> 
> > -----Original Message-----
> > From:  du...@we...
> > Subject: [Vxl-users] PKG_CONFIG
> > I have just installed vxl-1.0.0. In the cmake cache I found 
> > following values:
> 
> > PKG_CONFIG
> I suspect that this value is used by newer versions of CMake. 
> I don't think it affects VXL.
> 
> > CMAKE_INSTALL _PREFIX 
> This should be where your CMake program is installed. It 
> should be set correctly by CMake.
> 
> > EXECUTABLE_OUTPUT_PATH
> If you want all your executables in one place, set this. I'm 
> not sure if the tests will work correctly though if you do 
> set it. The default (unset) value puts all the executables 
> (tests and examples) in the part of the tree where they are built.
> 
> > LIBRARY_OUTPUT_PATH
> Same as aboe but for libraries. VXL does set this by default 
> however, putting all the values in $VXLBIN/lib, for ease of use.
> 
> > to what should I set them?
> CMake and VXL put sensible default values for every value in 
> the CMake Cache. Unless you have a reason to change them, 
> leave them all as they were.
> 
> 
> > When makes it sense to build shared libraries?
> This is a wider question about computing. It depends on 
> whether your platform supports sensible shared libraries 
> (e.g. Windows doesn't by default), and whether you want to 
> move around a single binary executable (use static libs) or 
> have faster compilation and multiple executables running on 
> the same machines (use dynamic libs)
> 
> > Thank you for any help.
> 
> We would be grateful if you could use text email on 
> vxl-users. Like many public lists, some of our members use 
> text only email readers.
> 
> Ian.
>