12-27-2012
Some prefer to do it in two lines, one for .cc.o and one for .o.exe or whatever, so the first also supports code going into libraries, and there is just one place for those options in make definitions.
I usually see the compiler options, -D's, -I's (preprocess is before compile, is before link), the -L right before the -l's it supports, -l's for each linked library and source or local object at the right end. I like to use dynamic linking, so no -L's, just a good LD_LIBRARY_PATH (or whatever your system likes to use, see man ld() for rules).
Sometimes I would -c compile all the .c or .cc into .o and ar them all into one library .a file, as order does not matter within a library, and finally compile with the .a file explicitly only. Only good for one main()! One best practice says put only one subroutine/function in each source file, and then the order is tricky. You can have one .a for each main() and it's "private" functions/methods/subroutines, and then link in any common code libraries.
The -I path must support the entry name or relative path in the source #include's (-I/a/b/c and #include "d/e.h" is for /a/b/c/d/e.h).
Last edited by DGPickett; 12-27-2012 at 06:07 PM..
7 More Discussions You Might Find Interesting
1. Linux
Hi All,
I installed Linux recently on my PC and finding it difficult to boost its performance.
It takes hell lot of time to open Mozilla, text pad , & even the booting process is too slow, many a times I got to manually power off to shutdown the computer.
I will be glad if you could help me... (18 Replies)
Discussion started by: jayfriend
18 Replies
2. Solaris
Is it possible to build Boost 1.35 using Sun Studio 10?
I can build Boost 1.35 using Sun Studio 11 successful. However, i'm unable to build it using Sun Studio 10 using the exact method.
I really apprecaite if any expert can help on this.
Thanks, (2 Replies)
Discussion started by: shingpui
2 Replies
3. Solaris
Hi All
I am working unders Sun Solaris and I am not
"/opt/boost/boost/thread/detail/thread.hpp", line 344: Error: boost::thread::thread(boost::thread&) is not accessible from boost::move(boost::detail::thread_move_t<boost::thread>).
Do you know if there are other solutions other than... (2 Replies)
Discussion started by: manustone
2 Replies
4. Programming
Hi,
Based on the following example in the Boost C++ website:
www. boost.org/doc/libs/1_47_0/doc/html/boost_asio/example/echo/async_tcp_echo_server.cpp]doc/html/boost_asio/example/echo/async_tcp_echo_server.cpp
I tried to create a similar TCP server that waits to accept a client connection... (0 Replies)
Discussion started by: tanlccc
0 Replies
5. Solaris
hi guys,
i downloaded boost1_49_0 tar.gz... then unzip and untar...
how to install boost 1_49_0 in solaris
plz help me (1 Reply)
Discussion started by: coolboys
1 Replies
6. UNIX for Dummies Questions & Answers
Hello all,
I am trying to "make" a database system, VDB (Veritas Data Base), and when I run "make" I receive the following error:
VDBException.h:19: error: expected `)' before '*' token
VDBException.h:20: error: expected `)' before '*' token
VDBException.h:43: error: expected `)' before '*'... (4 Replies)
Discussion started by: Tyler_92
4 Replies
7. Programming
Hi,
I just started using CMake and the Boost Libraries. In this progress I encountered some problems.
One of these problems is combining Boost unit tests with cmake. I don't know how to set the whole project up. I tried to set up a simple test project. This contains a main.cpp a comp.cpp and the... (0 Replies)
Discussion started by: ElCoyote
0 Replies
split(1) General Commands Manual split(1)
NAME
split - split a file into pieces
SYNOPSIS
line_count] suffix_length] [file [name]]
nsuffix_length] [file [name]]
Obsolescent
n] [file [name]]
DESCRIPTION
reads file and writes it in pieces (default 1000 lines) onto a set of output files. The name of the first output file is name with
appended, and so on lexicographically, up to (only ASCII letters are used, a maximum of 676 files). If no output name is given, is the
default.
If no input file is given, or if is given instead, the standard input file is used.
Options
recognizes the following command-line options and arguments:
The input file is split into pieces
line_count lines in size.
suffix_length letters are used to form the suffix of the output filenames. This option allows creation of more than 676 output
files. The output file names created cannot exceed the maximum file name length allowed in the directory containing
the files.
The input file is split into pieces
n bytes in size.
The input file is split into pieces
n x 1024 bytes in size. No space separates the n from the
The input file is split into pieces
n x 1048576 bytes in size. No space separates the n from the
The input file is split into pieces
n lines in size. This option is obsolescent and is equivalent to using the option.
EXTERNAL INFLUENCES
Environment Variables
determines the locale for the interpretation of text as single- and/or multi-byte characters.
determines the language in which messages are displayed.
If or is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty
variable. If is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of
If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to "C". See
environ(5).
International Code Set Support
Single- and multi-byte character code sets are supported.
SEE ALSO
csplit(1).
STANDARDS CONFORMANCE
split(1)