As I read the partial build guideline, I'm a bit confuse on the build step. When I done my changes on the sw module, can I specifically just building the sw module only. I see there is a Makefile under the sw module, can I just issue `make` command right under this directory to build the sw module? Or may be there isn't a simple process by simply calling the `make` will get the job done.
I'm not sure how the build process going to be, I'm expecting some output or a physical file generate after the build complete. Where could I grab this output file and where should I move/plug it into the core module, thus when I launch OpenOffice, I could see my changes immediately. BTW, I suppose to see an executable file generate after the build (if I still remember correctly there is an executable file called soffice which will launch OpenOffice), but now I couldn't find it, where does it keep? On Thu, Feb 13, 2014 at 4:55 PM, Oliver-Rainer Wittmann < orwittm...@googlemail.com> wrote: > Hi, > > > On 12.02.2014 14:34, LOH KOK HOE wrote: > >> Thanks Andrea. Sorry for my mistake. >> >> To Oliver, >> You mention AOO build environment have to be setup, did you mean the full >> build at the very first step? Right after the command > "source >> LinuxX86-64Env.Set.sh" which will lead to this command > "cd >> instsetoo_native && build --all". Does the command > "build --all" is the >> AOO build environment that you mention? >> >> > Once you have created (via the configure) the corresponding platform > script - in your case 'LinuxX86-64Env.Set.sh' - you have everything > together to start building. > 'source LinuxX86-64Env.Set.sh' and you are theoretically able to build > individual modules. > But modules have dependencies to other modules. Thus, it is recommended to > build once all modules. Module instsetoo_native to the top module - it > creates the installation packages. It depends more or less on all modules. > A 'build --all' in instsetoo_native builds it after all modules are built > on which it depends. > After this step you are able to build individual modules as all > dependencies are available. > > Best regards, Oliver. > > > > THanks @! >> >> >> On Wed, Feb 12, 2014 at 5:20 AM, Andrea Pescetti <pesce...@apache.org >> >wrote: >> >> Forwarding the answer below to LOH KOK HOE, who is not subscribed. LOH >>> KOK >>> HOE: please read http://openoffice.apache.org/mailing-lists.html to know >>> how our mailing lists work, or you will miss answers. Andrea >>> >>> Oliver-Rainer Wittmann wrote: >>> >>> Hi, >>>> >>>> >>>> On 10.02.2014 14:08, LOH KOK HOE wrote: >>>> >>>> I would like to focus my contribution to writer module only, how could >>>>> I >>>>> build and test only for this module? Do I need to make a full build >>>>> for the >>>>> whole system in order to run my test? >>>>> >>>>> >>>>> A full build to play around with the Writer (module sw in folder >>>> main/) >>>> is not needed. But your AOO build environment have to be setup and >>>> available as for a full build. And you need an installation package >>>> which corresponds to the source code revision of your AOO build >>>> environment. >>>> Once you have setup your AOO build environment you can just perform a >>>> debug build of module sw. Afterwards you have to copy the created >>>> libraries into the program folder of your installation. >>>> >>>> Do not hesitate to ask for further and deeper information or concrete >>>> steps for your environment on your way to play around with the Writer >>>> module. >>>> >>>> >>>> Best regards, Oliver. >>>> >>>> >>>> Thanks @! >>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> >>>> >>>> >>>> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
