Making file executable Post: 302464689

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

pls hlp: making .sh files executable

I've got a file named jdictd.sh containing the following: --- begin file contents --- #! /bin/csh echo I\'m running! java -cp jdictd.jar org.dict.server.JDictd data/dict.ini # Use the following line instead if JRE 1.1 is used # jre -cp jdictd.jar org.dict.server.JDictd data/dict.ini ---end...

2. AIX

Making Executable File

Hi All: I am a newbie. I have shell script and bunch of java jar files and I want to give one single executable file (may be .bin). Ex: I have test.sh, jar1.jar, jar2.jar. I have to make process.xxx When we run "process.xxx" it will run the "test.sh" script which inturn uses jar1.jar and...

3. UNIX for Dummies Questions & Answers

Making UNIX script executable

Hello, I am very new to UNIX and I have been learning about writing scripts and making them executable. I created a script called myscript. It has three lines: #! /bin/sh # This is my first shell script echo friendsjustfriends Now I try to run it using the sh command and it works Next I...

4. UNIX for Dummies Questions & Answers

need help making a script executable

making a script in vi to create a shell script called wherearethey by entering the following script: echo -n "Who are you looking for: "read userif then list=`w | grep $user | cut -c19-30` if then echo "The user $user is logged in from $list" else echo "The user $user is not logged in...

5. Shell Programming and Scripting

problem in making Awk executable script

Guys I placed #!path/awk -f placed awk script and used $1 to call 1st inputfile inside the script. But some where I did mistake. Could you please help me run this script as executable I forgot to mention I also used BEGIN before placing awk script. But nothing worked out. Script ...

6. Shell Programming and Scripting

Making a perl script executable

Hello, I have a perl program called snp_hwe.pl I have another program called hwe_test.run which contains the following: for file in *.inp do cp $file genotype_counts_c.txt ./snp_hwe.exe > $file'.res' done I want to change my perl program to an executable program while changing...

7. UNIX for Advanced & Expert Users

What choice when "making" an executable on FreeBSD?

I should make an executable on our server, and are having some problem (I changed this question cause I found out that anser). I'm getting this error when trying to do make: In file included from... /usr/include/sys/file.h:161: error: expected specifier-qualifier-list before 'u_int' *** Error...

8. Shell Programming and Scripting

Making any script executable

Hi all, I'm new to Unix so just wanted some help. I've been self learning and came accross a question online that I was trying. It is to make any shell script executable, the name of the file is to be made executable. I would use nano and type in something like #! /bin/bash Chmod +x...

9. Shell Programming and Scripting

Making bash script allways executable when transfer ?

Does it possible to make some bash script automatic to be a executable when transfered to another pc...?

LEARN ABOUT OSX

runtargetunittests

RunTargetUnitTests(1)					    BSD General Commands Manual 				     RunTargetUnitTests(1)

NAME

     RunTargetUnitTests -- run unit tests for the current target

SYNOPSIS

     RunTargetUnitTests

DESCRIPTION

     RunTargetUnitTests examines its environment and runs the unit tests it presumes are present using otest(1).

     RunTargetUnitTests is intended to be called from a shell script build phase.  It expects certain environment variables to be configured from
     Xcode build settings (see below).

     RunTargetUnitTests will run tests for all built architectures appropriate for the machine running the tests.

ENVIRONMENT

     ARCHS		 The architectures the tests were built for; when tests are run, they will be run once per architecture.  If unspecified,
			 tests are run for the architecture returned by arch(1).

     DEVELOPER_DIR	 The Xcode folder, e.g. "/Developer". If unspecified the value for SYSTEM_DEVELOPER_DIR will be used, or "/Developer" if
			 that also is unspecified.

     BUILT_PRODUCTS_DIR  The directory containing built products; when tests are run, this is specified in DYLD_FRAMEWORK_PATH.  If unspecified
			 tests are run from the current working directory with no DYLD_FRAMEWORK_PATH.

     FULL_PRODUCT_NAME	 The full name of the built product, including its wrapper extension if any.

     GCC_ENABLE_OBJC_GC  Whether or not the test bundle was compiled with Objective-C garbage collection enabled.  Possible values are
			 unsupported, supported, and required.	If not set, defaults to unsupported, which will run otest(1) with Objective-C
			 garbage collection disabled.

     NATIVE_ARCH_ACTUAL  The architecture of the machine running the tests, used to determine for which architectures tests can be run.  If
			 unspecified, defaults to the architecture returned by arch(1).

     OTEST		 The path to the otest command line tool; defaults to /Developer/Tools/otest.

     TEST_AFTER_BUILD	 Set to YES to run tests, any other value will prevent test execution.

FILES

     /Developer/Tools/RunTargetUnitTests  The script used to run tests from a shell script build phase.

     /Developer/Tools/otest		  The OCUnit test rig.

SEE ALSO

     arch(1), otest(1)

Mac OS X							   June 2, 2019 							  Mac OS X