10-27-2010
I suppose it generated -I and -L -lxxx -lyyy, but usually you can just put them in the Makefile as assignments or make includes. You might generate the variable setup with a make include, and then just reference the make variables.
The cc can make an include dependency lists using -I.
ldd can tell you where the -L dirs are, although if dynamic libs are used, there is usually an environment variable for all the necessary directories, so you need just -l's.
10 More Discussions You Might Find Interesting
1. Programming
I need for help . (1 Reply)
Discussion started by: dsun5
1 Replies
2. Programming
:( :confused: Does anybody here know how to compile and run C++ programs in UNIX enviroment? I am so confused. Any help on this would be greatly appreciated! Thanks! (5 Replies)
Discussion started by: Kahuashi
5 Replies
3. Shell Programming and Scripting
I've seen a few other threads like this, but they either went unanswered or failed to answer my question.
How do I set an environment variable in a Makefile?
What I'm trying to do is use GNU make to automate an ant build.
In order to run ant, I've got to first set a few environment... (1 Reply)
Discussion started by: Bags
1 Replies
4. Shell Programming and Scripting
Hi,
Can we execute a shell script by makefile.
I mean we will write a shell script in a make file and it will be executed when we compile the C++ program using make file. (2 Replies)
Discussion started by: surjyap
2 Replies
5. Shell Programming and Scripting
Is there a way to write a makefile for all the source files in a directory with a shell script? (2 Replies)
Discussion started by: zzhan
2 Replies
6. Shell Programming and Scripting
How can i compile a KSH shell script. I Dont want to execute it. I just need to compile it .
Any Help sincerly appreciated. (5 Replies)
Discussion started by: panyam
5 Replies
7. UNIX for Dummies Questions & Answers
this is my first post so Hello,
here is my question
@top level Makefile should not set values for
environment variables FC, CC, FFLAGS (etc) but
use the ones that mpi_make sets.
So as you can see i have to run an mpi program, in fortran and i am supposed to do the above.the program was... (3 Replies)
Discussion started by: Kwstas
3 Replies
8. Programming
Dear all
I try to write a makefile for my code which have many source files, 1 header file that i make and exist into same folder with other source files and some other header files (by libraries witch i use) that found in other folders.
In my header file i have put all other #includes for... (3 Replies)
Discussion started by: panou
3 Replies
9. Shell Programming and Scripting
Hello,
I have a Makefile that converts wrl (vrml) files to html files...
how can I use a shell script in that makefile which works on all html files after converting?
The Shell Script have to find and replace a String in every createt html file.
sorry I'm a Newbie, so I hope someone can... (0 Replies)
Discussion started by: Dan_78
0 Replies
10. AIX
I have a make file for C program, which always gives the error
ld: 0711-738 ERROR: Input file ../src/file_name.o
XCOFF32 object files are not allowed in 64 mode
Does anybody know the problem?
Thanks for contribution (2 Replies)
Discussion started by: digioleg54
2 Replies
LEARN ABOUT DEBIAN
dh_auto_install
DH_AUTO_INSTALL(1) Debhelper DH_AUTO_INSTALL(1)
NAME
dh_auto_install - automatically runs make install or similar
SYNOPSIS
dh_auto_install [buildsystemoptions] [debhelperoptions] [--params]
DESCRIPTION
dh_auto_install is a debhelper program that tries to automatically install built files. It does so by running the appropriate command for
the build system it detects the package uses. For example, if there's a Makefile and it contains a install target, then this is done by
running make (or MAKE, if the environment variable is set). If there is a setup.py or Build.PL, it is used. Note that the Ant build system
does not support installation, so dh_auto_install will not install files built using Ant.
Unless --destdir option is specified, the files are installed into debian/package/ if there is only one binary package. In the multiple
binary package case, the files are instead installed into debian/tmp/, and should be moved from there to the appropriate package build
directory using dh_install(1).
DESTDIR is used to tell make where to install the files. If the Makefile was generated by MakeMaker from a Makefile.PL, it will
automatically set PREFIX=/usr too, since such Makefiles need that.
This is intended to work for about 90% of packages. If it doesn't work, or tries to use the wrong install target, you're encouraged to skip
using dh_auto_install at all, and just run make install manually.
OPTIONS
See "BUILD SYSTEM OPTIONS" in debhelper(7) for a list of common build system selection and control options.
--destdir=directory
Install files into the specified directory. If this option is not specified, destination directory is determined automatically as
described in the "DESCRIPTION" section.
-- params
Pass params to the program that is run, after the parameters that dh_auto_install usually passes.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
9.20120909 2011-10-19 DH_AUTO_INSTALL(1)