[haiku-development] Re: [GSOC2017] Looking for project details
- From: Kacper Kasper <kacperkasper@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 30 Jan 2017 18:00:49 +0100
2017-01-30 15:36 GMT+01:00 Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>:
30 janvier 2017 15:12 "YongHao Hu" <christopherwuy@xxxxxxxxx> a écrit:
[...]
I would like to choose Porting LibreOffice, Add Haiku support to Allegro 5.0
and Calendar
application, as they seems suitable for my experience. Any new projects
advice is appreciated.
We are still working on our project ideas. I will leave the respective
mentors for each project give some more information.
[...]
As you noticed, our ideas are rather short and not very detailed. We expect
the student to do some research on the project ideas. For example, if you
plan to dig into porting LibreOffice, a good start would be (after getting
Haiku up and running) to get the LibreOffice sources with the early work done
here: https://github.com/kapix/libreoffice_core and see if you can get it to ;
compile.
Additional notes:
1. You will definitely need to get familiar with haikuporter [1].
Packages needed to build LibreOffice are not in our main repo so you
will need to build them yourself from haikuports [2].
I can create a repo with prebuilt packages to save you some time, but
basic haikuporter knowledge is necessary nonetheless.
2. You need to decide on which arch you are going to work. This can be
either x86 or x86_64. Both have pros and cons.
x86:
+ required libraries are ported and tested to work with LO's build system
+ should build out-of-the-box (from the repo mentioned above [3])
- 32-bit OS has memory limitations and using Debugger is cumbersome -
debug symbols are so big that it crashes during loading, so you either
need to strip symbols from all the libraries you are not interested
in, or use printf to debug
x86_64:
+ memory should not be a problem for debugging, however I'd recommend
to consider this only if you have lots of RAM (I'd say 16 GB is
minimum)
? only some libraries are tested to work and build with x86_64 (most
should build without problems, but some patching may be needed)
? there is no support for 64-bit Haiku in the repo [3], but
considering that for 32-bit copying Linux ones was enough, this may
not be a big issue
Official x86_gcc2 hybrid is not tested, and I wouldn't recommend using
it right now. The plan is to work on gcc2hybrid support when
everything is tested and working on x86.
3. You need to have at least 30 GB of free disk space (my build takes
15 GB, I imagine that 64-bit build would be even bigger if you decide
to pursue that).
4. You can set up Haiku in a VM to build LO, but I would recommend
using it on real hardware. VM's are really slow, and on hardware LO
takes at least 6 hours to build.
5. Some unit tests crash [4]. To avoid stopping the build process I
recommend specifying default action the debug_server should take for
cppunittester [5].
For you convenience: commands that should build all dependencies in
correct order [6].
If you have further questions feel free to ask.
- Kacper
[1]
https://github.com/haikuports/haikuports/wiki
[2]
https://github.com/haikuports/haikuports/issues/108
[3]
https://github.com/kapix/libreoffice_core
[4]
https://dev.haiku-os.org/ticket/13159
[5]
http://cgit.haiku-os.org/haiku/commit/?id=hrev46547
[6]
https://gist.github.com/KapiX/4d2c40a12e2079b8ca1cac6e5f3374fb
Other related posts:
