Multiple Directories - Revision history

Jadrian Miles at 23:52, 6 March 2011

2011-03-06T23:52:51Z

← Older revision		Revision as of 23:52, 6 March 2011
Line 23:		Line 23:


	While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged prior to installation as they are built. Library binaries are copied into a '''lib/''' directory and headers into an '''include/''' directory at the top level of the project.		While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged prior to installation as they are built. Library binaries are copied into a '''lib/''' directory and headers into an '''include/''' directory at the top level of the project (as specified by the [[PROJECT_HOME]] variable in the Makefile).

Brad Berg at 14:29, 2 March 2011

2011-03-02T14:29:22Z

← Older revision		Revision as of 14:29, 2 March 2011
Line 23:		Line 23:


	While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged ~~for~~ installation as they are built. Library binaries are copied into a '''lib/''' directory and headers into an '''include/''' directory at the top level of the project.		While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged prior to installation as they are built. Library binaries are copied into a '''lib/''' directory and headers into an '''include/''' directory at the top level of the project.

Brad Berg at 14:28, 2 March 2011

2011-03-02T14:28:08Z

← Older revision		Revision as of 14:28, 2 March 2011
Line 23:		Line 23:


	While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged for installation as they are built. Library binaries are ~~staged in~~ a '''lib/''' directory and headers in an '''include/''' directory at the top level of the project.		While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged for installation as they are built. Library binaries are copied into a '''lib/''' directory and headers into an '''include/''' directory at the top level of the project.

Brad Berg at 14:26, 2 March 2011

2011-03-02T14:26:52Z

← Older revision		Revision as of 14:26, 2 March 2011
Line 23:		Line 23:


	While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged for installation as they are built. Library binaries are staged in a '''lib/''' directory and headers in an '''include/''' directory at the top level of the project~~. When a project is installed the contents of the staging area are copied to the install target location~~.		While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged for installation as they are built. Library binaries are staged in a '''lib/''' directory and headers in an '''include/''' directory at the top level of the project.

Brad Berg at 14:20, 2 March 2011

2011-03-02T14:20:59Z

← Older revision		Revision as of 14:20, 2 March 2011
Line 1:		Line 1:
	Larger projects require more than one directory. Project developers are free to organize directories as they see fit. To make it clear for others, the top level directory should contain project wide information and a Makefile to build all project directories. The build system only only aware of the current directory. Build dependencies between directories is encoded using raw Make commands (e.g. See common/utility/Makefile).		Larger projects require more than one directory. Project developers are free to organize directories as they see fit. To make it clear for others, the top level directory should contain project wide information and a Makefile to build all project directories. The build system is only only aware of the current directory. Build dependencies between directories are encoded using raw Make commands (e.g. See common/utility/Makefile).

	Each project directory can contain a single library plus several programs. A project with multiple libraries will need a separate directory for each library. C++ Libraries use header files to define their interface. Header files are installed along with the library. Some header files are only used internally and are not installed. Set the [[INCLUDE_H]] variable to only those headers that are to be installed.		Each project directory can contain a single library plus several programs. A project with multiple libraries will need a separate directory for each library. C++ Libraries use header files to define their interface. Header files are installed along with the library. Some header files are only used internally and are not installed. Set the [[INCLUDE_H]] variable to only those headers that are to be installed.

	When writing C/C++ code include installed headers with:		When writing C/C++ code, include installed headers with:

	#include <myproject/header.h>		#include <myproject/header.h>
Line 18:		Line 18:


	Libraries to be installed in a project need to be built before any programs that depend on them. This is because ~~the~~ program ~~link~~ needs the library ~~binary~~ files and the program code needs to be able to access the header files with:		Libraries to be installed in a project need to be built before any programs that depend on them. This is because program linking needs the binary library files and the program code needs to be able to access the header files with:

	#include <myproject/header.h>		#include <myproject/header.h>


	While a project is being built nothing has been installed yet. To facilitate building dependent directories ~~the~~ libraries are staged for installation as they are built. Library binaries are staged in a '''lib/''' directory and headers in an '''include/''' directory at the top level of the project. When a project is installed the contents of the staging area are copied to the install target.		While a project is being built nothing has been installed yet. To facilitate building dependent directories libraries are staged for installation as they are built. Library binaries are staged in a '''lib/''' directory and headers in an '''include/''' directory at the top level of the project. When a project is installed the contents of the staging area are copied to the install target location.

Brad Berg at 14:16, 2 March 2011

2011-03-02T14:16:57Z

← Older revision		Revision as of 14:16, 2 March 2011
Line 23:		Line 23:


	While a project is being built nothing has been installed yet. To facilitate building dependent directories the libraries are staged for installation as they are built. Library binaries are staged in a "lib/" directory and headers in an "include" directory at the top level of the project. When a project is installed the contents of the staging area are copied to the install target.		While a project is being built nothing has been installed yet. To facilitate building dependent directories the libraries are staged for installation as they are built. Library binaries are staged in a '''lib/''' directory and headers in an '''include/''' directory at the top level of the project. When a project is installed the contents of the staging area are copied to the install target.

Brad Berg at 14:13, 2 March 2011

2011-03-02T14:13:56Z

← Older revision		Revision as of 14:13, 2 March 2011
Line 2:		Line 2:

	Each project directory can contain a single library plus several programs. A project with multiple libraries will need a separate directory for each library. C++ Libraries use header files to define their interface. Header files are installed along with the library. Some header files are only used internally and are not installed. Set the [[INCLUDE_H]] variable to only those headers that are to be installed.		Each project directory can contain a single library plus several programs. A project with multiple libraries will need a separate directory for each library. C++ Libraries use header files to define their interface. Header files are installed along with the library. Some header files are only used internally and are not installed. Set the [[INCLUDE_H]] variable to only those headers that are to be installed.

			When writing C/C++ code include installed headers with:

			#include <myproject/header.h>


			Internal headers in the current directory are included as:

			#include "header.h"


			Internal headers in another directory are included with a relative path:

			#include "../mylibrary/header.h"


			Libraries to be installed in a project need to be built before any programs that depend on them. This is because the program link needs the library binary files and the program code needs to be able to access the header files with:

			#include <myproject/header.h>


			While a project is being built nothing has been installed yet. To facilitate building dependent directories the libraries are staged for installation as they are built. Library binaries are staged in a "lib/" directory and headers in an "include" directory at the top level of the project. When a project is installed the contents of the staging area are copied to the install target.

Brad Berg: New page: Larger projects require more than one directory. Project developers are free to organize directories as they see fit. To make it clear for others, the top level directory should contain ...

2011-03-02T13:43:47Z

New page: Larger projects require more than one directory. Project developers are free to organize directories as they see fit. To make it clear for others, the top level directory should contain ...

New page

Larger projects require more than one directory. Project developers are free to organize directories as they see fit. To make it clear for others, the top level directory should contain project wide information and a Makefile to build all project directories. The build system only only aware of the current directory. Build dependencies between directories is encoded using raw Make commands (e.g. See common/utility/Makefile).

Each project directory can contain a single library plus several programs. A project with multiple libraries will need a separate directory for each library. C++ Libraries use header files to define their interface. Header files are installed along with the library. Some header files are only used internally and are not installed. Set the [[INCLUDE_H]] variable to only those headers that are to be installed.