1. dirkbaechle
  2. SCons_Qt5
  3. Issues
Issue #1 resolved

Precompiled Manual?

created an issue

Is there an already compiled manual available somewhere? I've not used DocBook before, and there seem to be quite a few dependencies.

Comments (11)

  1. dirkbaechle repo owner

    Creating the manual should work out of the box, if you install the freshly released SCons v2.3.1. You might have to uncomment the PDF creation commands if you don't have a PDF renderer like fop or xep installed. But for simple HTML output you now only need SCons and one of the libxml2 or lxml Python bindings.

    The Qt4 Tool has precompiled manuals at http://www.scons.org/wiki/Qt4Tool , and it's very similar to Qt5. But please try to compile the manual yourself and report any errors you find.



  2. InfernoZeus reporter

    I'm stuck using SCons v2.3.0. Should that be able to build the HTML manual out of the box? SCons tells me there's "No tool named DocBook".

    After installing it manually, I get the following error messages:

    scons: Reading SConscript files ...
    scons: done reading SConscript files.
    scons: Building targets ...
    o manual.html html.xsl manual.xml
    sh: 1: o: not found
    o reference.html html.xsl reference.xml
    sh: 1: o: not found
    scons: done building targets.
  3. dirkbaechle repo owner

    What do you mean when you say "you're stuck"? Can't even download the "local" version of SCons (doesn't require you to install it systemwide) and start it?

    SCons v.2.3.0 doesn't have the "docbook" Tool as core component, it was only added for v2.3.1. So the other option would be to download it separately from its repo (as given in the ToolsIndex at the Wiki).

    If you don't have the Docbook stylesheets installed in your system, you'll also want to remove the "DOCBOOK_XSL=..." parameter in the SConstruct.

  4. InfernoZeus reporter

    I switched over to v.2.3.1 temporarily, but I'm still getting the same error messages (both with and without the DOCBOOK_XSL parameter).

    I'm pretty new to SCons, is there some way to get more verbose logs to help find the cause?

  5. dirkbaechle repo owner

    Please make sure that you have one of the libxml2 or lxmxl Python bindings installed. You should be able to open a Python interpreter, and type either

    import lxml


    import libxml2

    without getting any errors. If you do get an ImportError, please install one of these Python bindings and their dependencies via your package manager.

    Then try again.

  6. dirkbaechle repo owner

    If you should still have trouble getting the DocBook Tool to work, I've added a README.rst to the repo a few seconds ago. So you can simply go to the frontpage of scons_qt5 and read the manual there now.

    Hope this helps.

  7. InfernoZeus reporter

    No ImportError's if I try to import libxml2.

    Apparently the message I'm getting is usually caused by SCons not being able to find gcc/g++, but if I try to manually set the paths to them in the Environment, I get even more cryptic messages:

    scons: Reading SConscript files ...
    AttributeError: 'SConsEnvironment' object has no attribute 'Object':
      File "/home/ben/Development/qt-scons/site_scons/site_tools/qt5/docs/SConstruct", line 35:
      File "/usr/local/lib/scons-2.3.1/SCons/SConf.py", line 643:
        ret = self.test(context, *args, **kw)
      File "/usr/local/lib/scons-2.3.1/SCons/SConf.py", line 948:
        res = SCons.Conftest.CheckCXX(context)
      File "/usr/local/lib/scons-2.3.1/SCons/Conftest.py", line 206:
        ret = _check_empty_program(context, 'CXX', text, 'C++')
      File "/usr/local/lib/scons-2.3.1/SCons/Conftest.py", line 243:
        return context.CompileProg(text, suffix)
      File "/usr/local/lib/scons-2.3.1/SCons/SConf.py", line 831:
        return not self.TryBuild(self.env.Object, text, ext)
    Checking whether the C++ compiler works... 

    Thanks for the README though, very helpful :)

  8. dirkbaechle repo owner

    The error message says that in l. 35 of your SConstruct "conf.CheckCXX()" gets called. Did you add it? I'm asking because I searched the full source tree for the Qt5 tool and SCons v2.3.1 itself, and found no match.

    Sorry for asking this, but have you already successfully run some other build with SCons, or are these your very first steps? In the latter case you might want to write to our mailing list at scons-users@scons.org, where you can get more and faster help because more people listen.

  9. InfernoZeus reporter

    Sorry, I added that to try and confirm that SCons was correctly detecting gcc/g++.

    I've built a couple of projects with SCons already, with no problems.

    Thanks for your help, I think I'll leave it for now as you've added the Readme, and the problem seems to be specific to my environment.

  10. dirkbaechle repo owner

    If it's okay with you like that, sure. I didn't want to cut off this conversation, but simply wondered what your level of knowledge with SCons would be.

    From what I could see so far, I'd still suspect that (for some unknown reason) the DocBook tool is not able to find the libxml2/lxml bindings, and also (this is the last fallback usually) can't detect a "xsltproc" executable on your current PATH. That's where the funny name "o" for the executable comes from, that SCons is trying to call.

    Anyway, we'll leave it at that for now. If you should experience further problems and have more questions, please feel invited to open a new issue report at the offending tool, or come over to the SCons user mailing list.

    Thanks a lot for your patience.

    Best regards,


  11. Log in to comment