We have no preferred way to build for Mac. The MacPorts community had
already solved about 25% of the build errors we had open, so I chose to
commit their fixes upstream and use their build recipe for our official
version.
That said... there is much room for improvement in this regard, and the
Apple community seems to have strong feelings between MacPorts and Homebrew
from a development perspective (so much that each time I've asked for help
on a public forum, an argument breaks out as to which solution is better).
We do have one lmms community member which claims to have had some success
with Homebrew, but I haven't heard from him in months.
The major benefit in leveraging homebrew is that it can help iron out
hard-coded dependencies specific to MacPorts in our scripts. It also has
the tendency to improve the overall quality of our build instructions.
Making our instructions infrastructurally independent usually benefits the
project by reducing the reliance on the availability of one single
technology (i.e. what if MacPorts goes away?)
If your goal is to fix a single bug, MacPorts will have you up and running
the quickest.
If your goal is to improve our build process in general and also start
fixing bugs, homebrew may be a better avenue.
So, for sake of getting bugs fixed in a timely fashion, I strongly
recommend MacPorts since a homebrew fan is likely to come around eventually.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
