![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts here. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Include directive | clalfa | High Level Programming | 2 | 02-02-2008 05:14 PM |
| vpath to an hdisk | 2dumb | AIX | 5 | 05-04-2007 08:03 AM |
| vpath fbvol relationship | samaks | AIX | 1 | 11-03-2006 12:04 AM |
| precompile directive? | norsk hedensk | High Level Programming | 2 | 10-03-2005 11:01 AM |
| apache directive only for outside network | dangral | UNIX for Dummies Questions & Answers | 2 | 02-06-2005 06:19 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
vpath directive in make
Hi all,
I need to check the contents of my vpath directive in my file. Is it possible to check the contents of the vpath directive as we do for a variable like @echo '$vpath' . Please let me know the above is correct or suggest me the correct one. Thanks in advance. -Jerry |
| Forum Sponsor | ||
|
|
|
#2
|
|||
|
|||
|
let me put the question in an approchable way..
In my make file I have a prerequisite which is a library and the I have the library in /jerry/lib and I have included the path in the vpath directive as vpath %.so /jerry/lib but still I get an error stating that the directory cant be found during the build. Hope this help and get more help from you guys.. -Jerry |
|
#3
|
|||
|
|||
|
The reason I was trying to print vpath is to find whether the libraries I have given in the pre-requisities list is added to the vpath for the searching.
The missing library problem is solved when I gave the library with the whole name instead of giving as -l<name>. This is a workaround and not the actual solution I still was not able to figure out why it didnt worked with -l<name>. Thank you -Jerry |
|
#4
|
||||
|
||||
|
I have no idea what you're talking about. In my universe, VPATH is a macro and you can do stuff like:
Code:
VPATH=/this:/that:/the/other/thing
default:
@echo in makefile VPATH = $(VPATH)
|
|
#5
|
|||
|
|||
|
The vpath (lower case) is a directive different from VPATH(uppercase) variable. vpath is more selective than VPATH. In VPATH you will give the path where the make should search for the libraries etc.
With vpath you can specify, for a specific pattern of pre-requisities needs to be searched in a specific path. How to use - vpath pattern directories Specify the search path directories for file names that match pattern. The search path, directories, is a list of directories to be searched, separated by colons (semi-colons on MS-DOS and MS-Windows) or blanks, just like the search path used in the VPATH variable. Eg. vpath %.h ../headers tells make to look for any prerequisite whose name ends in .h in the directory ../headers if the file is not found in the current directory. -Jerry |
|
#6
|
|||
|
|||
|
In this link U can find Details about "vpath"
|
|
#7
|
|||
|
|||
|
I have the same question as Jerry
How to print the "vpath" directive to see the list of results created during pattern search?
I see that in my code vpath is not able to get the directory path properly and hence all the files that I look for are reported as "not found" Is there any bug reported on the "vpath" ?? Thanks Sriram |
|||
| Google The UNIX and Linux Forums |