Sponsored Content
Top Forums Programming Makefile includes and shell environment during compile Post 302466878 by DGPickett on Wednesday 27th of October 2010 03:12:56 PM
Old 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 have not c compile environment ,i can download it but it ends with *.gz,so i can't

I need for help . (1 Reply)
Discussion started by: dsun5
1 Replies

2. Programming

How to compile and run C++ programs in UNIX environment?

:( :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

Setting environment variables in Makefile

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

shell script in makefile

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

Shell script makefile

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

compile a shell script

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

change makefile environment variables

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

Makefile + #includes

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

using a Shell Script in a Makefile

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

Error when run makefile to compile C program

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
ldd_ia(1)						      General Commands Manual							 ldd_ia(1)

NAME
ldd_ia: ldd - list dynamic dependencies of executable files or shared libraries on Integrity systems SYNOPSIS
filename... Remarks This manpage describes on Integrity systems. For on PA-RISC systems, see ldd_pa(1). DESCRIPTION
is a command that can list the dynamic dependencies of incomplete executable files or shared libraries. lists verbose information about dynamic dependencies and symbol references. If the object file is an executable file, lists all shared libraries that would be loaded as a result of executing the file. If it is a shared library, lists all shared libraries that would be loaded as a result of loading the library. uses the same algorithm as the dynamic loader and to locate the shared libraries at runtime. See in dld.so(5) for more information. Options recognizes the following options: Check reference to data symbols. Check reference to data and code symbols. Display the search path used to locate the shared libraries. Display all dependency relationships. EXTERNAL INFLUENCES
Environment Variables uses the following environment variables to locate shared libraries. These environment variables can be used to specify the directories to be searched for library files at runtime. The value is a colon-separated list of paths of such directories. For more information, see in dld.so(5) or the option in ld(1). The following internationalization variables affect the execution of Determines the locale category for native language, local customs and coded character set in the absence of and other environment variables. If is not specified or is set to the empty string, a default of (see lang(5)) is used instead of Determines the values for all locale categories and has precedence over and other environment variables. Determines the locale that should be used to affect the format and contents of diagnostic messages written to standard error. Determines the locale category for numeric formatting. Determines the locale category for character handling functions. Determines the location of message catalogs for the processing of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to See envi- ron(5). DIAGNOSTICS
prints the record of shared library path names to stdout. The optional list of symbol resolution problems are printed to stderr. returns zero when the operation is successful. A non-zero return code indicates that an error occurred. EXAMPLES
By default prints a simple dynamic path information. This consists of the dependencies recorded in the executable (or the shared library) followed by the physical location where these libraries are found. The option causes to print dependency relationship along with the dynamic path information. The option to causes it to analyze all symbol references and print information about unsatisfied code and data symbols. WARNINGS
does not list shared libraries explicitly loaded using dlopen(3C) or shl_load(3X). FILES
output file 32-bit Integrity system dynamic loader 64-bit Integrity system dynamic loader 32-bit dummy executable loaded to check the dependencies of shared libraries 64-bit dummy executable loaded to check the dependencies of shared libraries message catalog SEE ALSO
System Tools ld(1) invoke the link editor Miscellaneous a.out(4) assembler, compiler, and linker output dld.so(5) dynamic loader Texts and Tutorials
All times are GMT -4. The time now is 01:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy