Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sundials-config(1) [debian man page]

sundials-config(1)						     SUNDIALS							sundials-config(1)

NAME
sundials-config - returns required flags for linking to SUNDIALS libraries SYNOPSIS
sundials-config -m {cvode|cvodes|ida|kinsol} -t {s|p} -l {c|f} [-s {libs|cppflags}] [-hv] DESCRIPTION
sundials-config provides a way to obtain various configuration options for compiling programs that use SUNDIALS OPTIONS
-m {cvode|cvodes|ida|kinsol} Select the SUNDIALS module -t {s|p} Use serial of parallel vectors -l {c|f} Use C or Fortran -s {libs|cppflags} Show linking flags or C preprocessor flags (show both of no option is given) -h Get usage and options information -v View the script NOTES
-lf is not valid for -m cvodes -s cppflags returns an empty string for -l f AUTHOR
Radu Serban <radu@llnl.gov> This manual page was written by Andrey Romanenko for the Debian system (but may be used by others). Permission is granted to copy, dis- tribute and/or modify this document under the terms of the &gnu; General Public License, Version 2 any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. SEE ALSO
SUNDIALS Documentation 2006-07-25 sundials-config(1)

Check Out this Related Man Page

itpp-config(1)						      General Commands Manual						    itpp-config(1)

NAME
itpp-config - script to get information about intalled IT++ library prefix, compiler flags and its version SYNOPSIS
itpp-config [--prefix] [--exec-prefix] [--debug] [--static] [--cflags] [--libs] [--help] [--version] DESCRIPTION
itpp-config is a tool that can be used to determine the compiler and linker flags required for compiling and linking programs that use IT++. It can be also used for checking the intalled libitpp library version. OPTIONS
itpp-config accepts the following options: --prefix output libitpp installation prefix --exec-prefix output libitpp installation exec prefix --debug use debugging pre-processor, compiler and linker flags (needs to be used in front of --cflags and --libs) --static use static linker flags (needs to be used in front of --libs) --cflags output pre-processor and compiler flags --libs output linker flags --help display brief help and exit --version output version number AUTHOR
This manual page was written by Adam Piatyszek <ediap@users.sourceforge.net> as a text file, then converted to man format by txt2tags. COPYRIGHT
Copyright (C) 1995-2010 (see AUTHORS file for a list of contributors) This file is part of IT++ - a C++ library of mathematical, signal processing, speech processing, and communications classes and functions. IT++ is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. IT++ is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with IT++. If not, see <http://www.gnu.org/licenses/>. IT++ 4.2 September 2010 itpp-config(1)
Man Page

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Capture linking failures

Hi all, I have a script file that has numerous linking commands (ln -s) and currently there is no checking to see if the linking is successful or not and I need to implement something that checks if any of the linking failed and report a failure. The method I can think of is a small function... (3 Replies)
Discussion started by: zmfcat1
3 Replies

2. Cybersecurity

ida-python script

I am writing a python script to add comment to the result of ida pro. My question is how to add my comment to the area of the assemble codes text? I remember there is a simple function to realize this, but don't know its name now... (0 Replies)
Discussion started by: Henryyy
0 Replies