Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Edward C. Jones <edcjones@er...> - 2004-01-09 00:39:17
I use gcc or g++ for compiling thing. There are usually "-I", "-l", and
"-L" options. What should I use for these options if I am using VXL?
What functions are in the many ".so" files that were output? Where is
this stuff documented?
I followed the instructions for compiling VXL. The source is in
/usr/local/src. The binaries etc. are in /usr/local/src/bin. Can I
rename the bin directory and move it to somewhere sensible like
From: Ian Scott <ian.scott@st...> - 2004-01-09 15:27:30
> -----Original Message-----
> From: vxl-users-admin@...
> [mailto:vxl-users-admin@...]On Behalf Of Edward C.
> Sent: Friday, January 09, 2004 12:35 AM
> To: vxl-users@...
> Subject: [Vxl-users] Using shared libraries
> I use gcc or g++ for compiling thing. There are usually "-I",
> "-l", and
> "-L" options. What should I use for these options if I am using VXL?
> What functions are in the many ".so" files that were output?
Fot the include directories, you will need to use "-I$VXLSRC/vcl" and
"-I$VXLSRC/core". If you are using one of the libraries in contrib, e.g. the
spatial objects libary vsol in contrib/gel, then you need to add the
relevant contrib directory, e.g. "-I%VXLSRC/contrib/gel"
For the library directories, if you are using the default build settings,
For the libraries themselves, well that depends on what code you want to
use. However it is easy to map function and class names to and from the
relevent library. vnl_vector is in libvnl.so, vgl_point is in libvgl.so.
Depending on what library you are using you may also have to link libraries
it depends on - you will normally always have to link against vcl, i.e.
> Where is
> this stuff documented?
VXL itself is documented in
We provide specific examples of how to use VXL from within another CMake
This is the approach most people use.
I guess it might be useful to explain how to link against VXL with other
build systems. I'll add it in.
> I followed the instructions for compiling VXL. The source is in
> /usr/local/src. The binaries etc. are in /usr/local/src/bin. Can I
> rename the bin directory and move it to somewhere sensible like
The only executables in $VXLBIN are tests and examples, so it wouldn't be
all that useful to put them in /usr/local/bin.