I checked again and found that: using the "make module-name", for example, If I modify the module named "desktop", I will use: xxx/core> make desktop And it shows as below: ======================= xxx/core>* make desktop* cd xxx/core/desktop && /usr/bin/make -j 4 -rs [build DEP] LNK:Executable/soffice.bin [build C ] desktop/source/app/main.c [build CHK] loaded modules: desktop ... [build LNK] Executable/soffice.bin [build MOD] desktop [build ALL] top level modules: desktop [build ALL] loaded modules: desktop ... It can save some time. ======================== I run the command: xxx/core> *./install/program/soffice* No effects work in the results. Next, there are two methods which can get to the same goal. /Method-1:/ And I used *make dev-install*. It works well; /Method-2:/ And I used make dev-install-nocheck (or *make dev-install -o build*) And then,run the command: xxx/core> *./install/program/soffice*. It works well. Obviously, method-2 is part of method1, so that it can save some time. And what the side effect of the method-2 was, I couldn't meet it yet.
-- View this message in context: http://nabble.documentfoundation.org/How-to-remake-a-modified-source-codes-not-the-first-time-based-on-source-codes-core-which-has-been-m-tp4053499p4054020.html Sent from the Dev mailing list archive at Nabble.com. _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
