07-30-2001
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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
g-wrap-config
g-wrap-config(1) General Commands Manual g-wrap-config(1)
NAME
g-wrap-config - script to get information about the installed version of G-Wrap
SYNOPSIS
g-wrap-config [ --version ] [ --c-compile-args LANG | --c-link-args LANG | --guile-module-directory ]
DESCRIPTION
g-wrap-config is a tool that is used to configure and determine the compiler and linker flags that should be used to compile and link
progams, libraries, and plugins that use G-Wrap. However, since G-Wrap 1.9, this tool has been deprecated in favor of pkg-config(1). New
code should use the g-wrap-2.0-guile pkg-config module, g-wrap-config only exists for compatibility reasons.
OPTIONS
--c-compile-args LANG
Print the compiler flags that are necessary to compile a program or library that uses the G-Wrap language binding for LANG.
--c-link-args LANG
Print the linker flags that are necessary to link a program that uses the G-Wrap language binding for LANG.
--version
Prints the currently installed version of G-Wrap on standard output.
EXAMPLES
gcc -o main.o $(g-wrap-config --c-compile-args guile) main.c
is how you might use g-wrap-config to compile a C source file for an executable program.
gcc -o my_app $(g-wrap-config --c-link-args guile) main.o util.o
is how you might use g-wrap-config to link compiled objects into an executable program.
AUTHOR
G-Wrap has been written by Andreas Rottmann, Rob Browning and Christopher Lee.
This manual page was written by Andreas Rottmann, originally for the Debian Project.
G-Wrap 1.9 2005-05-01 g-wrap-config(1)