X-Git-Url: https://git.lyx.org/gitweb/?a=blobdiff_plain;f=INSTALL.scons;h=799463bc102508612a8358ded58dee1b7bf752de;hb=e62e3a695c59fee5d2ee13940bb71dfdadca127f;hp=f0da4e24a92dbfca4639ebefda7d4a6bb19f054c;hpb=c9fb2a107e33331fb8bf215f663a6e171c0ca0f4;p=lyx.git

diff --git a/INSTALL.scons b/INSTALL.scons
index f0da4e24a9..799463bc10 100644
--- a/INSTALL.scons
+++ b/INSTALL.scons
@@ -111,6 +111,7 @@ Convenience options:
     command line options so you can run 'scons install' directly after a
     long 'scons all' building command. You can load selected options using
     load_option=opt1,opt2,... or exclude options using the - version of it.
+    Note that the option 'bundle' is not reloaded.
   * rebuild=target1,target2... By default, scons will exam all components
     when you build lyx. You can free scons from some hard work and save
     yourself some time by telling scons to rebuild only specified
@@ -154,7 +155,7 @@ You can specify one or more of the following targets:
   Installation:
     po, install = all + po, installer (windows only, need NSIS)
   Misc:
-    msvs_projects
+    msvs_projects, update_po
 
 Your built targets are put into $build_dir, which is debug (mode=debug),
 release (mode=release) or any name specified via build_dir=name. The
@@ -167,6 +168,11 @@ directory structure is:
 MSVS projects will be put to development/scons (and you should invoke
 scons from there for this target).
 
+update_po is similar to 'cd po; make update-po' but does not generate
+.gmo files, which is the task of the install target. Note that this 
+target is the only target that changes files (po/*.po in this case)
+of the lyx source tree.
+
 
 A typical working sequence:
 ---------------------------