Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi, Thank you Jan,
i registered on gerrit platform. 
I prefer, if is possible, to see your Java problems for try to create my first patch, is it 
possible to use an IDE, like Eclipse, to edit the java code in easy way?

Reagards,
Massimiliano.



Il giorno 08 nov 2015, alle ore 18:44, jan iversen <jancasacondor@gmail.com> ha scritto:

Congratulations !!! that is actually the most difficult step.

Now when both of you have time it would be good for you to register on the mailing list:
http://nabble.documentfoundation.org/ <http://nabble.documentfoundation.org/>

This is where we all "talk" together.

Sooner or later you will also need to register in Gerrit:
https://wiki.documentfoundation.org/Development/gerrit 
<https://wiki.documentfoundation.org/Development/gerrit>

we use gerrit to submit and review patches, this is not mandatory for the first couple
of patches, I can do it for you, but it is something you need to get used to.

Finally here is a link to "easy hacks":
https://wiki.documentfoundation.org/Development/Easy_Hacks 
<https://wiki.documentfoundation.org/Development/Easy_Hacks>

Which is problems that are easy to solve, and are there for new people. I do however
also have a set of problems in java, which are open. Most of the java problems are
simple problems, but typically in multiple files. So whatever you prefer I am there
to help you.

Sukant@ Do not be stressed getting your environment up and running, there are plenty
of work waiting.

have a nice day.
rgds
jan i.



On 8 November 2015 at 17:06, Massimiliano Fiori <massimiliano.fiori@aol.it 
<mailto:massimiliano.fiori@aol.it>> wrote:
Hi, 
Yes i hadn't set CCACHE correctly. Now i have builded lode successfully.
Now what is my next step to create a patch for the project?

Thanks a lot, 
Massimiliano. 


Il giorno 07 nov 2015, alle ore 21:11, jan iversen <jancasacondor@gmail.com 
<mailto:jancasacondor@gmail.com>> ha scritto:

Hi.

I researched it a bit more, it seems that the clang compiler is not well supported by lode.

Have a look at:
https://wiki.documentfoundation.org/Development/Building_LibreOffice_with_Clang#Setup 
<https://wiki.documentfoundation.org/Development/Building_LibreOffice_with_Clang#Setup>

the developer specialists told me, that your problem is typically caused because you
do not have
CCACHE_CPP2=1

Have fun
rgds
jan i.


On 7 November 2015 at 19:59, jan iversen <jancasacondor@gmail.com 
<mailto:jancasacondor@gmail.com>> wrote:
Hi.

It seems to me you missed the "autogen.sh" statement.

you ran "setup --dev" and checked out the source.

then you need to do:

cd dev/core
./autogen.sh

and after that (if it does not give you any errors)
../../opt/bin/make 2>&1 | tee build.log

you can run ./autogen.sh anytime, so please run it again, and make sure it does not report 
errors.

Secondly it is important that you use "../../opt/bin/make" and NOT the make standard in OSX.

Finally you need to deactivate your virus checker (this is not the problem right now).

Please try my suggestion, and then let me have the whole build.log

have fun
jan i.

On 7 November 2015 at 14:54, Massimiliano Fiori <massimiliano.fiori@aol.it 
<mailto:massimiliano.fiori@aol.it>> wrote:
Hi Sakunt,
nice to meet you!

I try to build lode and i have this error after '../../opt/bin/make 2>&1 | tee build.log’ 
command :

[build C  ] cppuhelper/source/findsofficepath.c
clang: error: argument unused during compilation: '-I 
/Users/Bayway/Developer/lode/dev/core/cppuhelper/source/'
clang: error: argument unused during compilation: '-I 
/Users/Bayway/Developer/lode/dev/core/include'
clang: error: argument unused during compilation: '-I 
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/include'
clang: error: argument unused during compilation: '-I 
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/include/darwin'
clang: error: argument unused during compilation: '-I 
/Users/Bayway/Developer/lode/dev/core/config_host'
/Users/Bayway/Developer/lode/dev/core/solenv/gbuild/LinkTarget.mk:138: recipe for target 
'/Users/Bayway/Developer/lode/dev/core/workdir/CObject/cppuhelper/source/findsofficepath.o' 
failed
make[1]: *** 
[/Users/Bayway/Developer/lode/dev/core/workdir/CObject/cppuhelper/source/findsofficepath.o] 
Error 1
Makefile:247: recipe for target 'build' failed
make: *** [build] Error 2

My OS: Mac OSX 10.11.2

Thanks for all, 
Massimiliano


Il giorno 07 nov 2015, alle ore 09:21, jan iversen <jancasacondor@gmail.com 
<mailto:jancasacondor@gmail.com>> ha scritto:

Hi Massimiliano.

Welcome.

Sakunt meet Massimiliano
Massimiliano meet Sakunt.

As I wrote to Sakunt, I am would like to help you get started and help you get the first 
patches submitted.

The first 3-4 patches are always the most difficult, because you need to get the environment 
setup, write
commit messagees correctly etc. but that is exactly the point where we can work together.

Let us make a little "starter" and before you know it, you will be part of our communty.

Please look around in the wiki, and get started with lode.

Feel free to mail me directly (this mail is cc to the mailing list, so the other community 
member know what we
are doing) if you have questions or comments.

rgds
jan i.


On 7 November 2015 at 02:06, Massimiliano Fiori <massimiliano.fiori@aol.it 
<mailto:massimiliano.fiori@aol.it>> wrote:
Hi,
my name si Massimiliano and I have read your e-mail on list I would to help LibreOffice Project 
too and i would to take developer certificate in future, I've already worked on some easy hack, 
I can help in anyway?
I have more experience in java but I also know C and Python

Thanks a lot,
Regards

Massimiliano








Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.