05-07-2004
If the Makefiles aren't too long, may be you can post here. You can't usually just concatenate two Makefiles. In some cases, the ordering of targets does matter.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am trying to install Gandalf, a computer vision and numerical library (http://gandalf-library.sourceforge.net/). I am using Cygwin on a Windows machine and have tried everything to get this to build, but to no avail.
Gcc, make, and libtool are all included in my Cygwin install. I... (1 Reply)
Discussion started by: justinh
1 Replies
2. UNIX for Dummies Questions & Answers
I need to develop a makefile that spans across directories. For example, let's say i have an upper level directory (main) and about 2 subdirectories. I want my .cpp files and .o files to be in one subdirectory. I want my .a files to be in the other subdirectory. The .a files are made up of the... (0 Replies)
Discussion started by: benjie_asu
0 Replies
3. Shell Programming and Scripting
for example in my make file im building path from env variables and string but need to see what is did
what is the best way to print the result?
say I have in my Makefile :
exec_prefix = $(RUN_ENV_LOCAL)/apache
and I will like to print the exec_prefix value , how can it be done ? (1 Reply)
Discussion started by: umen
1 Replies
4. UNIX for Advanced & Expert Users
Solved........ (0 Replies)
Discussion started by: klam
0 Replies
5. UNIX for Dummies Questions & Answers
This query is regarding the makefiles of linux kernel modules.
I saw at some sites on net it is suggesting to include the following path:
KERNEL_SOURCE := /usr/src/linux...
while at some places it is askibg to include /lib/modules path:
KERNEL_SOURCE := /lib/modules/2.6.27-7-generic/build... (0 Replies)
Discussion started by: rupeshkp728
0 Replies
6. Programming
I have several programs in several directories and want to use make to build the executables. What I have done is to put the main programs in their own directory together with a makefile to build the program. Then I am thinking of having another makefile residing in the directory above so I can run... (1 Reply)
Discussion started by: kristinu
1 Replies
7. Shell Programming and Scripting
I have a make file and want to write some information and am doing
@echo " RAYPK_LIBSRC = $(RAYPK_LIBSRC)"
The line of code produces
RAYPK_LIBSRC = ./source/library/raypk/time.f ./source/library/raypk/model.f ./source/library/raypk/tomo.f ./source/library/raypk/plt.f... (1 Reply)
Discussion started by: kristinu
1 Replies
8. Shell Programming and Scripting
I have several makefiles to build various programs in a software suite (currently 4 programs). I want to create a main Makefile so that I can build everything I need.
Unsure on the way I should proceed, for example using
include fdtc.mk
or calling
$(MAKE) -f ./mk/Makefile nfdtc
Here... (15 Replies)
Discussion started by: kristinu
15 Replies
9. Programming
I am trying to practice to create Makefiles. The goal is to create a makefile such that if a change is made to any of the source code files, the project can be rebuilt by typing make at the command line.
I have the following files:
ac.cc: has include ac.h and pg.h
fr.cc: has main... (8 Replies)
Discussion started by: pintu1228
8 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
I was going through some makefiles where I saw occurrences of explib_subdirs and expinc_subdirs, which I could not understand.
Exporting libs to subdirs ? Exporting include files to specified subdirs ? When do we need to do that ?
What I could understand is, for a build, I would... (4 Replies)
Discussion started by: alltaken
4 Replies
LEARN ABOUT DEBIAN
go-clean
GO-CLEAN(1) General Commands Manual GO-CLEAN(1)
NAME
go - tool for managing Go source code
SYNOPSIS
go clean [-i] [-r] [-n] [-x] [ packages ]
DESCRIPTION
Clean removes object files from package source directories. The go command builds most objects in a temporary directory, so go clean is
mainly concerned with object files left by other tools or by manual invocations of go build.
Specifically, clean removes the following files from each of the source directories corresponding to the import paths:
_obj/ old object directory, left from Makefiles
_test/ old test directory, left from Makefiles
_testmain.go
old gotest file, left from Makefiles
test.out
old test log, left from Makefiles
build.out
old test log, left from Makefiles
*.[568ao]
object files, left from Makefiles
DIR(.exe)
from go build
DIR.test(.exe)
from go test -c
MAINFILE(.exe)
from go build MAINFILE.go
In the list, DIR represents the final path element of the directory, and MAINFILE is the base name of any Go source file in the directory
that is not included when building the package.
OPTIONS
-i The -i flag causes clean to remove the corresponding installed archive or binary (what 'go install' would create).
-n The -n flag causes clean to print the remove commands it would execute, but not run them.
-r The -r flag causes clean to be applied recursively to all the dependencies of the packages named by the import paths.
-x The -x flag causes clean to print remove commands as it executes them.
For more about specifying packages, see go-packages(7).
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-CLEAN(1)