• Welcome to the Pipe Organ Forum! This is a part of the open community Magle International Music Forums focused on pipe organs (also known as "church organs"), organists, organ music and related topics.

    This forum is intended to be a friendly place where technically advanced organists and beginners (or even non-organists) can feel comfortable having discussions and asking questions. We learn by reading and asking questions, and it is hoped that the beginners (or non-organists) will feel free to ask even the simplest questions, and that the more advanced organists will patiently answer these questions. On the other hand, we encourage complex, technical discussions of technique, music, organ-building, etc. The opinions and observations of a diverse group of people from around the world should prove to be interesting and stimulating to all of us.

    As pipe organ discussions can sometimes become lively, it should be pointed out that this is an open forum. Statements made here are the opinion of the poster, and not necessarily that of the forum itself, its administrator, or its moderators.

    In order to post a new topic - or reply to existing ones - you may join and become a member by clicking on Register New User. It's completely free and only requires a working email address (in order to confirm your registration - it will never be given away!). We strive to make this a friendly and informative forum for anyone interested in pipe organs and organ music.

    (Note: If you wish to link to and promote your own website please read this thread first.)

    Many kind regards
    smile.gif

    Frederik Magle
    Administrator

    Krummhorn
    Co-Administrator

Grandorgue installation on Linux lacks 'help'

edenyard

New member
Hello to all. I've just joined this list, having successfully downloaded, built and installed Grandorgue-svn V3.0.1.1111 on my Arch Linux system. I've also downloaded a couple of sample sets to experiment with and I like what I hear so far. However, I've noticed that nothing much happens when I press 'F1' for help. I get a new window opening entitled 'Help' but both the side pane and the main pane are blank white. Presumably GO can't find its help file. Where should this be located? I see that there's a grandorgue.xml file in /usr/local/share/mime/packages but it's only 1.4KB in size. I'd be grateful for some guidance on what I'm missing and where! Also, I bought the Romantic48 sample set from Silver Octopus some while ago for use with the Jorgan/Fluidsynth system that I've been playing with for a few years. I'd like to make a GO .organ file to be able to use it in GO and see if it sounds any better there. Is there any easy way of doing this, or is it a line-by-line typing job? Any help gratefully received! Many thanks, Gerald.
 

e9925248

New member
However, I've noticed that nothing much happens when I press 'F1' for help. I get a new window opening entitled 'Help' but both the side pane and the main pane are blank white. Presumably GO can't find its help file. Where should this be located? I see that there's a grandorgue.xml file in /usr/local/share/mime/packages but it's only 1.4KB in size. I'd be grateful for some guidance on what I'm missing and where!

I guess, that you have not installed a build dependency of the help file (or arch linux put it in a unexpected location). Please look at the cmake messages (especially if it is run the first time).

GO sources include packaging for the major linux disitribution - you can use that as reference.
 

edenyard

New member
What do I have to do to get line breaks (carriage-returns) in what I type here. I see that my first message appeared as all one paragraph, even though I actually typed it as 3 or 4 separate paragraphs. I see that other people posting on here manage to get line breaks and paragraph breaks so what's the secret? I just attempted to reply to message #2 on this thread and quote cmake's output but it appeared in the preview as a hopeless jumble of text without any line breaks so I've given up for now. Please someone enlighten me on what to do to get decently formatted text to show on here? This post should show up with 3 separate paragraphs.
 

edenyard

New member
Doesn't ANYBODY have any idea at all about this problem (missing line breaks)? . I have a few questions I'd like to find answers to but it's hopeless trying to type anything here while the site persists in removing line breaks . Anyone????? . PLEASE??????
 

L.Palo

New member
Hi!

Using Firefox on Ubuntu the format of line breaks etc has always worked fine when I write after hitting the "Go Advanced" button below the posts.

The WYSIWYG editor for formatting works just fine. If you want to quote something you can just paste the copied lines you want to quote within the tags created after hitting the "Quote" icon in the editor.

Anyway, if you have some questions you want answered I guess we can try to answer even if the text formatting is not as it should...

Kind regards

Lars P
 

Krummhorn

Administrator
Staff member
ADMINISTRATOR
Doesn't ANYBODY have any idea at all about this problem (missing line breaks)? . I have a few questions I'd like to find answers to but it's hopeless trying to type anything here while the site persists in removing line breaks . Anyone????? . PLEASE??????

When posting messages to the forums or other members, there are three interface types available to you. The simplest of these is a simple text box, while the last is a fully-fledged WYSIWYG editor, which allows you to format your text as you want it and see the results immediately.

Depending upon the capabilities of your web browser, you may not be able to use all of these options. If you experience problems when posting messages, try switching to a different interface type.*

