ENH: Clarify target_link_libraries docs

The target_link_libraries command supports flags as well as libraries.
This makes the support explicit in the documentation.
This commit is contained in:
Brad King 2009-02-02 09:42:23 -05:00
parent 367101b02c
commit eea054d82c
1 changed files with 7 additions and 5 deletions

View File

@ -64,12 +64,14 @@ public:
virtual const char* GetFullDocumentation() virtual const char* GetFullDocumentation()
{ {
return return
" target_link_libraries(<target> [lib1 [lib2 [...]]]\n" " target_link_libraries(<target> [item1 [item2 [...]]]\n"
" [[debug|optimized|general] <lib>] ...)\n" " [[debug|optimized|general] <item>] ...)\n"
"Specify a list of libraries to be linked into the specified target. " "Specify libraries or flags to use when linking a given target. "
"If any library name matches that of a target in the current project " "If a library name matches that of another target in the project "
"a dependency will automatically be added in the build system to make " "a dependency will automatically be added in the build system to make "
"sure the library being linked is up-to-date before the target links." "sure the library being linked is up-to-date before the target links. "
"Item names starting with '-', but not '-l' or '-framework', are "
"treated as linker flags."
"\n" "\n"
"A \"debug\", \"optimized\", or \"general\" keyword indicates that " "A \"debug\", \"optimized\", or \"general\" keyword indicates that "
"the library immediately following it is to be used only for the " "the library immediately following it is to be used only for the "