|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
program name and function name builtins
Post 302399234 by xiamin on Friday 26th of February 2010 07:53:27 PM
02-26-2010
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I want a command in unix shell script which will exit my whole program, not only from the function it's using. For e.g:
$1 == "m_who" && $4 == "Extrnl Vendor" {
print "You don have access"
exit (0);
}
If this error is showing on the screen, then nothing should not... (9 Replies)
Discussion started by: ronix007
9 Replies
2. Programming
Apart from writing debug and statements in constructors is there any way by which we can trace the function call stack at any depth?
The issue that we always face is that when program crashes (Web Server running on Linux) we have no idea where it crashes and we have to do the hard way of... (1 Reply)
Discussion started by: uunniixx
1 Replies
3. Shell Programming and Scripting
Hello All,
Is there any way to find a function name in a program file using perl.
for example, there is a file called Test.C in that
.
.
void function1(..)
{
<some code>
}
int function2(..)
{
.
.
sam() /*RA abc100*/
...
..
..
xyz()/*RA abc201*/
.. (8 Replies)
Discussion started by: Parthiban
8 Replies
4. Programming
I have a program which has 7-8 threads, and lots of shared variables; these variables (and also they may not the primitive type, they may be enum or struct ), then they may read/write by different threads at the same time.
Now, my design is like this,
typedef unsigned short int UINT16;... (14 Replies)
Discussion started by: sehang
14 Replies
5. UNIX for Advanced & Expert Users
I am looking to create some ksh93 extensions using the custom builtin feature.
I can successfully create a builtin function, load it using the builtin -f command and get an output. However, I want to get/set values of KSH variables from within my built-in.
For example, lets say I am creating... (2 Replies)
Discussion started by: a_programmer
2 Replies
6. UNIX for Dummies Questions & Answers
Why do shell builtins like echo and pwd have binaries in /bin? When I do which pwd, I get the one in /bin. that means that I am not using the builtin version? What determines which one gets used? Is the which command a definitive way to determine what is being run when I enter pwd? (16 Replies)
Discussion started by: glev2005
16 Replies
7. UNIX for Dummies Questions & Answers
We have a program source C and is required to indicate how many times each function is called from the C program. also print the line number where there is a call.
I've tried something like this:
#!/bin/sh
for i in $*;do
if !
then
echo $i is not a C file.
else echo $i... (0 Replies)
Discussion started by: oana06
0 Replies
8. UNIX for Dummies Questions & Answers
Hi !
It is a general question.
When an awk script looks like:
#! bin/awk
function example(i){
<body>
}
{
example(1) #the function uses input_1 and return output_a
}
{
example(2) #the function uses previous output_a as an input and returns... (15 Replies)
Discussion started by: beca123456
15 Replies
9. UNIX for Dummies Questions & Answers
Not sure if this is the right forum but I have collated a listing of shell and bash builtins.
Builtins is a loose word and may include the '/bin' drawer/folder/directory but NOT any
others in the path list.
In the case of my Macbook Pro, OSX 10.7.5 the enabled internals is also listed...
... (1 Reply)
Discussion started by: wisecracker
1 Replies
10. UNIX for Beginners Questions & Answers
I work at a company that uses a program written in AWK to track various data and prepare reports. Worked with this program for three years plus (the author is no longer with us) and the YTD Production report will not return a report with a date after 123119. This is a problem. Below is the (I... (3 Replies)
Discussion started by: paulgdavitt
3 Replies
LEARN ABOUT CENTOS
gimptool
GIMPTOOL-2.0(1) General Commands Manual GIMPTOOL-2.0(1) NAME
gimptool-2.0 - script to perform various GIMPy functions SYNOPSIS
gimptool-2.0 [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--msvc-syntax] [--bindir] [--sbindir] [--libexecdir] [--datadir] [--sysconfdir] [--sharedstatedir] [--localstatedir] [--libdir] [--infodir] [--mandir] [--includedir] [--gimpplugindir] [--gimpdatadir] [--libs] [--libs-noui] [--cflags] [--cflags-noi] [--build plug-in.c] [--build-strip plug-in.c] [--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-in.c] [--install-bin plug-in] [--install-admin-strip plug-in.c] [--install-bin-strip plug-in] [--install-admin-bin plug-in] [--install-script script.scm] [--install-admin-script script.scm] [--uninstall-bin plug-in] [--uninstall-admin-bin plug-in] [--uninstall-script script.scm] [--unin- stall-admin-script script.scm] DESCRIPTION
gimptool-2.0 is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file. gimptool-2.0 can also be used by programs that need to know what libraries and include-paths GIMP was compiled with. gimptool-2.0 uses pkg- config for this task. For use in Makefiles, it is recommended that you use pkg-config directly instead of calling gimptool-2.0. OPTIONS
gimptool-2.0 accepts the following options: --version Print the currently installed version of GIMP on the standard output. --help Print out the help blurb, showing commonly used commandline options. --quiet Run quietly without echoing any of the build commands. --silent Run silently without echoing any of the build commands. Same as --quiet. -n Test mode. Print the commands but don't actually execute them. Useful for making dry runs for testing. --just-print Test mode. Print the commands but don't actually execute them. Same as -n. --dry-run Test mode. Print the commands but don't actually execute them. Same as -n. --recon Test mode. Print the commands but don't actually execute them. Same as -n. --msvc-syntax Useful on Windows. Outputs the compiler and linker flags in the syntax used by Microsoft's toolchain. Passed to the pkg-config com- mand that does most of gimptool-2.0's work. --bindir Outputs the bindir used to install the GIMP. --sbindir Outputs the sbindir used to install the GIMP. --libexecdir Outputs the libexecdir used to install the GIMP. --datadir Outputs the datadir used to install the GIMP. --sysconfdir Outputs the sysconfdir used to install the GIMP. --sharedstatedir Outputs the sharedstatedir used to install the GIMP. --localstatedir Outputs the localstatedir used to install the GIMP. --libdir Outputs the libdir used to install the GIMP. --infodir Outputs the infodir used to install the GIMP. --mandir Outputs the mandir used to install the GIMP. --includedir Outputs the includedir used to install the GIMP. --gimpdatadir Outputs the actual directory where the GIMP data files were installed. --gimpplugindir Outputs the actual directory where the GIMP plug-ins were installed. --build plug-in.c Compile and link plug-in.c into a GIMP plug-in. --build-strip plug-in.c Compile,link, and strip plug-in.c into a GIMP plug-in. --install plug-in.c Compile, link, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-strip plug-in.c Compile, link,strip, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin plug-in.c Compile, link, and install plug-in.c into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin plug-in Install plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin-bin plug-in Install plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin-strip plug-in Install stripped plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin-bin-strip plug-in Install stripped plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-script script.scm Install script.scm into the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts) --install-admin-script script.scm Install script.scm into the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --uninstall-bin plug-in Uninstall plug-in from the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --uninstall-admin-bin plug-in Uninstall plug-in from the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --uninstall-script script.scm Uninstall script.scm from the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts) --uninstall-admin-script script.scm Uninstall script.scm from the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --libs Print the linker flags that are necessary to link a GIMP plug-in. --libs-noui Print the linker flags that are necessary to link a GIMP plug-in, for plug-ins that do not require the GTK+ libraries. --cflags Print the compiler flags that are necessary to compile a GIMP plug-in. --clags-noui Print the compiler flags that are necessary to compile a GIMP plug-in for plug-ins that do not require the GTK+ libraries. --prefix=PREFIX If specified, use PREFIX instead of the installation prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options. --exec-prefix=PREFIX If specified, use PREFIX instead of the installation exec prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options. ENVIRONMENT
CC to get the name of the desired C compiler. CFLAGS to get the preferred flags to pass to the C compiler for plug-in building. LDFLAGS to get the preferred flags for passing to the linker. LIBS for passing extra libs that may be needed in the build process. For example, LIBS=-lintl . PKG_CONFIG to get the location of the pkg-config program that is used to determine details about your glib, pango, gtk+ and gimp installation. SEE ALSO
gimp(1), gimprc(5), pkg-config(1) AUTHORS
gimptool was written by Manish Singh (yosh@gimp.org) and is based on gtk-config by Owen Taylor (owen@gtk.org). This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins (adrian@gimp.org) and Marc Lehmann (pcg@goof.com>). GIMP Manual Pages Version 2.8.10 GIMPTOOL-2.0(1)