The forum 'default' interface is Show Enhanced (WYSIWYG) Editor Toolbar for all members at point of registration. To use that editor, click on the Go Advanced button.

What browser are you using? Are you using a PC or MAC? Mobile device for replying? The problem could be related to 'browser' settings too ... possibly the font you are using is not compatible with the forum's default verdana ... (?). Just throwing out possibilities here ... this situation has not occurred before for other members. I ran a check on the forum software/settings and everything on the site is working as it is supposed to.

* if you need this changed, let me know as access to a members profile (where these settings are located) is restricted until one has completed at least 10 posts on the forum.
 

edenyard

New member
Very many thanks, Lars and Krummhorn, for coming to my aid! Spurred on by your suggestions, I've managed to find out the cause of the problem. For the record, I'm running Firefox 16.0.2 on a fully up-to-date Arch Linux system and I've never encountered this posting problem on any other forum's site. However....

I discovered this afternoon (more or less by accident) that my RequestPolicy add-on for Firefox was preventing me from getting to the 'advanced' editor on the Magle site. Until I read your posts, I hadn't realised that there was any choice in post editor. Having read them, I realised that I wasn't seeing the 'Go Advanced' or anything like that.

Now having reloaded the page with RequestPolicy turned off, I get a completely different post editor which honours my line breaks and has loads of additional buttons at the top of it, including font, size, bold/italic/underline, spacing and all sorts of other goodies. A trial run using 'Preview Post' seems to confirm that all is now well.

To keep things tidy, I'll make another post concerning the original thread problem. In the meantime, thanks again for pointing me to the solution.

Best wishes,
Gerald.
 

edenyard

New member
Further to the 'missing GO help' problem that I started this thread about, I've watched the build process more closely, thanks to whoever posted message #2 (sorry - I can't see the poster's name anywhere).

Theres an error message during the build:

Code:
============================================================================
Found Gettext: /usr/bin/msgmerge (found version "0.18.1") 
gettext not found
docbook-xsl stylesheets not found
Not build help - some programs are missing
Not building translations - some programs are missing
  Project                     : GrandOrgue
  Description                 : GrandOrgue - OpenSource Virtual Pipe Organ Software
  Version                     : 0.3.0.6
============================================================================

However, 'which gettext' returns with '/usr/bin/gettext' so that certainly exists on the path. Also, I find docbook-xsl stylesheets are installed in /usr/share/xml/docbook/xsl-stylesheets-1.77.1/

Thinking that, maybe, the build process doesn't see 'xml-stylesheets' because it has '-1.77.1' appended, I symlinked the directory to /usr/share/xml/docbook/xsl-stylesheets/ but that doesn't make any difference. Same error.

The build process is still adamant that gettext and xsl-stylesheets are missing, despite my being able to see them present. This is a standard Arch Linux x86_64 system, by the way.

Please can someone advise on how I fix this build problem? I'm stumped now!

Thanks,
Gerald.
 

L.Palo

New member
Hi!

The readme file states under B) Building on Linux:

2) Install docbook-xsl, xlstproc, zip, gettext and po4a (if present on your distribution)

On debian derivates (ie Ubuntu etc) all the packages can be found in the repositories. I'm unfortunately not familiar with Arch Linux at all so this is the best help I can give for now...

Kind regards

Lars P
 

e9925248

New member
However, 'which gettext' returns with '/usr/bin/gettext' so that certainly exists on the path.

This is a test shipped with cmake - it searches for msgfmt and msgmerge. It will later also search for xgettext.

Also, I find docbook-xsl stylesheets are installed in /usr/share/xml/docbook/xsl-stylesheets-1.77.1/

Thinking that, maybe, the build process doesn't see 'xml-stylesheets' because it has '-1.77.1' appended, I symlinked the directory to /usr/share/xml/docbook/xsl-stylesheets/ but that doesn't make any difference. Same error.

The build process is still adamant that gettext and xsl-stylesheets are missing, despite my being able to see them present. This is a standard Arch Linux x86_64 system, by the way.

The docbook search path (for file /htmlhelp/htmlhelp.xsl) is usr/share/xml/docbook/stylesheet/nwalsh /usr/share/xml/docbook/stylesheet/nwalsh/current /usr/share/sgml/docbook/xsl-stylesheets. You can pass an additional dir via cmake -DDOCBOOK_DIR=....

Please also note, that cmake caches search results between runs - so this can prevent cmake from reacting to system changes.
 

scush

New member
Going off the lenth of that path, the stylesheets most be on the other side of the moon.
No spaces in directory names so should be ok.

Sorry realized it's the search path without ;;;
 
Last edited:

edenyard

