Sponsored Content
Full Discussion: Makefile wildcards
Top Forums Programming Makefile wildcards Post 4681 by rcscott on Monday 30th of July 2001 09:10:19 AM
Old 07-30-2001
Data Compiler

Sun WorkShop Compiler C 4.2
under Solaris 5.5.1

They can be compiled one after another as usual, but I do not want to specify each c file specifically in the makefile hence the use of a wildcard.

Any ideas ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Wildcards in VI

I'm trying to delete lines from a large text file using VI. Every line that I am wanting to delete start with 'S' - all others do not. (A list of users) I've tried using * but doesn't seem to like it...any ideas... Doesn't have to be VI - but I'm better with VI than sed/awk. (8 Replies)
Discussion started by: peter.herlihy
8 Replies

2. UNIX for Dummies Questions & Answers

wildcards

when writing a shell script (bourne) and using a unix command like 'ls' is there anything special you need to do to use a wildcard (like *)? (3 Replies)
Discussion started by: benu302000
3 Replies

3. UNIX for Dummies Questions & Answers

ls with wildcards

ok, I'm trying to write a script file that lists files with specific elements in the name into a txt file, it looks like this ls s*.dat > file_names.txt can't figure out whats wrong with that line, any ideas? thanks in advance (10 Replies)
Discussion started by: benu302000
10 Replies

4. UNIX for Dummies Questions & Answers

wildcards NOT

Hi All Please excuse another straightforward question. When creating a tar archive from a directory I am attempting to use wildcards to eliminate certain filetypes (otherwise the archive gets too large). So I am looking for something along these lines. tar -cf archive.tar * <minus all *.rst... (5 Replies)
Discussion started by: C3000
5 Replies

5. UNIX for Advanced & Expert Users

Makefile problem - How to run module load in a Makefile

Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error: make: module: command not found Why is this? Is there any way to run this command in a Makefile? NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 Replies)
Discussion started by: hernandinho
2 Replies

6. UNIX for Dummies Questions & Answers

wildcards in path

Is there some rule about using wildcards in path? Say I want to create a file, but one of the directories in the path is called 1433d.default and on different machines it will be called <some other string>.default touch ~/Library/Application/*.default/myfile In theory I thought that... (5 Replies)
Discussion started by: glev2005
5 Replies

7. UNIX for Advanced & Expert Users

Makefile executing another Makefile first?

I have 2 libraries in 2 different directories that I build with Makefiles. library B depends on library A. If I modify a .cpp file in library A and run lib B's Makefile can I have B's makefile to automatically rebuild library A? I am now rebuilding A, followed by B... but I'd like B to... (0 Replies)
Discussion started by: wwuster
0 Replies

8. UNIX for Dummies Questions & Answers

SED and wildcards

I am using this code to locate and modify one particular ID in a file containing thousands of entries sed 's/^>OldID/>NewID/g' Infile > Outfile How can I modify the code so I can rename all old IDs to a new unique ID? I tried this sed 's/^>*/>NewID/g' Infile > Outfile but it did not... (10 Replies)
Discussion started by: Xterra
10 Replies

9. UNIX for Advanced & Expert Users

Wildcards

These 2 websites do a GREAT job of explaining different types of wildcards. I learned about the categories of characters which I never knew about at all. GNU/Linux Command-Line Tools Guide - Wildcards GREP (1 Reply)
Discussion started by: cokedude
1 Replies

10. Homework & Coursework Questions

Help with Simple Multi-Level Makefile (Extremely New at Makefile)

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
Discussion started by: Tatl
1 Replies
PTH-CONFIG(1)						       GNU Portable Threads						     PTH-CONFIG(1)

NAME
pth-config - Pth library build utility VERSION
GNU Pth 2.0.7 (08-Jun-2006) SYNOPSIS
pth-config [--help] [--version] [--all] [--prefix] [--exec-prefix] [--bindir] [--libdir] [--includedir] [--mandir] [--datadir] [--acdir] [--cflags] [--ldflags] [--libs] DESCRIPTION
The pth-config program is a little helper utility for easy configuring and building applications based on the pth(3) library. It can be used to query the C compiler and linker flags which are required to correctly compile and link the application against the pth(3) library. OPTIONS
pth-config accepts the following options: --help Prints the short usage information. --version Prints the version number and date of the installed pth(3) library. --all Forces the output of all flags, that is, including extra flags which are not Pth specific. --prefix Prints the installation prefix of architecture independent files --exec-prefix Prints the installation prefix of architecture dependent files. --bindir Prints the installation directory of binaries. --libdir Prints the installation directory of libraries. --includedir Prints the installation directory of include headers. --mandir Prints the installation directory of manual pages. --datadir Prints the installation directory of shared data. --acdir Prints the installation directory of autoconf data. --cflags Prints the C compiler flags which are needed to compile the pth(3)-based application. The output is usually added to the "CFLAGS" vari- able of the applications "Makefile". --ldflags Prints the linker flags ("-L") which are needed to link the application with the pth(3) library. The output is usually added to the "LDFLAGS" variable of the applications "Makefile". --libs Prints the library flags ("-l") which are needed to link the application with the pth(3) library. The output is usually added to the "LIBS" variable of the applications "Makefile". EXAMPLE
CC = cc CFLAGS = -O `pth-config --cflags` LDFLAGS = `pth-config --ldflags` LIBS = -lm `pth-config --libs` all: foo foo: foo.o $(CC) $(LDFLAGS) -o foo foo.o $(LIBS) foo.o: foo.c $(CC) $(CFLAGS) -c foo.c SEE ALSO
pth(3), cc(1). AUTHOR
Ralf S. Engelschall rse@engelschall.com www.engelschall.com 08-Jun-2006 GNU Pth 2.0.7 PTH-CONFIG(1)
All times are GMT -4. The time now is 02:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy