Re: compiling MacOS application in LilyDev

[Hans Åberg]

> On 9 Nov 2021, at 19:06, Kieren MacMillan  
> wrote:
> 
>> The intent is probably to create an app.
> 
> Yes, for me to run (personally).
> 
>> One can make installers with MacPorts, I posted some on the users list.
> 
> I found that thread — helpful!
> 
> I tried, and got:
> 
> Error: Failed to activate dbus: Image error: 
> /Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and 
> does not belong to a registered port.  Unable to activate port dbus. Use 
> 'port -f activate dbus' to force the activation.
> 
> I tried that, …

I do not have dbus. A net search on that error line gives various suggestions.

If you want reinstall MacPorts, this command lists the requested installs:
  port echo requested | cut -d ' ' -f 1 | uniq
It is from
  https://trac.macports.org/wiki/Migration

Re: compiling MacOS application in LilyDev

[Hans Åberg]

> On 9 Nov 2021, at 19:06, Kieren MacMillan  
> wrote:
> 
> Hi Hans,
> 
>> The intent is probably to create an app.
> 
> Yes, for me to run (personally).
> 
>> One can make installers with MacPorts, I posted some on the users list.
> 
> I found that thread — helpful!
> 
> I tried, and got:
> 
> Error: Failed to activate dbus: Image error: 
> /Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and 
> does not belong to a registered port.  Unable to activate port dbus. Use 
> 'port -f activate dbus' to force the activation.
> 
> I tried that, and got
> 
> dlopen(/opt/local/libexec/macports/lib/macports1.0/MacPorts.dylib, 6): Symbol 
> not found: _iconv
>  Referenced from: /usr/lib/libcups.2.dylib
>  Expected in: /opt/local/lib/libiconv.2.dylib
> in /usr/lib/libcups.2.dylib
>while executing
> "load /opt/local/libexec/macports/lib/macports1.0/MacPorts.dylib"
>("package ifneeded macports 1.0" script)
>invoked from within
> "package require macports"
>(file "/opt/local/bin/port" line 46)
> 
> Advice?


The link [1] suggests it has to do with some DYLD_* environment variables. I 
have /opt/local/* additions only to PATH, and optionally to MANPATH and 
INFOPATH.

1. 
https://stackoverflow.com/questions/30420695/dyld-symbol-not-found-iconv-when-using-javac-to-compile-on-macos

Re: compiling MacOS application in LilyDev

[Kieren MacMillan]

Hi Hans,

> You tried what? Making your own installer from MacPorts?

I tried

   port install lilypond-devel

> I can post the steps I use to make the installer if you so want.

I would appreciate that.

Thanks!
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info

Re: compiling MacOS application in LilyDev

[Hans Åberg]

> On 9 Nov 2021, at 19:06, Kieren MacMillan  
> wrote:
> 
> Hi Hans,
> 
>> One can make installers with MacPorts, I posted some on the users list.
> 
> I found that thread — helpful!
> 
> I tried, and got:
> 
> Error: …

You tried what? Making your own installer from MacPorts? —The ones I do install 
in /opt/lilypond/, and you use /opt/lilypond/ it looked like. The location I 
use is suggested by the FHS (file hierarchy standard) and Werner.

One issue is that /opt/lilypond/bin/ must be in PATH, otherwise some programs 
like 'gs' will not be called.

I can post the steps I use to make the installer if you so want.

It might be of interest if you try making a universal installer, but it would 
likely involve getting touch with the MacPorts people for help.

Re: compiling MacOS application in LilyDev

[Kieren MacMillan]

Hi Hans,

> The intent is probably to create an app.

Yes, for me to run (personally).

> One can make installers with MacPorts, I posted some on the users list.

I found that thread — helpful!

I tried, and got:

Error: Failed to activate dbus: Image error: 
/Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and 
does not belong to a registered port.  Unable to activate port dbus. Use 'port 
-f activate dbus' to force the activation.

I tried that, and got

dlopen(/opt/local/libexec/macports/lib/macports1.0/MacPorts.dylib, 6): Symbol 
not found: _iconv
  Referenced from: /usr/lib/libcups.2.dylib
  Expected in: /opt/local/lib/libiconv.2.dylib
 in /usr/lib/libcups.2.dylib
while executing
"load /opt/local/libexec/macports/lib/macports1.0/MacPorts.dylib"
("package ifneeded macports 1.0" script)
invoked from within
"package require macports"
(file "/opt/local/bin/port" line 46)

Advice?

Thanks,
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info

Re: compiling MacOS application in LilyDev

[Hans Åberg]

> On 9 Nov 2021, at 00:50, Karlin High  wrote:
> 
> On 11/8/2021 4:55 PM, Kieren MacMillan wrote:
>> I’m on 10.13.6 (High Sierra)
> 
> High Sierra can still run 32-bit, right? That could allow for using GUB on 
> LilyDev to produce a standard macOS installer.

The intent is probably to create an app. One can make installers with MacPorts, 
I posted some on the users list. They are for a specific MacOS version. One can 
also make universal installers, but some component did not compile when I 
tried. Also, LilyPond can overflow on 32-bit: some issue resolved when I 
switched to the MacPorts version which is 64-bit. So only use the 32-bit 
version if 64-bit is not available, I think.

Re: compiling MacOS application in LilyDev

[Karlin High]

On 11/8/2021 4:55 PM, Kieren MacMillan wrote:

I’m on 10.13.6 (High Sierra)


High Sierra can still run 32-bit, right? That could allow for using GUB 
on LilyDev to produce a standard macOS installer.

--
Karlin High
Missouri, USA

Re: compiling MacOS application in LilyDev

[Jefferson Felix]

> How can I tell if it ultimately worked?
I'm not sure if it works on High Sierra. But if you didn't installed
any other version of Lilypond, lilypond --version will print "GNU
Lilypond 2.23.5 (running Guile 2.2)"

-- 
---
Jefferson dos Santos Felix

Re: compiling MacOS application in LilyDev

[Kieren MacMillan]

Hi Jefferson,

> If you need to compile from the master branch natively on macOS, with
> Guile 2.2, the easiest way is to use homebrew:
> brew install --HEAD lilypond
> This command installs all lilypond build dependencies, clones the
> master branch and compiles it, but the docs are not included.

Ooh! I think this is exactly what I need [for my own personal use of the 
bleeding-edge].

Unfortunately, I’m on 10.13.6 (High Sierra), and running that brew command 
leads (after a long time!) to a bunch of warnings:

Warning: Your Xcode (9.2) is outdated.
Please update to Xcode 10.1 (or delete it).
Xcode can be updated from the App Store.

How can I tell if it ultimately worked?

> But if you are compiling for the purpose of contributing to Lilypond,
> I believe Lilydev is still the recommended way to do this.

Excellent. I really wasn’t grokking that my two different uses (dev and 
personal) could be handled two different ways.

Thanks!
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info

Re: compiling MacOS application in LilyDev

[Jefferson Felix]

Kieren,

If you need to compile from the master branch natively on macOS, with
Guile 2.2, the easiest way is to use homebrew:

brew install --HEAD lilypond

This command installs all lilypond build dependencies, clones the
master branch and compiles it, but the docs are not included.

But if you are compiling for the purpose of contributing to Lilypond,
I believe Lilydev is still the recommended way to do this.


Em seg., 8 de nov. de 2021 às 17:24, Jonas Hahnfeld via Discussions on
LilyPond development  escreveu:
>
> Am Sonntag, dem 07.11.2021 um 20:13 -0600 schrieb Karlin High:
> > On Sun, Nov 7, 2021, 6:46 PM Kieren MacMillan 
> > 
> > wrote:
> >
> > > is it possible for me to compile a version of Lilypond that will run
> > > natively on my Mac OS machine?
> > >
> >
> > One starting point:
> >
> > 
>
> As far as I can tell, this won't work with current master because it's
> stuck on 2.20 with Python 2. Now it depends on what you call "run
> natively": If you are fine with 32-bit executables, GUB is still the
> official source for our binaries and cross-compiles from Linux. It's
> probably possible to make it work under LilyDev, but it's ... uhm ...
> not the easiest setup to get right.
>
> If you're feeling a bit advantageous and want 64-bit binaries with
> Guile 2.2, you are welcome to give the new infrastructure a try that I
> have been developing for the past months. The version in master works
> *almost*, be sure to apply
> https://gitlab.com/lilypond/lilypond/-/merge_requests/986 or wait for
> it to be merged. This needs to be run natively on macOS (*not* under
> the LilyDev VM) and you'll need to install all build-time dependencies
> to build LilyPond and its run-time dependencies (for example with
> HomeBrew: bison, fontforge, meson, ninja, python, t1utils, texlive).
>
> Jonas



-- 
---
Jefferson dos Santos Felix

Re: compiling MacOS application in LilyDev

[Jonas Hahnfeld via Discussions on LilyPond development]

Am Sonntag, dem 07.11.2021 um 20:13 -0600 schrieb Karlin High:
> On Sun, Nov 7, 2021, 6:46 PM Kieren MacMillan 
> wrote:
> 
> > is it possible for me to compile a version of Lilypond that will run
> > natively on my Mac OS machine?
> > 
> 
> One starting point:
> 
> 

As far as I can tell, this won't work with current master because it's
stuck on 2.20 with Python 2. Now it depends on what you call "run
natively": If you are fine with 32-bit executables, GUB is still the
official source for our binaries and cross-compiles from Linux. It's
probably possible to make it work under LilyDev, but it's ... uhm ...
not the easiest setup to get right.

If you're feeling a bit advantageous and want 64-bit binaries with
Guile 2.2, you are welcome to give the new infrastructure a try that I
have been developing for the past months. The version in master works
*almost*, be sure to apply
https://gitlab.com/lilypond/lilypond/-/merge_requests/986 or wait for
it to be merged. This needs to be run natively on macOS (*not* under
the LilyDev VM) and you'll need to install all build-time dependencies
to build LilyPond and its run-time dependencies (for example with
HomeBrew: bison, fontforge, meson, ninja, python, t1utils, texlive).

Jonas


signature.asc
Description: This is a digitally signed message part

Re: compiling MacOS application in LilyDev

[Karlin High]

On Sun, Nov 7, 2021, 6:46 PM Kieren MacMillan 
wrote:

> is it possible for me to compile a version of Lilypond that will run
> natively on my Mac OS machine?
>

One starting point:



>

compiling MacOS application in LilyDev

[Kieren MacMillan]

Hi all,

Now that I can compile master from source, is it possible for me to compile a 
version of Lilypond that will run natively on my Mac OS machine? (My 
development/compilation environment is LilyDev running in VirtualBox.)

Thanks,
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info