New member
2) Install docbook-xsl, xlstproc, zip, gettext and po4a (if present on your distribution)

Thanks for that, Lars.

Everything in that list seemed to be present on my system with the exception of xlstproc, which (a) appears to be called xsltproc ('L' and 'S' swapped around) and (b) isn't a package in its own right in Arch but is found in package libxslt, just for the record.

After adding -DDOCBOOK_DIR=/usr/share/xml/docbook/xsl-stylesheets to the line that invokes cmake in the PKGBUILD file, and also adding a symlink /usr/share/xml/docbook/xsl-stylesheets to point to /usr/share/xml/docbook/xsl-stylesheets-1.77.1, the help files are now built and included in the installation package.

Interestingly, the build process still claims that it cannot find 'gettext' (it IS actually present in /usr/bin/gettext). This, then, is presumably a bug in the build script supplied with the source code or whatever.

Anyway - the 'help' problem is now resolved. I thought it useful to document the solution here, just in case any other Arch users come this way!

Thanks again for your help.
Gerald.
 

e9925248

New member
Interestingly, the build process still claims that it cannot find 'gettext' (it IS actually present in /usr/bin/gettext). This, then, is presumably a bug in the build script supplied with the source code or whatever.

GO uses the FindGettext Module from CMake (/usr/share/cmake-2.8/Modules/FindGettext.cmake). This prints this misleading error message. It search for the various programs part of the "gettext" package (http://www.gnu.org/software/gettext/). Technically, it searches for the msgmerge and msgfmt binaries.
 

edenyard

New member
GO uses the FindGettext Module from CMake (/usr/share/cmake-2.8/Modules/FindGettext.cmake). This prints this misleading error message. It search for the various programs part of the "gettext" package (http://www.gnu.org/software/gettext/). Technically, it searches for the msgmerge and msgfmt binaries.

Code:
[COLOR=#000000][gerald@x2 ~]$ which msgmerge
/usr/bin/msgmerge
[gerald@x2 ~]$ which msgfmt
/usr/bin/msgfmt[/COLOR]

It appears that both msgmerge and msgfmt are present in the search path.

Is there something else to check?

Cheers,
Gerald.
 

e9925248

New member
Code:
[COLOR=#000000][gerald@x2 ~]$ which msgmerge
/usr/bin/msgmerge
[gerald@x2 ~]$ which msgfmt
/usr/bin/msgfmt[/COLOR]

It appears that both msgmerge and msgfmt are present in the search path.

Is there something else to check?

Maybe cmake cached something:
grep GETTEXT CMakeCache.txt
 

edenyard

New member
Maybe cmake cached something:
grep GETTEXT CMakeCache.txt

Relevant lines found in CMakeCache:

Code:
[COLOR=#000000]//Path to a program.
GETTEXT_MSGFMT_EXECUTABLE:FILEPATH=/usr/bin/msgfmt

//Path to a program.
GETTEXT_MSGMERGE_EXECUTABLE:FILEPATH=/usr/bin/msgmerge

//Path to a program.
GETTEXT_XGETTEXT_EXECUTABLE:FILEPATH=/usr/bin/xgettext


//Path to a program.
PO4A_GETTEXT:FILEPATH=/usr/bin/vendor_perl/po4a-gettextize


//Details about finding Gettext
FIND_PACKAGE_MESSAGE_DETAILS_Gettext:INTERNAL=[/usr/bin/msgmerge][/usr/bin/msgfmt][v0.18.1()][/COLOR]

The build directories were erased immediately before the build, so I wouldn't have thought that the build process could remember anything from previous builds.

What's next?

Cheers,
Gerald.
 

scush

New member
FIND_PROGRAM(GETTEXT_XGETTEXT_EXECUTABLE xgettext)
IF (NOT GETTEXT_FOUND)
MESSAGE(STATUS "gettext not found")
ENDIF()
IF (NOT GETTEXT_XGETTEXT_EXECUTABLE)
MESSAGE(STATUS "xgettext not found (package gettext)")
ENDIF()
IF (NOT GETTEXT_MSGMERGE_EXECUTABLE)
MESSAGE(STATUS "msgmerge not found (package gettext)")
ENDIF()
IF (NOT GETTEXT_MSGFMT_EXECUTABLE)
MESSAGE(STATUS "msgfmt not found (package gettext)")
ENDIF()


To what does gettext refer,deleting lines 2,3,4 removes the message
 
Last edited:

scush

New member
Hi

Could this be why I can't build wasapi ?

john

Ps That's fixed the "gettext not found" Thanks Martin.
I will see if it makes any difference to the build.

Pps It had no effect 3x mo 2x htb
 
Last edited:
Top