mirror of
https://github.com/ethauvin/kobalt-doc.git
synced 2025-04-25 03:57:11 -07:00
Fix sections.
This commit is contained in:
parent
4248eab785
commit
45716813ce
1 changed files with 16 additions and 16 deletions
|
@ -478,7 +478,7 @@ assemble {
|
|||
ways to use <code>install</code>.
|
||||
</p>
|
||||
|
||||
<h3 class="section" id="install-target" indent="1">Bulk install</h3>
|
||||
<h3 class="section" indent="2" id="install-target" indent="1">Bulk install</h3>
|
||||
|
||||
<p>
|
||||
The simplest way to install is either not specify anything in the <code>install</code> directive or an optional
|
||||
|
@ -489,13 +489,13 @@ assemble {
|
|||
target = "libs"
|
||||
}
|
||||
</pre>
|
||||
|
||||
<p>
|
||||
With this approach, everything that was generated in <code>kobaltBuild/libs</code> gets copied to this
|
||||
target directory.
|
||||
</p>
|
||||
|
||||
<h3 class="section" id="install-include" indent="1">Fine grained install</h3>
|
||||
|
||||
<h3 class="section" indent="2" id="install-include" indent="1">Fine grained install</h3>
|
||||
<p>
|
||||
You can also be more selective in what you install with either the <code>copy</code> directive to copy
|
||||
individual files or with <code>include</code>, which lets you specify more sophisticated ways of moving
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue