Getting Underway: First steps

[Harshi Mistry]

Sure. I am on it, I will do it before Sunday. I was kind of stuck in
figuring out cmake way of doing things.
So compiling cpp file with JNI code needs JNI headers to be included and
Java binaries to be linked. I do like this when running my standalone code:

gcc -I/usr/lib64/jvm/java-7-openjdk/include/
-I/usr/lib64/jvm/java-7-openjdk/include/linux/ -L/usr/bin/java
-L/usr/lib64/jvm/java-7-openjdk/jre/lib/amd64/server/ javaFromCpp.cpp -ljvm

Also running resultant executable requires LD_LIBRARY_PATH to be set. I was
figuring out how to do these things in cmake.
As far as I understand I need to do find_package(JNI) in top CMakeLists.txt
file in src/calligra directory. Then do following in CMakeLists.txt in odb
directory.

include_directories(${JNI_INCLUDE_DIRS})
target_link_libraries (helloworld ${JNI_LIBRARIES})

Though I am not yet sure how to set LD_LIBRARY_PATH in cmake.
Further, I need to install a Java library called hsqldb.jar (used for jdbc
operations on odb files) using cmake and get its absolute path in my cpp
code. I don't understand how to do it. Please help me in this.

Thanks,
Harshita



On 6 June 2014 00:36, Jaroslaw Staniek <staniek at kde.org> wrote:

> On 5 June 2014 09:17, Jaroslaw Staniek <staniek at kde.org> wrote:
> > Hello,
> > How do you do? I'd like to receive:
> > - status (achievements, issues, close todos) every week on Wednesdays
> > morning CET
> > - updated http://community.kde.org/GSoC/2014/StatusReports
> >
>
> ^^ http://community.kde.org/GSoC/2014/StatusReports is expected by KDE
> before Sunday
> Please also take time and blog on your blog or on blogs.kde.org
>
> > Thanks!
> >
> > ---------- Forwarded message ----------
> > From: Valorie Zimmerman <valorie.zimmerman at gmail.com>
> > Date: 5 June 2014 08:50
> > Subject: Getting Underway: First steps
> > To: KDE-soc <kde-soc at kde.org>
> >
> >
> > Greetings again, GSoC students.
> >
> > At this point, we hope that you and your mentor are very well
> > acquainted, and have worked out a routine for regular communication.
> >
> > We hope the code base you are working with is now familiar to you, as
> > are all the tools and documentation you need.
> >
> > We hope all of you have your KDE developer account set up and working,
> > so that your code can be seen by your team members (including
> > Reviewboard).
> >
> > We hope that your blog is set up somewhere, and that you have added it
> > to PlanetKDE [Pro-tip: "Add your blog" link right up top].
> >
> > And we hope you have blogged at least once, introducing yourself and
> > your project to the KDE community as a whole. If not, do it now,
> > please. Once you have published blog posts, please list on the Status
> > Reports wiki page, and keep that up-to-date.[1]
> >
> > Please write back if you are having any problems with any of the above
> > steps, or ask your mentor.
> >
> > All the best,
> >
> > Your loving GSoC admins
> >
> > 1. http://community.kde.org/GSoC/2014/StatusReports
> > _______________________________________________
> > Kde-soc mailing list
> > Kde-soc at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-soc
> >
> >
> > --
> > regards / pozdrawiam, Jaroslaw Staniek
> >  Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org
> >  Qt for Tizen | http://qt-project.org/wiki/Tizen
> >  Qt Certified Specialist | http://www.linkedin.com/in/jstaniek
>
>
>
> --
> regards / pozdrawiam, Jaroslaw Staniek
>  Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org
>  Qt for Tizen | http://qt-project.org/wiki/Tizen
>  Qt Certified Specialist | http://www.linkedin.com/in/jstaniek
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/calligra-devel/attachments/20140606/403a7c0b/attachment.htm>