Sigil-0.9.3 Released

[patrik]

I believe I have, but maybe I missed something?

3.4.0-0ubuntu2 amd64 header files and a static library for Python (default)
ii libpython3.4-dev:amd64 3.4.3-1ubuntu1~14.04.3 amd64 Header files and a static library for Python (v3.4)
ii python3-dev 3.4.0-0ubuntu2 amd64 header files and a static library for Python (default)
ii python3.4-dev 3.4.3-1ubuntu1~14.04.3 amd64 Header files and a static library for Python (v3.4)

[patrik]

Ah, I pointed to /usr/lib/python3.4 instead of /usr/lib/python3.4m.

Make now goes all the way to 100%, but then I get:

...
[100%] Building CXX object src/CMakeFiles/sigil.dir/sigil_automoc.cpp.o
make[2]: *** No rule to make target `/usr/lib/python3.4m', needed by `bin/sigil'. Stop.
make[1]: *** [src/CMakeFiles/sigil.dir/all] Error 2
make: *** [all] Error 2

[DiapDealer]

Also note that your value for -DPYTHON_LIBRARY is not valid. I looks like you've supplied a directory instead of the path to the actual library file. You might also need to supply the path to your Python.h file (as Kevin noted) with -DPYTHON_INCLUDE.

I'm a little surprised you need specify those paths at all, quite frankly. You seem to be using the standard system Python 3.4.3 that Mint 17.2 supplies, so there should be no need to use any of the -DPYTHON cmake overrides. If you have all the necessary python34 packages installed, cmake should find them with no problem.

Make sure you have the python34-dev package installed (as Kevin mentioned), and in addition, make sure you have the libpython3.4 and libpython3.4-dev packages installed (as per the Building on Linux documentation). Then try running the cmake command without all the -DPYTHON overrides (you may need to wipe out your build directory and start over, though).

[DiapDealer]

Originally Posted by patrik

I believe I have, but maybe I missed something?

3.4.0-0ubuntu2 amd64 header files and a static library for Python (default)
ii libpython3.4-dev:amd64 3.4.3-1ubuntu1~14.04.3 amd64 Header files and a static library for Python (v3.4)
ii python3-dev 3.4.0-0ubuntu2 amd64 header files and a static library for Python (default)
ii python3.4-dev 3.4.3-1ubuntu1~14.04.3 amd64 Header files and a static library for Python (v3.4)

As I suspected in my previous post, you're missing the libpython34 package. Did you check out the Building on Linux document? These dependencies are all mentioned there.

[patrik]

Originally Posted by DiapDealer

Also note that your value for -DPYTHON_LIBRARY is not valid. I looks like you've supplied a directory instead of the path to the actual library file. You might also need to supply the path to your Python.h file (as Kevin noted) with -DPYTHON_INCLUDE.

I'm a little surprised you need specify those paths at all, quite frankly. You seem to be using the standard system Python 3.4.3 that Mint 17.2 supplies, so there should be no need to use any of the -DPYTHON cmake overrides. If you have all the necessary python34 packages installed, cmake should find them with no problem.

Make sure you have the python34-dev package installed (as Kevin mentioned), and in addition, make sure you have the libpython3.4 and libpython3.4-dev packages installed (as per the Building on Linux documentation). Then try running the cmake command without all the -DPYTHON overrides (you may need to wipe out your build directory and start over, though).

I started out doing exactly that, but then I got:

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
PYTHON_LIBRARY (ADVANCED)
linked by target "sigil" in directory /home/patrik/Downloads/Sigil/Sigil-0.9.3_src/src

-- Configuring incomplete, errors occurred!

That's when I started to add the paths.

[patrik]

Originally Posted by DiapDealer

As I suspected in my previous post, you're missing the libpython34 package. Did you check out the Building on Linux document? These dependencies are all mentioned there.

Yes, I followed the document.

I believe I do have python34 and -dev installed.
Just to be sure I tried to install it again, and the system said it was already installed.

edit:
The only thing that wasn't installed is python3.4-six which couldn't be found. (but python3-six is installed)

[DiapDealer]

If you installed any python packages after that initial cmake command, you may need to delete your build directory before running the cmake command again.

Mint 17.2 with the system python 3.4.3 is the exact same system I build on.

Originally Posted by patrik

Ah, I pointed to /usr/lib/python3.4 instead of /usr/lib/python3.4m.

That's still not a valid library file. If you must specify the library with -DPYTHON_LIBRARY, the correct file will start with "lib" and end in a ".so" extension. On My Mint 17.2 system the python library path would be -DPYTHON_LIBRARY= /usr/lib/x86_64-linux-gnu/libpython34m.so. But you really shouldn't need to specify it manually.

[DiapDealer]

Originally Posted by patrik

edit:
The only thing that wasn't installed is python3.4-six which couldn't be found. (but python3-six is installed)

Same - same. I really think you should delete everything in your cmake sigil build directory and start over at this point. If cmake still can't find everything on its own, then make sure the -DPYTHON_LIBRARY path points to a valid library similar to the one I indicated in my previous post (and that the file exists).

[patrik]

Ok, I deleted everything and started over. After all the cmake and make'ing, I still got to 100% and then the error (as shown above).

Did it again, but now with no LIB-path set to cmake. Exactly the same.

Ok... did it all again, this time setting LIB-path to libpython3.4m.so.
Yes, success!

Continued following the doc-file, downloaded the testplugin_v11.zip. Error.... not valid plugin file.... Argh..... what did i do wrong this time....
Downloaded the flightcrew-plugin, and that installed just fine! Puh....

Thanks for the help!

[DiapDealer]

Originally Posted by patrik

Continued following the doc-file, downloaded the testplugin_v11.zip. Error.... not valid plugin file.... Argh..... what did i do wrong this time....
Downloaded the flightcrew-plugin, and that installed just fine! Puh....

Sounds like you got a bad download. But you don't have to download the test plugin. It should already be located in the 'doc' folder of the Sigil source code. Be sure you don't rename the zip file before installing it. Plugin file names are very specific.

[patrik]

I guess, but I did download it several times.... Oh well, installed the one that was in the src. All passed!

[DiapDealer]

Originally Posted by patrik

I guess, but I did download it several times.... Oh well, installed the one that was in the src. All passed!

Glad to hear it!

[roger64]

Hi

A suggestion: when we create a new EPUB3, it lacks any language spec (xml:lang="x"). Wouldn't be useful to provide it with one according to the Preferences/Language settings?

[KevinH]

The default language (or languages) are defined in the content.opf, making the need for lang or xml:lang on the html tag redundant. In pure standalone html files that are not part of an epub (i.e. without a content.opf), it is good practice to add those attributes for reading by assistive technologies. In epubs they are not required and it is up to the ebook developer to decide to add them or not.

If this is something you want, you can esily use a plugin like DiapDealers newest addition to add anything here you want or even a simple search and replace of the html tags.

KevinH

[roger64]

It's like raincoat and umbrella. Some people take both.

I just had a look to the content.opf file of a new EPUB3 and this information seems to be missing as well. I have no personal problem about it, but this seems a bit curious. Who does not need any language?