06-21-2006
modifying C file and linking back to project files
hi,
This is the first time I work in a big C project. All source code files are located in say directory /source/pp and all header files are in /include/pp. I've created a link to both of these directories from my home dir, say /home/ss. So in the /home/ss dir I have the /source/pp and /include/pp directories which are really links. Now, I want to modify one of the C files in /source/pp. I can't do it directly from the /source/pp directory...that's why i created the links to these folders. I created another directory in /home/ss from which I could work in. My question is, how can I get a file from the /source/pp directory, modify it and link it to all the other c files and header files?
9 More Discussions You Might Find Interesting
1. Programming
Hi mates,
I am trying to copile and link to C programs with command:
cc file1,file2
but i raises the error "file not found" ... am i doing the right way?
any suggestion will be appreciated.
thanks
abdul (4 Replies)
Discussion started by: abdul
4 Replies
2. Programming
Hi
I'm getting
ld: fatal: option -h and building a dynamic executable are incompatible
ld: fatal: Flags processing errors
When I run
ld -shared -L/usr/dt/lib -lDtSvc -o builtin.so Workspace.o
after running
gcc -fPIC -I/usr/X11R6/include -I/usr/dt/include -c Workspace.c
I'm... (6 Replies)
Discussion started by: laho
6 Replies
3. UNIX for Dummies Questions & Answers
Hello,
Can anyone tell me how I can make a file link or shortcut in UNIX 4.0, several
file links where damaged during an outage examples below.
Examples: file -> file
libX11.so -> /usr/shlib/libX11.so.pre.O3D
All of the file links that were damaged were in /shlib and point to... (3 Replies)
Discussion started by: jays337
3 Replies
4. Programming
Dear friends,
First off all , let me apologize for my inexperience. I am just starting use of Linux and gcc .
Actually I ve some .c files in the present directory , and now I am
giving
+vc <my_file1.c> <my.file2.c> <myfile3.c>.
All the c files are in present directory.... (2 Replies)
Discussion started by: user_prady
2 Replies
5. Shell Programming and Scripting
I used to program ksh a while back, but I've been off in Oracle/Windows land (for clients -- not by choice) for so long that I can't remember what should be an easy thing. Here's the scenario:
1)Find all files and directories beneath some directory point (A).
2)If directory, make the... (7 Replies)
Discussion started by: scyphers
7 Replies
6. Solaris
i have two doubts..
1. what is the use /etc/project file. i renamed this file and when i tried to switch user or login with some user account the login was happening slowly. but when i renamed it to original name it was working fine... why so?
2. unix already has useradd and grouadd for... (4 Replies)
Discussion started by: chidori
4 Replies
7. Shell Programming and Scripting
this is what i have to find the files modified within the past 24 hours
find . -mtime -1 -type f -print0 | xargs -0 tar rvf "$archive.tar"
however i need to save/name this archive as the current date (MM-DD,YYYY.tar.gz)
how do i doo this (1 Reply)
Discussion started by: bugenhagen_
1 Replies
8. Shell Programming and Scripting
I have 2 txt files, 1.txt and 2.txt which contain the paths to files that need to be linked.
Example 1.txt:
/root/001/folder2/image4.nii.gz
/root/002/folder2/image4.nii.gz
Example 2.txt:
/root/001/folder2/image5.nii.gz
/root/002/folder2/image5.nii.gz
Each line represents images from... (7 Replies)
Discussion started by: LeftoverStew
7 Replies
9. Programming
Basically my problem is that when I try to compile anything using ./configure && make, it fails because of linker errors. I can reproduce the behavior I'm getting as follows:
I have the two following files
main.c:
#include <stdio.h>
extern void func(void);
int
main(int argc, char... (5 Replies)
Discussion started by: MarshallBanana
5 Replies
LEARN ABOUT DEBIAN
clisp-link
CLISP-LINK(1) Platform: x86_64-unknown-linux-gnu CLISP-LINK(1)
NAME
clisp-link - link a new external module to CLISP[1].
SYNOPSIS
clisp-link [create] [module] [file...]
clisp-link [add] [source] [destination] [module...]
clisp-link [run] [source] [module...]
clisp-link [install] [module...]
DESCRIPTION
This shell script operates on CLISP[1] module sets and linking sets:
o creates new module sets out of source files
o adds module sets to a linking set to produce a new linking set
o runs CLISP[1] with module sets added
o Only in CLISP[1] built without configure flag --without-dynamic-modules.
installs new module sets for general use
OPTIONS
create
The command
$ clisp-link create module file ...
creates a module set in module directory which refers (via symbolic links) to files file... The files are expected to be modules of
their own.
add
The command
$ clisp-link add source destination module ...
combines the linking set in directory source and the modules in directories module... to a new linking set, in the directory
destination which is newly created.
run
The command
$ clisp-link run source module ...
runs the linking set in directory source, with the modules in directories module... Unless CLISP[1] has been built with the
configuration option --without-dynamic-modules, the loading will be performed using SYS::DYNLOAD-MODULES. Otherwise - this is much
slower - a temporary linking set will be created and deleted afterwards.
install
Only in CLISP[1] built without configure flag --without-dynamic-modules.
The command
$ clisp-link install module ...
installs the modules in directories module... into CUSTOM:*LIB-DIRECTORY* or, if it is not writable to the user (e.g., if a system-wide
CLISP[1] installation is used and the user does not have administrative privileges), into CUSTOM:*USER-LIB-DIRECTORY*.
Variable CUSTOM:*USER-LIB-DIRECTORY* is initially set to (MERGE-PATHNAMES[2] ".clisp/" (USER-HOMEDIR-PATHNAME[3])) if that directory
exists, and can be reset in the RC file.
Note
Do not add CUSTOM:*USER-LIB-DIRECTORY* to CUSTOM:*LOAD-PATHS* or under any element thereof. Use REQUIRE instead of LOAD to load
dynamic modules.
For this command to work, each module directory must contain a Makefile with a clisp-module-distrib target which uses LN to distribute
the files necessary to run the module into destdir. This is in addition to the general requirement that link.sh is present.
EXAMPLES
See Section 32.2.6, "Example".
FILES
clisp-link needs a "link kit" directory containing:
o "modules.c"
o "clisp.h"
clisp-link expects to find these files in a subdirectory linkkit/ of the installation directory (i.e., CUSTOM:*LIB-DIRECTORY*) which it
acquires by running
$ `dirname $0`/clisp -b
This can be overridden by the environment variable[4] CLISP_LINKKIT.
SEE ALSO
CLISP impnotes
clisp(1)
AUTHORS
Bruno Haible <http://www.haible.de/bruno/>
The original author and long-time maintainer.
Michael Stoll <http://www.faculty.iu-bremen.de/mstoll/>
The original author.
Sam Steingold <http://sds.podval.org/>
Co-maintainer since 1998.
Others
See COPYRIGHT (file in the CLISP sources) for the list of other contributors and the license.
COPYRIGHT
Copyright (C) 1992-2010 Bruno Haible
Copyright (C) 1998-2010 Sam Steingold
NOTES
1. CLISP
http://clisp.cons.org
2. MERGE-PATHNAMES
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_merge-pathnames.html
3. USER-HOMEDIR-PATHNAME
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_user-homedir-pathname.html
4. environment variable
[set $man.base.url.for.relative.links]/basedefs/xbd_chap08.html
CLISP 2.49 Last modified: 2010-07-07 CLISP-LINK(1)