Hi, jaroslaw,

I am not sure of the import of that bug mentioned to my situation. Unless advised otherwise I intend to proceed as below.

I seem to have all the dependencies, I suppose these were installed following through the 'Debian specific instructions'. Checking any of them shows them at required or later version.

I have made the directory structure as per Calligra recommendatons, so on to the next step - get the tar.gz as the subject says, or other method.

There are some alternatives. Since this is not the machine on which I would regularly do test builds, but since we would want to be able to update easily every so often, and since I would prefer the stable version as it is a production machine, then the path would seem to be:

1. Get the Development Version using Option 2 - ie download a repository tarball from the kde link given, and unpack it.

2. Then, using the procedure outlined in Latest Stable Version using Option 2 should allow me to swop horses in mid stream to the Stable Version ... OR is this specifically only applicable if you have obtained the Development Version direct from git (Development Version using Option 1 in the first place? This is not clear to me.

Can you clarify this before I maybe go up a one-way street.

I see at this stage that I am going to end up with the whole Calligra suite. Only really want Kexi as am locked into Open Office, but, hey, plenty of room.

Regards
Ian

I recommend the Development Version's repository tarball, new features go into this version which eventually become 2.9. Latest stable only receive fixes that come to 2.8.1, 2.8.2, etc.

Development Version (in git naming it's called 'master' branch) is assumed to only contain tested, carefully written code, this is a decission made in Calligra one day, before master branch could have even broken compilation.

And using repository tarball gives easy updates usign the a single command of the git tool.

Jaroslaw,

Report-back:

I downloaded the tarball calligra-latest from the repository into my folder 'Downloads'. (my monthly data budget is blown twice over and Calligra does not tell you what this 'weighs' - it being the heaviest option offered!

I unpacked it into 'Downloads' (using the menu option to extract tars in midnightcommander for this since no specific tar line is given by Calligra Building) and I now have a subdirectory 'calligra' with all files in.

Running ./initrepo.sh seemed to do nothing, so looking inside this I decided was supposed to have 'git' which I then installed. The script then produced the following output: I suppose having 'git' is implied in Calligra Building, but not mentioned for the tarball option which it should be as I assumed that I was escaping git.

inksi@athene ~/Downloads/calligra $ ./initrepo.sh
Checking out files: 100% (21812/21812), done.
HEAD is now at 2Picking 'kde4libs' as source package instead of 'kdelibs5'3c430a BUG:331805 Do not let the selection grow bigger than the image on invert
inksi@athene ~/Downloads/calligra $

is there something I should know? I will check the bug later.

Looking more closely some of the dependancy issues as my next step. In order of listing in Calligra Building

I am not sure about my version of Qt4. libqt4-dev appears to be 4.4.8.1 and I am not sure how to update this
Not something that an apt-get update is going to fix it seems. Is there a ppa?

kdelibs is 4.4.8 so fine
kdebase s 4.4.8 so fine
cmake is 2.8.7 so fine

lcms does not appear on my Mint (unless is is liblcms1-dev in which case it is version 1-something.
libpng-dev only appears as libpng12-dev on Mint

not sure what to do there

At this stage it is mentioned that dependencies can be installed using
$ apt-get build-dep kdelibs5

... but apt-get says:.
'Picking 'kde4libs' as source package instead of 'kdelibs5' '

not sure what to do there

libeigen is 2.0.17 so fine
libexiv2 0.22-2 so fine
libboost-dev I appear to have so fine
libsqlite3 and dev 3.7.9.2 so fine
libicu-dev and libivu48 are what i have as 4.8.1.1 so fine except nothing called 'icu' on its own as implied by Calligra Building

Time to call a halt until above issues resolved.

regards
Ian

inksi wrote:[...]
HEAD is now at 2Picking 'kde4libs' as source package instead of 'kdelibs5'3c430a BUG:331805 Do not let the selection grow bigger than the image on invert
inksi@athene ~/Downloads/calligra $

This is OK, the "BUG:..." is a part of a commit message (change) that is displayed. It's a bugfix.

inksi wrote:I am not sure about my version of Qt4. libqt4-dev appears to be 4.4.8.1 and I am not sure how to update this

type:
qmake --version

Mine is "Using Qt version 4.8.4"

Good that you're tracking the dependencies. Some of them are not needed for Kexi but nevermind, this is usually a one-time task.

inksi wrote:lcms does not appear on my Mint (unless is is liblcms1-dev in which case it is version 1-something.
libpng-dev only appears as libpng12-dev on Mint

Both are ok, if you have libpng14, that would be good. Please try to ask on Mint forums or try to find power users of Mint on the KDE forums.

inksi wrote:At this stage it is mentioned that dependencies can be installed using
$ apt-get build-dep kdelibs5

... but apt-get says:.
'Picking 'kde4libs' as source package instead of 'kdelibs5' '

Does it install dependent packages? If so that would be ok.

Now, the ultimate way to know if the dependencies are met is to configure the build. If you build all Calligra apps (longer, more space of course), type:

mkdir -p $HOME/kde4/build/calligra
mkdir -p $HOME/kde4/inst
cd $HOME/kde4/build/calligra

cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=DebugFull

If you want only Kexi, I actually recommend building Kexi+Sheets (as they use some common stuff that's useful), instead of the last above line, type:

cmake -DPRODUCTSET=KEXI+SHEETS -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=DebugFull

Please share the result of this configure stage (if you have a lot to paste you can paste to http://paste.kde.org/ and share a link).
Many dependencies are optional so you can add them later, re-run configure/rebuild.

After you're ok with the configure stage, you just type:

make

(to build, -j5 option speeds it up as the documentation says http://community.kde.org/Calligra/Build ... d_Calligra)

and

make install

(to install)

Good morning, Jaroslaw,

Issue 1.

$ apt-get build-dep kdelibs5

... but apt-get says:.
'Picking 'kde4libs' as source package instead of 'kdelibs5' '
Does it install dependent packages? If so that would be ok.

So I went with this. 28 packages installed. See output on
http://goo.gl/mz8bNK

Issue 2:

cmake -DPRODUCTSET=KEXI+SHEETS -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=DebugFull

Please share the result of this configure stage (if you have a lot to paste you can paste to http://paste.kde.org/ and share a link).

My Qt4 version is 4.8.1 - I will assume that since Ubuntu/Mint is a major version that it has been patched and will add -DIHAVEPATCHEDQT=true to the cmake configuration line given above.

... Went ok. I note that having extracted the tarball using the simple one-size-fits-all command built into midnightcommander that of course everything was in a subdirectory of my Downloads directory. I copied it to ~/kde4/src/calligra as was needed. Calligra Building could show the correct untar command there since everyone just downloads into their favourite download directory or to the Desktop

output on
http://paste.kde.org/pemn15tpf

Issue 3

(to build, -j5 option speeds it up as the documentation says http://community.kde.org/Calligra/Build ... d_Calligra)

j3 for me as my amd chip is dual-core
I would also like the add the option in for a 64-bit build. Can you please advise?

This is going well, Jaroslaw!Looking forward to the next step.

PS. after original post of the above:

-- checking for module 'libwps-0.2'
-- package 'libwps-0.2' not found
-- checking for module 'libvisio-0.0'
-- package 'libvisio-0.0' not found
-- checking for module 'libetonyek-0.0'
-- package 'libetonyek-0.0' not found

libwps-0.2-2 is installed according to my package manager
libvisio-0.0-0 is available if needed, but not installed.
libetonyek is unfound on the package manager

inksi


regards
inksi

inksi wrote:j3 for me as my amd chip is dual-core
I would also like the add the option in for a 64-bit build. Can you please advise?

OK!

-j3 looks ok for you.

64 bit build is a default on your 64bit OS, if I understand correctly.

So if you run make/make install, then you'd have kexi available already

A simple hint:
"make install" contains "make" step already. So if some of the source code has been changed, typing "make -j3 install" does the job. And the 'cmake' configuration step will be automatically re-run if needed.

regards

Jaroslaw. hi,

Amazing!

Build took 30 mins. a m a z i n g

I was not sure from reading your post so I did $ make -j3 and $ make install seperately, but could I have just done the latter and all would have been done at one pass?

I have to get this onto the menu somehow. Will work on that.

My aim is to get this machine set up with some other stuff and then move it into production. Then I will see about a build on another production machine, and then look at building on the development laptop and see to regular builds as offered.

A million thanks for all the help and support. I will be back soon.

inksi.

Cool. Next builds, unless you build from scratch would take minutes, e.g. in case when you grab a fix from me.

To be clear, the following sets of commands are equivalent:

Code: Select all

make
make install


Code: Select all

make install


(replace make with make -j3 in your case)

PS: if you want to install quickly without building anything, type:

Code: Select all

make install/fast


Jaroslaw, hi.

There are some glitches here, but maybe they be used to start new threads. I will list them here for the record. Tell me if they should be 'rethreaded'

1. We installed KEXI+SHEETS. While kexi runs, sheets does not. Since $ kexi is the correct invocation, I assume that $ sheets is too.

Code: Select all

inksi@athene ~ $ sheets
sheets: command not found

2. The behaviour when editing text in existing records is odd.

(jstaniek: moved to viewtopic.php?f=221&t=120309)

regards
inksi
ps. I am using postgresql if this has any bearing,

inksi wrote:1. We installed KEXI+SHEETS. While kexi runs, sheets does not. Since $ kexi is the correct invocation, I assume that $ sheets is too.

Code: Select all

inksi@athene ~ $ sheets
sheets: command not found

Use

Code: Select all

~ $ calligrasheets

- by decision of the Team, the calligra prefix is used for apps that would be otherwise too common words; 'sheets' looks like one of them. 'kexi' is not.

inksi wrote:2. The behaviour when editing text in existing records is odd.

Good topics but please move them to another thread. Thanks.