Apache OpenOffice Buildsystem
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Alternative Title |
| |
| Title of Series | ||
| Number of Parts | 490 | |
| Author | ||
| License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/47492 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSDEM 2020311 / 490
4
7
9
10
14
15
16
25
26
29
31
33
34
35
37
40
41
42
43
45
46
47
50
51
52
53
54
58
60
64
65
66
67
70
71
72
74
75
76
77
78
82
83
84
86
89
90
93
94
95
96
98
100
101
105
106
109
110
116
118
123
124
130
135
137
141
142
144
146
151
154
157
159
164
166
167
169
172
174
178
182
184
185
186
187
189
190
191
192
193
194
195
200
202
203
204
205
206
207
208
211
212
214
218
222
225
228
230
232
233
235
236
240
242
244
249
250
251
253
254
258
261
262
266
267
268
271
273
274
275
278
280
281
282
283
284
285
286
288
289
290
291
293
295
296
297
298
301
302
303
305
306
307
310
311
315
317
318
319
328
333
350
353
354
356
359
360
361
370
372
373
374
375
379
380
381
383
385
386
387
388
391
393
394
395
397
398
399
401
409
410
411
414
420
421
422
423
424
425
427
429
430
434
438
439
444
449
450
454
457
458
459
460
461
464
465
466
468
469
470
471
472
480
484
486
487
489
490
00:00
Integrated development environmentBuildingInformationElectronic program guidePhase transitionSoftware development kitJava appletSoftware testingScripting languageDefault (computer science)Software frameworkSelf-organizationComputer configurationConfiguration spaceMultiplication signPhysical systemOffice suiteTextsystemBitProjective planeOpen setWikiSoftware developerDefault (computer science)Software testingBuildingIntegrated development environmentJava appletLink (knot theory)Software frameworkComputer configurationFirmwareRevision controlRobotConfiguration spaceLibrary (computing)WebsiteLevel (video gaming)WindowDistribution (mathematics)Web pageAxiom of choiceOrder (biology)CodeOpen sourcePresentation of a groupException handlingAuthorizationScripting languageMetropolitan area networkDifferent (Kate Ryan album)InformationBinary filePhase transition19 (number)Traffic reportingText editorMappingSound effectProcess (computing)Staff (military)Instance (computer science)FamilyThomas BayesOptical disc driveService (economics)Automatic differentiationElement (mathematics)Computer animation
08:53
WikiAbelian categoryExecution unitBuildingComputer configurationIntegrated development environmentShared memoryGroup actionSound effectSqueeze theoremStaff (military)Optical disc drivePerspective (visual)Physical systemMereologyMultiplication signAreaFlow separationFrequencyArithmetic meanCodecSpacetimeBitFormal languageHuman migrationCategory of beingIntegrated development environmentWikiFreewareAxiom of choiceComputer animation
11:57
WikiAbelian categoryBuildingComputer configurationIntegrated development environmentBuildingUnit testingSymbol tableGroup actionComputer clusterCodecCuboidError messageMoving averageSoftware testingComputer configurationInstallation artTunisAreaOffice suitePhysical systemLibrary (computing)Functional (mathematics)Latent heatModule (mathematics)PlastikkarteExtension (kinesiology)Category of beingStandard deviationWindowUtility softwareComputer animation
15:26
BuildingParallel portIntegrated development environmentModule (mathematics)Physical systemModule (mathematics)Process (computing)2 (number)Staff (military)CodeOffice suiteEmailData miningElectronic mailing listAsynchronous Transfer ModeBootstrap aggregatingArrow of timeSoftware crackingMultiplication signBitOpen setBuildingThread (computing)RobotVirtual machineCoprocessorComputer animation
19:06
Module (mathematics)BuildingHydraulic jumpPhysical systemParallel portIntegrated development environmentModul <Datentyp>GezeitenkraftPrincipal idealArmMathematicsOrder (biology)Interface (computing)Module (mathematics)BuildingSoftware developerComputer animation
21:20
Module (mathematics)Parallel portBuildingIntegrated development environmentPhysical systemProcess (computing)Endliche ModelltheorieModule (mathematics)BuildingIntegrated development environmentComputer animation
23:46
Electric currentPhysical systemIntegrated development environmentScripting languageBuildingDisintegrationBuildingPhysical systemProcess (computing)Integrated development environmentJava appletScripting languageLatent heatDistribution (mathematics)Module (mathematics)Slide ruleConfiguration spaceMixture modelOcean currentOffice suiteWeightPerspective (visual)Computer configurationMereologyEmailMoment (mathematics)Metropolitan area networkCodeSign (mathematics)Computer animation
29:07
FacebookPoint cloudOpen source
Transcript: English(auto-generated)
00:05
Time to start, yeah? Yeah, welcome to our developers' room for office systems. I don't know the true name, but... Yeah, maybe it's Open Document Editors.
00:21
Yeah, Open Document Editors, yeah? So, and I will have a small talk about building an open office, our build system, how it works, and so on. The reason for it is I get asked on the recruitment channels often,
00:42
how do I build open, or I want to contribute, and then I say, okay, build open office, and then I don't get an answer. So I hope that with this talk, I can help people a little bit more to get over this hurdle.
01:03
Yeah. So my name is Peter, and I'm usually using the nickname Petco. I joined in 2016 the Open Office project from Apache, and I was the chairman 2018 and 2019.
01:23
Yeah, that's what you need to know about me and what I do in the project or what I did so far in the project. Yeah. Okay, like I said, the goal of this talk, it's, I won't give you an overview.
01:41
I do not want to go really deep inside depth. I will not go so much into the differences between Windows, Mac. So it's more about principles, what you need to know, and the understanding. Yeah? And I will talk a little bit
02:02
what I picked up, where we were going with the build system, how it's changing. We work on this from time to time, and, yeah. So if anyone is interested in building open office,
02:25
we have written two guides, one with general information, where we explain a lot what and how these options is, what does it mean, and so on, central stem things. And if you have an OS
02:41
and you want specifically built on for one, for your system, then we have an OS page where you, on detail, get explained from Windows or Linux, even break down among certain distributions. I can only recommend,
03:01
if you download the presentation, use the links. The presentation is only in helper and we're giving you some guidance, you know? So when we build open office, we have, let's say, different phases, you know?
03:21
Where we built, which you have to follow in order to get a successful build. First, you set up your environment. That means you prepare, you have to install the dependencies that the building environment needs to get working.
03:41
Then we have to do a configure that the build system knows what do you want to build. The third is bootstrapping. Then we pull in the dependencies that we need for building the code.
04:02
Even if you pick the choice that you go on system libraries, where you have probably to do some adjustments, but our build environment is set up so it's generally working.
04:23
So you have, so we pull in all dependencies and we provide all the dependencies from our resources, ourselves. So if you build open office plain,
04:41
then you will provide all the dependencies in the right versions that there is. If you want to use the system libraries, you will have to tweak around, probably. And, yeah, and the last thing is to build open office, you know? Building commands and so on.
05:04
So build environment needs a working PAL version and for the Java stuff, and Java, of course, we have Gperf for, Google Perf for performance test.
05:22
You need this UNU WinRag DLL for building. At least I did not know how to circumvent this. Did you? Yeah. Okay, I get all those complaints from the,
05:43
but maybe if you say without SDK, then it will not, you will not be a request to set it up. If you build on Windows, you will need additional tools,
06:00
the Mozilla build tool, for example, and the Microsoft SDK. On Mac, you will also need some special, the SDK firmware for Mac. I'm not sure which version thought. In doubt, if you have questions when you're trying it, ask on the dev there. We help you look it up.
06:20
You get the answers you need, you know? So if you have installed everything and you're prepared to build, then you can go to the next level and you have to know a little bit how, where we store some stuff.
06:43
So in the X libraries and in the X sources, we have, we will store our dependencies, yeah? So the, the instset.oo native folder
07:02
is where we build OpenOffice. This is the home folder of the build. There we will start the build scripts from and it will always also provide a default to build in this folder, yeah? And there's a test,
07:21
where the test framework is. I cannot, you know, I just took this test stuff from the website so I don't know exactly how this stuff works. Yeah, then we have set up our environment.
07:41
We know where the dependencies goes and so on. And then we want to configure our system, yeah? So we use auto-config, auto-conf, and then configure for doing this, like in most,
08:00
like in most Linux or open source projects. But for the starters, you need to, to say some, some, you have to switch some, some switches, you have to give that. And my recommendation is you can go on the C Wiki
08:22
where we have layout with some examples where you can start or you can use the build bots. We have some build bots that run every day and you can start with their configuration and with their links and so on. We will look then what's,
08:46
we will take a short look what the important switch is and there are some more and you can have the look. For example, this is most, the most central one.
09:02
We have, we have loranda-autoconf, then you start with .configure, then you have the first switch you will always need. With dmake, we still use the old dmake system in parts.
09:20
We are in the migration, we are running away from dmake to the remake and if the migration is done as far as I know, it will use automatically. So, but we still need to use this. When you, when you pass the URL,
09:40
then you can, then it will, I don't know, I think in the bootstrap, it will download dmake, it will be built automatically and you have not, you need not to do any extra stuff. The EPM is the second dependency
10:05
for the build environment which we need. You can also install this separately and have it, and just pass the URL where it can be directly found.
10:20
Here, it will be downloaded and built on the EPM we need for packaging. So, if you build depth files, RPMs and so on, this will be done by this package. Then, with LAN, you define which languages you want.
10:42
These languages are copied from the buildbots. So, you have a short choice. If you do it for yourself, then you will, you will maybe reduce it or, so.
11:01
And then you have some switches like wiki publisher, wearables, category B, enable OpenGL, enable DBOS. Without JUnit and enable bundled directions, these are still a bit what will be built, how it will be built.
11:21
For example, enable category B. This is a license issue. If you, or not issue, but it's a licensing stuff. So, OpenOffice is built quite modular, and the core, it's an APL2,
11:43
but which is from Apache perspective, a category R license, also other free license like the,
12:01
no, I forgot. Like other similar license to the Apache license, there will be also category R and other licenses like the Mozilla license is counted like category B. So, if a module of a third-party extension
12:23
is made in, is published with Mozilla, this is the Mozilla license. For example, you need this enable category B so it will be built with the build. You're going to do. Enable OpenGL will enable the OpenGL stuff.
12:47
On Windows, you have also the option to use DirectX if you have the SD card available for it.
13:01
DBOS is something Linux specific and so on. I recommend to use this vendor and then just write something so it's not confused as an official build. If you do it as an official build, you will probably get into some issues
13:21
if the PMC looks at it. If you build for yourself, you can give with the option or with the switch, with package formats, you can give the, you can configure what packages it will be installed,
13:41
if it's ABRBM, RPM, DEB or whatever. If you use installed, it will be, it will be roll out in the build folder and you can directly use it for your tests. The last two are enabled debug util and enable symbols
14:02
that will help you in the debugging. You can then attach it to GDB or you get a search error if you open up the Windows. The last thing is you can deactivate modules
14:22
like without JUnit will deactivate the JUnit testing. Without STLport, you will, you will disable a specific module
14:40
that this STLport especially will, is about some basic standard library functionality and it's, and this one is, I put it in there because we usually build without STLport, the modules,
15:03
so maybe for starters, you will want to do this also or you want to use this for, you want to use this option. If you use this option as it is given here, at least on Linux, it will build quite nicely
15:21
and you will get a debug-able build of OpenOffice. So when we have configured our system, we do a bootstrap in between. The bootstrap is only downloading the dependencies we want to build. The command for building OpenOffice
15:41
is build all p8, for example, minus p8, slash slash, or dash dash, and dash p8. For example, and what does it mean? It means we want to build everything
16:05
with eight parallel modules built and with eight threads per module. So, yeah, this is pretty much,
16:20
with p8 and p8, we have rather bad experience. I think it's maybe better to use something like p2 and have here something p8, depending on your processors. You have to experiment with it a little bit
16:41
because OpenOffice still needs a lot of time. Build bots need something like, I don't know, six to 20 hours, yeah? Was it, right, something like that? Build is quick.
17:01
Build is quick, okay. I need something around an hour, maybe, on my machine. Yeah, so what does it mean with this p8? I have some, maybe some graphics,
17:22
some small graphics to make it more clear, maybe. We look at the first pm. We have our modules, yeah? If we use p1, it will build one module after another. If we have build with p2, it will start with the first module and then depending on the dependency setup,
17:41
it will start to go ready for two or more stuff. It will open up more parallel buildings, yeah? So if you have too much parallel modules to be built,
18:02
we have some dependency lacks, I think. You will maybe find out that we want to build module three but it has a dependency to module four and module four is not built and so the build will stop with an error.
18:22
Best is if you come across these things, ask about on the dev mailing list and we will look into it and we will help to fix it. If we go to the p, if you go to the second switch,
18:41
if you build one module, then we open up more one-on-one threads and we build this code stuff in parallel. You can also think this will be passed, the second one will be passed to dmake and gmake
19:01
so they work in parallel and they work faster. If we do our builds and it stops and we fix something, then it breaks and we fix it and we want to continue there or we have to, we clean something up.
19:23
Then we don't want to start over. So we can continue where we have stopped or in the module where we did our changes, we can set up at this place and restart the build
19:42
and there's two ways you can do the build. The first one is we talk of compatible builds and we talk of incompatible builds. So for example, we have module one, we have module two,
20:02
we have module three, we build all three or we build, we started to build all three and then we do a change in module two. So then we want to set up again on module two and the wise thing is to build then again module three.
20:21
If we build module three or we set, we would give then the build command build from module two. And the build will then know, okay, I want to build also module three.
20:41
I will go in depth just to have the principle. And in compatible builds, we already know module three will not be affected. We are sure as a developer that this module, that the change in module two will not affect module three or anything that comes after it.
21:02
So we only build module two, which will be much quicker. But well, if there's something changing in the interfaces or something, then you have an issue that might be difficult to debug.
21:22
So the recommendation is definitely, if you have no idea whatsoever, then do incompatible builds, build everything from the place where you quit and then you're safe.
21:41
The build command is done in the instset oo-native. Then the build environment will always know that you want to continue after the module you have changed is done. It will automatically know which dependencies after that
22:03
has to be rebuilt. For that, we need to clean the build that has already been done. This is done with the command build from module two minus minus prepare, yeah?
22:23
But since we also use gmake and gmake will not respond, will not be cleaned with the minus minus prepare, you need also to set up build minus minus from module two
22:43
and then minus job and then make clean, make clean debug equals T minus ignore. This will be safe for you. Then you have really cleaned your build environment and you can really start over with build from module two, yeah?
23:05
This is something you have to keep in mind for this and quick look on the... So and if you do compatible builds,
23:21
you go into the module name and just clean in the module, yeah? If it's a module that is based on gmake, you can just pass a make clean and then you're done and then you can start with build from module two.
23:47
Okay. Last slide. As we have seen, the current build environment is at the center of its build, it's a Perl.
24:01
So the build command is a Perl script. We use a mixture of dmake and gmake. I think it's, I don't know, I'm not very sure, but I think around 60 to 80% of the modules are already on gmake
24:21
and we use and for Java stuff or Java code. In the future, there's some, there's quite an agreement that we will move away from the build Perl script. The preference is to only use the GNU make.
24:45
So you have the standard make, make install and stuff. We will continue to use and. Our GNU make configuration is set up in the way if there is Java in the module,
25:01
then make will automatically fire up and build Java. So this is for building perspective, it's the end is really on the floor,
25:23
but maybe if the GNU make, if the build Pl will not replace the, if you cannot replace build Pl with the GNU make, then maybe end will become an option. There's also the wish to use Python or Scon,
25:44
but it's not so preferred. So let's put it like this. And yeah, in future, we will only use gmake, we will drop dmake if we manage to recreate the last modules.
26:05
To gmake, we will continue to use end. And this is my personal wish, that we someday can use an EDE, I don't know, Eclipse NetBeans or something to develop OpenOffice further.
26:27
So yeah, thank you for your attention and for this quick run through the OpenOffice build system and environment.
26:43
We have, I think, one minute for questions. Yes? So currently, there's, I think, no specific support
27:07
for specific distributions. I don't know. You do Debian specific builds, right?
27:43
Oh, you mean the signing the build code? In the current builds or current releases,
28:01
we did not do this. We have a process in place or we have people who are looked into it and with the next release, we will start to sign our builds for Mac. And I'm not sure, we try for Windows, yeah?
28:21
But this is, I think, at the moment, a manual process and we have to make our experience until, and we will see if we get that, how we can get the process then smaller. So we start with a separate manual process and then go to, and then see where it takes us.
28:42
I hope it answered your question. Anything more? Okay, thank you for your audience.