Sponsored Content
Top Forums Shell Programming and Scripting Building programs from separate makefiles Post 302759489 by Corona688 on Tuesday 22nd of January 2013 11:19:56 AM
Old 01-22-2013
I agree in principle. When writing new makefiles, one should write it as one system so it can run efficiently.

When you have to use someone else's makefiles however, you have very little control.

If you're not rewriting them, cramming them all together in one folder is hardly better than keeping them separate. When they were in folders, they were at least organized. Now it's one awful pile.

What option are you trying to pass, to what? If you're not calling make again, there's not a lot to pass options to.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Combining makefiles

I have concatenated 2 makefiles, to produce 1 however it is not running all of the code, producing a fatal error: symbol referencing errors. No output written. Can anybody please help? (4 Replies)
Discussion started by: Dan Rooney
4 Replies

2. UNIX for Dummies Questions & Answers

makefiles in a directory and subdirectories

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

How can I print variables im using in makefiles?

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

makefiles

Solved........ (0 Replies)
Discussion started by: klam
0 Replies

5. UNIX for Dummies Questions & Answers

Are programs like sys_open( ) ,sys_read( ) et al examples of system level programs ?

Are the programs written on schedulers ,thread library , process management, memory management, et al called systems programs ? How are they different from the programs that implement functions like open() , printf() , scanf() , read() .. they have a prefix sys_open, sys_close, sys_read etc , right... (1 Reply)
Discussion started by: vishwamitra
1 Replies

6. Programming

Makefiles for different programs

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. Programming

Makefile for building multiple programs

I have the following part of a makefile and want to simplify it using rules rather than having to code the same two blocks when I need ti build another program. An having difficulty doing it all: 1dvel2 1dvel 2dvel ... (8 Replies)
Discussion started by: kristinu
8 Replies

8. Programming

First time programmer needs Help with Makefiles

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

9. UNIX for Dummies Questions & Answers

Difference between inbuilt suid programs and user defined root suid programs under bash shell?

Hey guys, Suppose i run passwd via bash shell. It is a suid program, which temporarily runs as root(owner) and modifies the user entries. However, when i write a C file and give 4755 permission and root ownership to the 'a.out' file , it doesn't run as root in bash shell. I verified this by... (2 Replies)
Discussion started by: syncmaster
2 Replies

10. UNIX for Beginners Questions & Answers

Makefiles

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

NAME
folder - set folder or display current folder name (only available within the message handling system, mh) SYNOPSIS
folder [+folder] [msg] [options] OPTIONS
Displays information on all the folders in your Mail directory. The folders are listed alphabetically, with a line of information given for each folder. This is identical to the display produced by the folders command. See folders(1). Lists only the name of the current folder, with no additional information. This is faster because the folders need not be read. Displays a header produced by the system, in addition to the information about the current file. This header is identical to the one that appears at the top of the listing produced by folder -all or by folders. The header can be suppressed by using the -noheader option. Prints a list of the valid options to this com- mand. Lists the contents of the folder-stack. No +folder argument is allowed with this option. The contents of the folder-stack are listed automatically when the -pop or -push option is used. This corresponds to the dirs operation in the C-shell. Re-numbers messages in the folder. Messages are re-numbered sequentially, and any gaps in the numbering are removed. The default operation is -nopack, which does not change the numbering in the folder. Discards the top of the folder-stack, after setting the current folder to that value. No +folder argu- ment is allowed with this option. This corresponds to the popd operation in the C-shell; see csh(1). The -push and -pop options are mutu- ally exclusive: the last occurrence of either one overrides any previous occurrence of the other. Pushes the current folder onto the folder-stack, and makes the +folder argument into the current folder. If +folder is not given, the current folder and the top of the folder-stack are exchanged. This corresponds to the pushd operation in the C-shell; see csh(1). The -push switch and the -pop switch are mutually exclusive: the last occurrence of either one overrides any previous occurrence of the other. Lists each folder recursively. Information on the current folder is displayed, followed by information on any sub-folders which it contains. Displays only the total num- ber of messages and folders in your Mail directory. This option does not print any information about the current folder. It can be sup- pressed using the -nototal option. The defaults for folder are: +folder defaults to the current folder msg defaults to none -nofast -noheader -nototal -nopack -norecurse DESCRIPTION
The folder command lets you set the current folder, or display information about it. It can also be used to manage the folder stack. If you use the folder command without a +folder argument, information about the current folder is displayed on the screen. If you use folder with the +folder argument, the named folder is set to be the current folder. Information about the named folder is also displayed on the screen. If you use folder with the msg argument, it will set the specified message to be current. Information on the current folder is also dis- played. You can use both the +folder and msg arguments together in one command. If you specify a +folder that does not exist, you are asked whether you want to create it. This is a good way to create an empty folder for later use. The display is identical whether you set the folder or display the contents of the current folder. The following example shows the type of display that is produced. The display lists the current folder, the number of messages in it, the range of the messages (low-high), and the current message within the folder. It also flags extra files if they exist. inbox+ has 16 messages ( 3- 22); cur= 15. RESTRICTIONS
Do not create folder names that are made up of only digits. PROFILE COMPONENTS
Current-Folder: To find the default current folder Folder-Protect: To set mode when creating a new folder Folder-Stack: To determine the folder stack lsproc: Program to list the contents of a folder EXAMPLES
The following example shows how folder can be used to change the current folder to +test, and display information on that folder. The plus sign (+) next to test indicates that it is now the current folder. % folder +test test+ has 2 messages ( 1- 2); cur= 2. The next example shows the display produced by using the -all option to folder: Folder # of messages ( range ); cur msg (other files) V2.3 has 3 messages ( 1- 3). adrian has 20 messages ( 1- 20); cur= 2. brian has 16 messages ( 1- 16). chris has 12 messages ( 1- 12). copylog has 242 messages ( 1- 242); cur= 225. inbox+ has 73 messages ( 1- 127); cur= 127. int has 4 messages ( 1- 4); cur= 2 (others). jack has 17 messages ( 1- 17); cur= 17. TOTAL= 387 messages in 8 folders. This display is identical to that produced by the folders command. See folders(1) for an explanation of this display. The next example shows how to use folder to create an empty folder: % folder +test Create folder "$HOME/Mail/test"? y test+ has no messages. You can also use folder to create an empty sub-folder within an existing folder. The following example shows how you can create a sub-folder in the folder +test: % folder +test/testtwo Create folder "$HOME/Mail/test/testwo"? y test/testtwo+ has no messages. See refile(1) for more details of sub-folders. FILES
The user profile. SEE ALSO
csh(1), refile(1), mhpath(1) folder(1)
All times are GMT -4. The time now is 11:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy