build for mac os x

classic Classic list List threaded Threaded
52 messages Options
123
Reply | Threaded
Open this post in threaded view
|

build for mac os x

Arnaud Moreau
Hi,

I'm interested in helping building musescore for mac os x. Is already somebody working on this? Is there some additional information available, which cannot be found on the website or SVN repository?

Best regards

Arnaud

--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

David Bolton-2
Arnaud Moreau wrote:
> Hi,
>
> I'm interested in helping building musescore for mac os x. Is already somebody working on this? Is there some additional information available, which cannot be found on the website or SVN repository?
>
> Best regards
>
> Arnaud
>
>  

A couple weeks ago Samuli wrote to the list. See the thread here:
http://n2.nabble.com/Mac-build.-td1456484.html

There are compile instructions for Ubuntu in the developers handbook
that might be helpful as a starting place.
http://musescore.org/en/handbook/compile-instructions-ubuntu

--
David Bolton
http://davidbolton.info


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

lasconic
Administrator
And of course you can ask support here if it's not mac related :)


2008/11/14 David Bolton <[hidden email]>
Arnaud Moreau wrote:
> Hi,
>
> I'm interested in helping building musescore for mac os x. Is already somebody working on this? Is there some additional information available, which cannot be found on the website or SVN repository?
>
> Best regards
>
> Arnaud
>
>

A couple weeks ago Samuli wrote to the list. See the thread here:
http://n2.nabble.com/Mac-build.-td1456484.html

There are compile instructions for Ubuntu in the developers handbook
that might be helpful as a starting place.
http://musescore.org/en/handbook/compile-instructions-ubuntu

--
David Bolton
http://davidbolton.info


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Johan Pauwels-2
Hi all,

Since I'd be interested in a Mac version for myself and clearly it's a  
requirement for adoption in music schools, I took a first real shot at  
compiling mscore for Mac OSX. I have no experience at all with any GUI  
programming and my knowledge of Xcode is basic too, so my mistakes are  
probably trivial for an experienced Mac developer, but I'm a quick  
learner and there seems no-one else around anyway.

Here's a summary of what I've done.

Previously installed:
-Xcode (Mac IDE, optional install with OSX)
-MacPorts 1.6 (apt-like software installer)
-QT 4.4.3 open source edition
-CMake 2.6-2

Compiling steps:
-downloaded and extracted musescore-0.9.3
-using MacPorts, installed doxygen, jack and portaudio (don't know to  
what extent they are required, but there were flags to use them in  
CMake)
-generated an Xcode project using Xcode
-opened the Xcode project and tried to compile


Two show-stopping errors arose when I tried to compile, both in the  
case of the complete project (equivalent to make) as for specific  
targets (e.g. equivalent to make libfluid). Compiling the "doxy"-
target worked btw, so the generated Xcode project is working.

1. In "all.h": No such file for #include <values.h>
Afaik, values.h is a header which defines machine constants, but is  
not present under BSD based systems, since it's obsolete. Most  
functionality can be found in limits.h and float.h. Error disappeared  
when replacing by only #include limits.h. Maybe somebody can tell me  
which of the constants in values.h is used and whether the inclusion  
of float.h is also necessary. It would be best to check whether this  
header can be replaced for all platforms, since it says in the file  
itself /* This interface is obsolete.  New programs should use  
<limits.h> and/or <float.h> instead of <values.h>.  */. Apparently it  
is not ANSI C (http://lists.apple.com/archives/scitech/2003/Nov/msg00190.html 
).

2. In "all.h":  No such file for #include <QtGui/QX11Info>
Not surprisingly, since this statement appears within #ifndef  
__MINGW32__ and is obviously platform dependent and related to the Qt  
toolkit, of which I know nothing. If it has to be replaced by  
something Mac specific, you can use #ifdef __APPLE__. Anyway, if it's  
a linux specific header, I think it would be better to just include it  
for Linux (#ifdef __LINUX__ ?) instead of just excluding it for not  
Linux, that would be a bit more extendable (in the case you want  
another port, for instance to your toaster).


Successful builds by leaving out QX11Info and replacing values.h by  
limits.h
-libawl.a
-libosdapzip.a
-smf2xml (when executed from command line without arguments, they are  
busy but no output nor error message appears)
-xml2smf (when executed from command line without arguments, they are  
busy but no output nor error message appears)
-gendoc
-onlinedoc
-libfluid.a
-libqtscript_debug.a

Unsuccessful builds when executing above steps
-libawlplugin.dylib: lots of linking errors with Qt
-mscore
-libqtscript_core.dylib: lots of linking errors with Qt
-libqtscript_gui.dylib: lots of linking errors with Qt
-libqtscript_network.dylib: lots of linking errors with Qt
-libqtscript_uitools.dylib: lots of linking errors with Qt
-libqtscript_xml.dylib: lots of linking errors with Qt

The linking errors with Qt make me conclude that an equivalent for  
QX11Info is necessary. It's probably no coincidence that all dynamic  
libraries give errors either. Does a Qt-savvy person has any tips for  
getting any further?

That's it for now,
Johan

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

lasconic
Administrator
I'm really really out of my base here. But is using Xcode necessary ? You can't install g++ and make and try the normal Linux way ?
Regarding 2., as a first step you can try to put
set(BUILD_SCRIPT_INTERFACE FALSE)
set(BUILD_SCRIPT_DEBUG FALSE)
 in mscore/CMakeLists.txt.

Keep on trying !

Lasconic

2008/11/29 Johan Pauwels <[hidden email]>
Hi all,

Since I'd be interested in a Mac version for myself and clearly it's a
requirement for adoption in music schools, I took a first real shot at
compiling mscore for Mac OSX. I have no experience at all with any GUI
programming and my knowledge of Xcode is basic too, so my mistakes are
probably trivial for an experienced Mac developer, but I'm a quick
learner and there seems no-one else around anyway.

Here's a summary of what I've done.

Previously installed:
-Xcode (Mac IDE, optional install with OSX)
-MacPorts 1.6 (apt-like software installer)
-QT 4.4.3 open source edition
-CMake 2.6-2

Compiling steps:
-downloaded and extracted musescore-0.9.3
-using MacPorts, installed doxygen, jack and portaudio (don't know to
what extent they are required, but there were flags to use them in
CMake)
-generated an Xcode project using Xcode
-opened the Xcode project and tried to compile


Two show-stopping errors arose when I tried to compile, both in the
case of the complete project (equivalent to make) as for specific
targets (e.g. equivalent to make libfluid). Compiling the "doxy"-
target worked btw, so the generated Xcode project is working.

1. In "all.h": No such file for #include <values.h>
Afaik, values.h is a header which defines machine constants, but is
not present under BSD based systems, since it's obsolete. Most
functionality can be found in limits.h and float.h. Error disappeared
when replacing by only #include limits.h. Maybe somebody can tell me
which of the constants in values.h is used and whether the inclusion
of float.h is also necessary. It would be best to check whether this
header can be replaced for all platforms, since it says in the file
itself /* This interface is obsolete.  New programs should use
<limits.h> and/or <float.h> instead of <values.h>.  */. Apparently it
is not ANSI C (http://lists.apple.com/archives/scitech/2003/Nov/msg00190.html
).

2. In "all.h":  No such file for #include <QtGui/QX11Info>
Not surprisingly, since this statement appears within #ifndef
__MINGW32__ and is obviously platform dependent and related to the Qt
toolkit, of which I know nothing. If it has to be replaced by
something Mac specific, you can use #ifdef __APPLE__. Anyway, if it's
a linux specific header, I think it would be better to just include it
for Linux (#ifdef __LINUX__ ?) instead of just excluding it for not
Linux, that would be a bit more extendable (in the case you want
another port, for instance to your toaster).


Successful builds by leaving out QX11Info and replacing values.h by
limits.h
-libawl.a
-libosdapzip.a
-smf2xml (when executed from command line without arguments, they are
busy but no output nor error message appears)
-xml2smf (when executed from command line without arguments, they are
busy but no output nor error message appears)
-gendoc
-onlinedoc
-libfluid.a
-libqtscript_debug.a

Unsuccessful builds when executing above steps
-libawlplugin.dylib: lots of linking errors with Qt
-mscore
-libqtscript_core.dylib: lots of linking errors with Qt
-libqtscript_gui.dylib: lots of linking errors with Qt
-libqtscript_network.dylib: lots of linking errors with Qt
-libqtscript_uitools.dylib: lots of linking errors with Qt
-libqtscript_xml.dylib: lots of linking errors with Qt

The linking errors with Qt make me conclude that an equivalent for
QX11Info is necessary. It's probably no coincidence that all dynamic
libraries give errors either. Does a Qt-savvy person has any tips for
getting any further?

That's it for now,
Johan

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Frye
This is basically the situation with the "linux" way of building. I believe I am seeing all the same linking errors with QT. I just have not had the time to look into QT yet.

-Samuli

On Nov 30, 2008, at 12:15 AM, Lasconic wrote:

I'm really really out of my base here. But is using Xcode necessary ? You can't install g++ and make and try the normal Linux way ?
Regarding 2., as a first step you can try to put
set(BUILD_SCRIPT_INTERFACE FALSE)
set(BUILD_SCRIPT_DEBUG FALSE)
 in mscore/CMakeLists.txt.

Keep on trying !

Lasconic

2008/11/29 Johan Pauwels <[hidden email]>
Hi all,

Since I'd be interested in a Mac version for myself and clearly it's a
requirement for adoption in music schools, I took a first real shot at
compiling mscore for Mac OSX. I have no experience at all with any GUI
programming and my knowledge of Xcode is basic too, so my mistakes are
probably trivial for an experienced Mac developer, but I'm a quick
learner and there seems no-one else around anyway.

Here's a summary of what I've done.

Previously installed:
-Xcode (Mac IDE, optional install with OSX)
-MacPorts 1.6 (apt-like software installer)
-QT 4.4.3 open source edition
-CMake 2.6-2

Compiling steps:
-downloaded and extracted musescore-0.9.3
-using MacPorts, installed doxygen, jack and portaudio (don't know to
what extent they are required, but there were flags to use them in
CMake)
-generated an Xcode project using Xcode
-opened the Xcode project and tried to compile


Two show-stopping errors arose when I tried to compile, both in the
case of the complete project (equivalent to make) as for specific
targets (e.g. equivalent to make libfluid). Compiling the "doxy"-
target worked btw, so the generated Xcode project is working.

1. In "all.h": No such file for #include <values.h>
Afaik, values.h is a header which defines machine constants, but is
not present under BSD based systems, since it's obsolete. Most
functionality can be found in limits.h and float.h. Error disappeared
when replacing by only #include limits.h. Maybe somebody can tell me
which of the constants in values.h is used and whether the inclusion
of float.h is also necessary. It would be best to check whether this
header can be replaced for all platforms, since it says in the file
itself /* This interface is obsolete.  New programs should use
<limits.h> and/or <float.h> instead of <values.h>.  */. Apparently it
is not ANSI C (http://lists.apple.com/archives/scitech/2003/Nov/msg00190.html
).

2. In "all.h":  No such file for #include <QtGui/QX11Info>
Not surprisingly, since this statement appears within #ifndef
__MINGW32__ and is obviously platform dependent and related to the Qt
toolkit, of which I know nothing. If it has to be replaced by
something Mac specific, you can use #ifdef __APPLE__. Anyway, if it's
a linux specific header, I think it would be better to just include it
for Linux (#ifdef __LINUX__ ?) instead of just excluding it for not
Linux, that would be a bit more extendable (in the case you want
another port, for instance to your toaster).


Successful builds by leaving out QX11Info and replacing values.h by
limits.h
-libawl.a
-libosdapzip.a
-smf2xml (when executed from command line without arguments, they are
busy but no output nor error message appears)
-xml2smf (when executed from command line without arguments, they are
busy but no output nor error message appears)
-gendoc
-onlinedoc
-libfluid.a
-libqtscript_debug.a

Unsuccessful builds when executing above steps
-libawlplugin.dylib: lots of linking errors with Qt
-mscore
-libqtscript_core.dylib: lots of linking errors with Qt
-libqtscript_gui.dylib: lots of linking errors with Qt
-libqtscript_network.dylib: lots of linking errors with Qt
-libqtscript_uitools.dylib: lots of linking errors with Qt
-libqtscript_xml.dylib: lots of linking errors with Qt

The linking errors with Qt make me conclude that an equivalent for
QX11Info is necessary. It's probably no coincidence that all dynamic
libraries give errors either. Does a Qt-savvy person has any tips for
getting any further?

That's it for now,
Johan

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Johan Pauwels-2
In reply to this post by lasconic

On 29 Nov 2008, at 23:15, Lasconic wrote:

I'm really really out of my base here. But is using Xcode necessary ? You can't install g++ and make and try the normal Linux way ?

This is the normal Mac way, Xcode is just a GUI which calls g++. CMake generates for every platform tools for building (as you know of course, just pointing it out for later reference) and for Mac this happens to be Xcode files. Generating command line OS X makefiles can be configured too, but assuming CMake is built for this purpose, it is safe to say that building with Xcode or make doesn't give any differences and as long as I get hundreds of errors, I prefer seeing them organized a bit in a window. If compiling this way works, I'll gladly look into using makefiles to be able to automate building, but it's going to need a custom makefile anyway, you can't just use the linux makefile (stupid example: option -shared needs to become -dynamic, but CMake should take care of this).

Regarding 2., as a first step you can try to put
set(BUILD_SCRIPT_INTERFACE FALSE)
set(BUILD_SCRIPT_DEBUG FALSE)
 in mscore/CMakeLists.txt.

Doesn't seem to make any difference, still the linking errors, I copied the first ones to give you an idea

    cd /Users/johan/Documents/mscore-svn/build
    /Developer/usr/bin/g++-4.0 -o /Users/johan/Documents/mscore-svn/build/awl/Debug/libawlplugin.dylib -L/Users/johan/Documents/mscore-svn/build/awl/Debug -F/Users/johan/Documents/mscore-svn/build/awl/Debug -filelist /Users/johan/Documents/mscore-svn/build/awl/mscore.build/Debug/libawlplugin.dylib.build/Objects-normal/i386/awlplugin.LinkFileList -arch i386 -Wl,-single_module -compatibility_version 1.0.0 -current_version 1.0.0 -install_name /libawlplugin.dylib -dynamiclib -dynamiclib -headerpad_max_install_names -install_name libawlplugin.dylib
Undefined symbols:
  "QPainterPath::QPainterPath(QPointF const&)", referenced from:
      Awl::Knob::paint(QRect const&)in knob.o
  "QObject::connectNotify(char const*)", referenced from:
      vtable for Awl::AbstractSliderin moc_aslider.o
      vtable for Awl::Knobin moc_knob.o
      vtable for Awl::PanKnobin moc_panknob.o
      vtable for Awl::VolKnobin moc_volknob.o
      vtable for Awl::MidiPanKnobin moc_midipanknob.o
      vtable for KnobPluginin moc_awlplugin.o
      vtable for VolKnobPluginin moc_awlplugin.o
      vtable for PanKnobPluginin moc_awlplugin.o
      vtable for MidiPanKnobPluginin moc_awlplugin.o
      vtable for ColorLabelPluginin moc_awlplugin.o
      vtable for AwlPluginsin moc_awlplugin.o
      vtable for Awl::ColorLabelin moc_colorlabel.o
  "QString::arg(QString const&, int, QChar const&) const", referenced from:
      QDesignerCustomWidgetInterface::domXml() const in moc_awlplugin.o
      QDesignerCustomWidgetInterface::domXml() const in moc_awlplugin.o
      QDesignerCustomWidgetInterface::domXml() const in awlplugin.o
      QDesignerCustomWidgetInterface::domXml() const in awlplugin.o
  "QPainter::drawText(QRectF const&, int, QString const&, QRectF*)", referenced from:
      Awl::Knob::paint(QRect const&)in knob.o
  "QWidget::closeEvent(QCloseEvent*)", referenced from:
      vtable for Awl::AbstractSliderin moc_aslider.o
      vtable for Awl::Knobin moc_knob.o
      vtable for Awl::PanKnobin moc_panknob.o
      vtable for Awl::VolKnobin moc_volknob.o
      vtable for Awl::MidiPanKnobin moc_midipanknob.o
      vtable for Awl::ColorLabelin moc_colorlabel.o
  "QPainter::~QPainter()", referenced from:
      Awl::Knob::paint(QRect const&)in knob.o
      Awl::ColorLabel::paintEvent(QPaintEvent*)       in colorlabel.o
  "QWidget::sizeHint() const", referenced from:
      vtable for Awl::AbstractSliderin moc_aslider.o
  "QPainterPath::lineTo(QPointF const&)", referenced from:
      QPainterPath::lineTo(double, double)in knob.o
  "QListData::detach2()", referenced from:
      QList<QDesignerCustomWidgetInterface*>::detach_helper()        in awlplugin.o


Keep on trying !

More things I've done since last mail: I've switched to using the SVN version, which seems a bit cleaner with less targets (no gendoc, etc). Still the same results, static libraries and smf2xml/xml2smf compile, but not libawlplugin.dylib and consequently not mscore. 

Another issue which needs to be resolved sooner or later: in utils.cpp, clock_gettime not found because it is not present in OS X version of time.h. Suggested portable alternative seems to be gettimeofday (http://www.nabble.com/gettimeofday-or-clock_gettime-td19367943.html).

Now I'm out of ideas,
Johan

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

wschweer
Administrator
I guess you did not create&compile the qt moc generated files. All header files,
which contain classes derived from QObject and which contain an Q_OBJECT macro
must be processed with the qt utility "moc". The generated c++ files must then
be compiled and linked. If not you get linking errors complaining about
missing "vtable".
The cmake generated makefiles take care of all this dependencies.

Am Sonntag 30 November 2008 15:59:02 schrieb Johan Pauwels:

> On 29 Nov 2008, at 23:15, Lasconic wrote:
> > I'm really really out of my base here. But is using Xcode
> > necessary ? You can't install g++ and make and try the normal Linux
> > way ?
>
> This is the normal Mac way, Xcode is just a GUI which calls g++. CMake
> generates for every platform tools for building (as you know of
> course, just pointing it out for later reference) and for Mac this
> happens to be Xcode files. Generating command line OS X makefiles can
> be configured too, but assuming CMake is built for this purpose, it is
> safe to say that building with Xcode or make doesn't give any
> differences and as long as I get hundreds of errors, I prefer seeing
> them organized a bit in a window. If compiling this way works, I'll
> gladly look into using makefiles to be able to automate building, but
> it's going to need a custom makefile anyway, you can't just use the
> linux makefile (stupid example: option -shared needs to become -
> dynamic, but CMake should take care of this).
>
> > Regarding 2., as a first step you can try to put
> > set(BUILD_SCRIPT_INTERFACE FALSE)
> >
> > set(BUILD_SCRIPT_DEBUG FALSE)
> >  in mscore/CMakeLists.txt.
>
> Doesn't seem to make any difference, still the linking errors, I
> copied the first ones to give you an idea
>
>      cd /Users/johan/Documents/mscore-svn/build
>      /Developer/usr/bin/g++-4.0 -o /Users/johan/Documents/mscore-svn/
> build/awl/Debug/libawlplugin.dylib -L/Users/johan/Documents/mscore-svn/
> build/awl/Debug -F/Users/johan/Documents/mscore-svn/build/awl/Debug -
> filelist /Users/johan/Documents/mscore-svn/build/awl/mscore.build/
> Debug/libawlplugin.dylib.build/Objects-normal/i386/
> awlplugin.LinkFileList -arch i386 -Wl,-single_module -
> compatibility_version 1.0.0 -current_version 1.0.0 -install_name /
> libawlplugin.dylib -dynamiclib -dynamiclib -
> headerpad_max_install_names -install_name libawlplugin.dylib
> Undefined symbols:
>    "QPainterPath::QPainterPath(QPointF const&)", referenced from:
>        Awl::Knob::paint(QRect const&)in knob.o
>    "QObject::connectNotify(char const*)", referenced from:
>        vtable for Awl::AbstractSliderin moc_aslider.o
>        vtable for Awl::Knobin moc_knob.o
>        vtable for Awl::PanKnobin moc_panknob.o
>        vtable for Awl::VolKnobin moc_volknob.o
>        vtable for Awl::MidiPanKnobin moc_midipanknob.o
>        vtable for KnobPluginin moc_awlplugin.o
>        vtable for VolKnobPluginin moc_awlplugin.o
>        vtable for PanKnobPluginin moc_awlplugin.o
>        vtable for MidiPanKnobPluginin moc_awlplugin.o
>        vtable for ColorLabelPluginin moc_awlplugin.o
>        vtable for AwlPluginsin moc_awlplugin.o
>        vtable for Awl::ColorLabelin moc_colorlabel.o
>    "QString::arg(QString const&, int, QChar const&) const", referenced
> from:
>        QDesignerCustomWidgetInterface::domXml() const in moc_awlplugin.o
>        QDesignerCustomWidgetInterface::domXml() const in moc_awlplugin.o
>        QDesignerCustomWidgetInterface::domXml() const in awlplugin.o
>        QDesignerCustomWidgetInterface::domXml() const in awlplugin.o
>    "QPainter::drawText(QRectF const&, int, QString const&, QRectF*)",
> referenced from:
>        Awl::Knob::paint(QRect const&)in knob.o
>    "QWidget::closeEvent(QCloseEvent*)", referenced from:
>        vtable for Awl::AbstractSliderin moc_aslider.o
>        vtable for Awl::Knobin moc_knob.o
>        vtable for Awl::PanKnobin moc_panknob.o
>        vtable for Awl::VolKnobin moc_volknob.o
>        vtable for Awl::MidiPanKnobin moc_midipanknob.o
>        vtable for Awl::ColorLabelin moc_colorlabel.o
>    "QPainter::~QPainter()", referenced from:
>        Awl::Knob::paint(QRect const&)in knob.o
>        Awl::ColorLabel::paintEvent(QPaintEvent*)       in colorlabel.o
>    "QWidget::sizeHint() const", referenced from:
>        vtable for Awl::AbstractSliderin moc_aslider.o
>    "QPainterPath::lineTo(QPointF const&)", referenced from:
>        QPainterPath::lineTo(double, double)in knob.o
>    "QListData::detach2()", referenced from:
>        QList<QDesignerCustomWidgetInterface*>::detach_helper()
> in awlplugin.o
>
> > Keep on trying !
>
> More things I've done since last mail: I've switched to using the SVN
> version, which seems a bit cleaner with less targets (no gendoc, etc).
> Still the same results, static libraries and smf2xml/xml2smf compile,
> but not libawlplugin.dylib and consequently not mscore.
>
> Another issue which needs to be resolved sooner or later: in
> utils.cpp, clock_gettime not found because it is not present in OS X
> version of time.h. Suggested portable alternative seems to be
> gettimeofday
> (http://www.nabble.com/gettimeofday-or-clock_gettime-td19367943.html ).
>
> Now I'm out of ideas,
> Johan


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Johan Pauwels-2

On 30 Nov 2008, at 16:20, Werner Schweer wrote:

> I guess you did not create&compile the qt moc generated files. All  
> header files,
> which contain classes derived from QObject and which contain an  
> Q_OBJECT macro
> must be processed with the qt utility "moc". The generated c++ files  
> must then
> be compiled and linked. If not you get linking errors complaining  
> about
> missing "vtable".
> The cmake generated makefiles take care of all this dependencies.
>

I guess so too, since I have no idea what you're talking about. Can  
you provide me with a link with more details on how to do that? But if  
the CMake generated makefiles are supposed to take care of that, it  
shouldn't be a problem, would it? Anyway, I tried in the end to  
compile it with the provided makefile and, unsurprisingly, it gave the  
same errors.

Johan

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

lasconic
Administrator
In reply to this post by Johan Pauwels-2


2008/11/30 Johan Pauwels <[hidden email]>

On 29 Nov 2008, at 23:15, Lasconic wrote:

I'm really really out of my base here. But is using Xcode necessary ? You can't install g++ and make and try the normal Linux way ?

This is the normal Mac way, Xcode is just a GUI which calls g++. CMake generates for every platform tools for building (as you know of course, just pointing it out for later reference) and for Mac this happens to be Xcode files. Generating command line OS X makefiles can be configured too, but assuming CMake is built for this purpose, it is safe to say that building with Xcode or make doesn't give any differences and as long as I get hundreds of errors, I prefer seeing them organized a bit in a window. If compiling this way works, I'll gladly look into using makefiles to be able to automate building, but it's going to need a custom makefile anyway, you can't just use the linux makefile (stupid example: option -shared needs to become -dynamic, but CMake should take care of this).


Thanks for the clarification. In the steps you give you said "generated an Xcode project using Xcode". You mean generating Xcode project with Cmake right ? How did you do that ?
Regarding moc... AS werner said some.h files, like those listed in mscore/mscore/CMakeLists.txt
QT4_WRAP_CPP (mocs
81 canvas.h editinstrument.h editstyle.h ........
Have to be process with moc, an executable of qt distrib before compilation. Again I'm out of my knowledge but just trying to guess, is there any documentation for the Xcode generator ? Can you see if "moc" is called ? and if not why ?





-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Joachim Ganseman
Hello everybody,

I started to play with the sources yesterday, and I just managed to get a 'skeleton' MacOS X build running - certainly not ready for publication, but I'll explain step by step what I did to get XCode partially up and running MuseScore. It might provide a start for further debugging.

Some of the steps underneath may be superfluous! This took a lot of trial and error, since I'm not familiar with Mac development, XCode, Qt, nor Cmake. Since the build time is quite long I did not check afterwards which steps could perhaps be skipped.

System: MacOS X 10.5 with XCode 3.1.2.

part 1: preliminary
- install CMake 2.6.2, installing the .dmg file will do just fine.
- install Qt 4.4.3, installing the .dmg file will do just fine.
- download the source from the trunk: svn co https://mscore.svn.sourceforge.net/svnroot/mscore/trunk mscore
- open a terminal, go to the source's main folder, run the following command: "./gen-qt-projectfile . >> mscore.pro"

part 2: editing the source (should perhaps be wrapped in #ifdefs in the svn)
- file all.h : change "values.h" to "limits.h"
- Qt for Mac does not have QX11Info. In file all.h, wrap the include (line 79) in an ifdef:
#ifdef Q_WS_X11
#include <QtGui/QX11Info>
#endif
- file mscore/select.cpp : change "values.h" to "limits.h"
- mac OSX uses sys/time.h just like MingW, but this needs to be incorporated. XCode on Mac defines the __APPLE__ macro. In file mscore/utils.cpp, change "#ifdef __MINGW__" on lines 21 and 358 to "#if defined (__MINGW32__) || defined (__APPLE__)"

part 3: editing the cmake files
There are some compilation errors due to dependencies that I have not yet figured out.
- for the "undefined interface" compile error, I added in the CMakeLists.txt in the main folder the following setting: "set(QT_USE_QTDESIGNER TRUE)"
- for the same error, in file awl/CMakeLists.txt I changed "if (NOT MINGW)" in
"if (NOT MINGW AND NOT APPLE)", and of course the same for the "endif" at the end of the file.
- because of linker errors in the QtScript modules, I edited a setting in the main folder CMakeLists.txt: "set(BUILD_SCRIPT_INTERFACE FALSE)" instead of TRUE.

part 4: generate and build:
- CMake can generate Xcode project files! In a terminal in the source's main folder, run the following command: "cmake -G Xcode". A file mscore.xcodeproj will appear. Open it, your XCode project is ready.
- Build-and-run everything in Release mode (though Debug did it too for me).
- The result should appear on your screen, without proper buttons nor fonts, but it runs!

Next steps would probably be:
- external resources: images, buttons, fonts, etc need to get working.
- the QtScript part. I don't know whether the unfound symbols need to be exported, or whether I missed a linked library. Since this part seemed to be optional, I edited it out earlier.
- linking: should be done statically on OsX, but is at the moment still dynamic. Ultimate goal would be a nice dmg package but I have no idea (yet) how to accomplish this.
- alsa, jack, ... ?

Probably the best idea to incorporate OSX support in the source tree in the future is to patch in the necessary #ifdefs where necessary in the code, tweak the CMakeLists.txt files where needed and just have a single build instruction, "cmake -G Xcode", generate the xcode project with everything already in the right place.

I hope this contributes a little!

Joachim Ganseman
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Thomas Bonte
Administrator
Hi Joachim,

Glad to see you kicked in! If you check the Changelog (https://mscore.svn.sourceforge.net/svnroot/mscore/trunk/mscore/ChangeLog) you will see that your post introduced some changes already in the repository. You can track svn commit via this feed: http://cia.vc/stats/project/mscore/.rss

Joachim Ganseman wrote
Hello everybody,

I started to play with the sources yesterday, and I just managed to get a 'skeleton' MacOS X build running - certainly not ready for publication, but I'll explain step by step what I did to get XCode partially up and running MuseScore. It might provide a start for further debugging.

Some of the steps underneath may be superfluous! This took a lot of trial and error, since I'm not familiar with Mac development, XCode, Qt, nor Cmake. Since the build time is quite long I did not check afterwards which steps could perhaps be skipped.

System: MacOS X 10.5 with XCode 3.1.2.

part 1: preliminary
- install CMake 2.6.2, installing the .dmg file will do just fine.
- install Qt 4.4.3, installing the .dmg file will do just fine.
- download the source from the trunk: svn co https://mscore.svn.sourceforge.net/svnroot/mscore/trunk mscore
- open a terminal, go to the source's main folder, run the following command: "./gen-qt-projectfile . >> mscore.pro"

part 2: editing the source (should perhaps be wrapped in #ifdefs in the svn)
- file all.h : change "values.h" to "limits.h"
- Qt for Mac does not have QX11Info. In file all.h, wrap the include (line 79) in an ifdef:
#ifdef Q_WS_X11
#include <QtGui/QX11Info>
#endif
- file mscore/select.cpp : change "values.h" to "limits.h"
- mac OSX uses sys/time.h just like MingW, but this needs to be incorporated. XCode on Mac defines the __APPLE__ macro. In file mscore/utils.cpp, change "#ifdef __MINGW__" on lines 21 and 358 to "#if defined (__MINGW32__) || defined (__APPLE__)"

part 3: editing the cmake files
There are some compilation errors due to dependencies that I have not yet figured out.
- for the "undefined interface" compile error, I added in the CMakeLists.txt in the main folder the following setting: "set(QT_USE_QTDESIGNER TRUE)"
- for the same error, in file awl/CMakeLists.txt I changed "if (NOT MINGW)" in
"if (NOT MINGW AND NOT APPLE)", and of course the same for the "endif" at the end of the file.
- because of linker errors in the QtScript modules, I edited a setting in the main folder CMakeLists.txt: "set(BUILD_SCRIPT_INTERFACE FALSE)" instead of TRUE.

part 4: generate and build:
- CMake can generate Xcode project files! In a terminal in the source's main folder, run the following command: "cmake -G Xcode". A file mscore.xcodeproj will appear. Open it, your XCode project is ready.
- Build-and-run everything in Release mode (though Debug did it too for me).
- The result should appear on your screen, without proper buttons nor fonts, but it runs!

Next steps would probably be:
- external resources: images, buttons, fonts, etc need to get working.
- the QtScript part. I don't know whether the unfound symbols need to be exported, or whether I missed a linked library. Since this part seemed to be optional, I edited it out earlier.
- linking: should be done statically on OsX, but is at the moment still dynamic. Ultimate goal would be a nice dmg package but I have no idea (yet) how to accomplish this.
- alsa, jack, ... ?

Probably the best idea to incorporate OSX support in the source tree in the future is to patch in the necessary #ifdefs where necessary in the code, tweak the CMakeLists.txt files where needed and just have a single build instruction, "cmake -G Xcode", generate the xcode project with everything already in the right place.

I hope this contributes a little!

Joachim Ganseman
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x -> screenshots

Thomas Bonte
Administrator
In reply to this post by Joachim Ganseman
From Joachim (wrongly sent only to me)

Hi,

I've put 2 screenshots here:
http://picasaweb.google.be/musicalign/Musescore_mac1#
One is a screenshot of how it opens from the beginning, in the second
I opened an old Finale-generated MusicXML file of myself, and scott
joplin's elite syncopations. import seems to work fine, and I can drag
the 'notes' (though square) around too. I'll try get things up and
running a little better during this weekend.

Joachim
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x -> screenshots

Frye
I have tried to build revision 1346. However when I'm generating the Xcode project file I'm getting this error about palette.ui file missing. And I cannot find it under mscore directory. Am I missing something? Also the build process gives a bunch of errors regarding this.

-Samuli

QT_LIBRARIES  
Disabling ALSA support due to OS X or MINGW build.
Jack detected
portaudio detected
-- Configuring done
-- Generating done
CMake Error in mscore/CMakeLists.txt:
  Cannot find source file "palette.ui".  Tried extensions .c .C .c++ .cc .cpp
  .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx


-- Build files have been written to: /Users/samujarv/devel/mscore-build/mscore
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x -> screenshots

wschweer
Administrator
Sorry, i forgot to add the file to svn.

Werner

Am Donnerstag 04 Dezember 2008 21:13:31 schrieb Frye:

> I have tried to build revision 1346. However when I'm generating the Xcode
> project file I'm getting this error about palette.ui file missing. And I
> cannot find it under mscore directory. Am I missing something? Also the
> build process gives a bunch of errors regarding this.
>
> -Samuli
>
> QT_LIBRARIES
> Disabling ALSA support due to OS X or MINGW build.
> Jack detected
> portaudio detected
> -- Configuring done
> -- Generating done
> CMake Error in mscore/CMakeLists.txt:
>   Cannot find source file "palette.ui".  Tried extensions .c .C .c++ .cc
> .cpp
>   .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx
>
>
> -- Build files have been written to:
> /Users/samujarv/devel/mscore-build/mscore


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x -> screenshots

Frye
Now the file is there and I get a bit longer, but for some reason the build fails with errors regarding alsa. I don't have enough time to look into this today, however the camake output says that it is disabling alsa. And still during the build I get these errors. So it seems like the alsa is not completely disabled. But as I said this is just a hunch. It seems that alsa.h is included in jackaudio.cpp, but I don't have time to look into it more today.

-Samuli

Line Location alsa.h:38: error: alsa/asoundlib.h: No such file or directory
Line Location alsa.h:51: error: 'snd_pcm_hw_params_t' has not been declared
Line Location alsa.h:51: error: 'snd_pcm_t' has not been declared
Line Location alsa.h:52: error: 'snd_pcm_sw_params_t' has not been declared
Line Location alsa.h:52: error: 'snd_pcm_t' has not been declared
Line Location alsa.h:56: error: 'snd_pcm_uframes_t' does not name a type
Line Location alsa.h:58: error: 'snd_pcm_format_t' does not name a type
Line Location alsa.h:59: error: 'snd_pcm_access_t' does not name a type
Line Location alsa.h:60: error: expected ';' before '*' token
Line Location alsa.h:60: error: ISO C++ forbids declaration of 'snd_pcm_t' with no type
Line Location alsa.h:61: error: ISO C++ forbids declaration of 'snd_pcm_hw_params_t' with no type
Line Location alsa.h:61: error: expected ';' before '*' token
Line Location alsa.h:62: error: ISO C++ forbids declaration of 'snd_pcm_sw_params_t' with no type
Line Location alsa.h:62: error: expected ';' before '*' token
Line Location alsa.h:65: error: field '_pfd' has incomplete type
Line Location alsa.h:66: error: 'snd_pcm_uframes_t' does not name a type
Line Location alsa.h:67: error: 'snd_pcm_uframes_t' does not name a type
Line Location alsa.h:82: error: 'snd_pcm_uframes_t' has not been declared
Line Location alsa.h:83: error: 'snd_pcm_sframes_t' does not name a type
Line Location alsa.h:84: error: ISO C++ forbids declaration of 'snd_pcm_t' with no type
Line Location alsa.h:84: error: expected ';' before '*' token
Line Location alsa.h:85: error: expected `;' before 'void'
Line Location alsa.h:85: error: 'snd_pcm_uframes_t' has not been declared
Line Location alsa.h:90: error: 'snd_pcm_uframes_t' has not been declared
Line Location alsa.h:96: error: 'snd_pcm_uframes_t' does not name a type


wschweer wrote
Sorry, i forgot to add the file to svn.

Werner
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Frye
-- Configuring done
CMake Error in mscore/CMakeLists.txt:
  Cannot find source file "resfile.o".  Tried extensions .c .C .c++ .cc .cpp
  .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx

This is when I am running cmake -G Xcode and revision is 1351.

I tried with few older revisions and this seems to go back up to 1347. 1348 is the first revision that gives this error.

-Samuli
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

lasconic
Administrator
Maybe the problem was introduced here : http://mscore.svn.sourceforge.net/viewvc/mscore/trunk/mscore/mscore/CMakeLists.txt?r1=1348&r2=1347&pathrev=1348

2008/12/7 Frye <[hidden email]>

-- Configuring done
CMake Error in mscore/CMakeLists.txt:
 Cannot find source file "resfile.o".  Tried extensions .c .C .c++ .cc .cpp
 .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx

This is when I am running cmake -G Xcode and revision is 1351.

I tried with few older revisions and this seems to go back up to 1347. 1348
is the first revision that gives this error.

-Samuli
--
View this message in context: http://n2.nabble.com/build-for-mac-os-x-tp1499960p1625473.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

Frye
Yep, is this resfile something I need to generate or should it be there already?

lasconic wrote
Maybe the problem was introduced here :
http://mscore.svn.sourceforge.net/viewvc/mscore/trunk/mscore/mscore/CMakeLists.txt?r1=1348&r2=1347&pathrev=1348

2008/12/7 Frye <samuli.jarvinen@gmail.com>

>
> -- Configuring done
> CMake Error in mscore/CMakeLists.txt:
>  Cannot find source file "resfile.o".  Tried extensions .c .C .c++ .cc .cpp
>  .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx
>
> This is when I am running cmake -G Xcode and revision is 1351.
>
> I tried with few older revisions and this seems to go back up to 1347. 1348
> is the first revision that gives this error.
>
> -Samuli
> --
> View this message in context:
> http://n2.nabble.com/build-for-mac-os-x-tp1499960p1625473.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
>
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|

Re: build for mac os x

lasconic
Administrator
I think that  the .o file will be generated on compilation so in the next step... You can try to remove the APPLE flag in the IF ELSE ENDIF statement I guess.


2008/12/7 Frye <[hidden email]>

Yep, is this resfile something I need to generate or should it be there
already?


lasconic wrote:
>
> Maybe the problem was introduced here :
> http://mscore.svn.sourceforge.net/viewvc/mscore/trunk/mscore/mscore/CMakeLists.txt?r1=1348&r2=1347&pathrev=1348
>
> 2008/12/7 Frye <[hidden email]>
>
>>
>> -- Configuring done
>> CMake Error in mscore/CMakeLists.txt:
>>  Cannot find source file "resfile.o".  Tried extensions .c .C .c++ .cc
>> .cpp
>>  .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx
>>
>> This is when I am running cmake -G Xcode and revision is 1351.
>>
>> I tried with few older revisions and this seems to go back up to 1347.
>> 1348
>> is the first revision that gives this error.
>>
>> -Samuli
>> --
>> View this message in context:
>> http://n2.nabble.com/build-for-mac-os-x-tp1499960p1625473.html
>> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
>> Nevada.
>> The future of the web can't happen without you.  Join us at MIX09 to help
>> pave the way to the Next Web now. Learn more and register at
>>
>> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
>> _______________________________________________
>> Mscore-developer mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>>
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
> Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Mscore-developer mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>

--
View this message in context: http://n2.nabble.com/build-for-mac-os-x-tp1499960p1625497.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
123