Hello Philipp,<br><br><div class="gmail_quote">2010/12/23 Philipp Überbacher <span dir="ltr">&lt;<a href="mailto:hollunder@lavabit.com">hollunder@lavabit.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div class="h5"><br>
</div></div>Hi there,<br>
I tried building muse to give it a spin today, but the build failed:<br>
<br>
Linking CXX shared library libmuse_core.so<br>midiedit/libmuse_midiedit.so: undefined reference to<br>make: *** [all] Error 2<br>
    Aborting...<br></blockquote><div><br></div><div>Hmm, no idea why this happens for you. Perhaps Orcan has some idea?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Anyway, upfront a couple of questions/suggestions.<br>
<br>
website:<br>
- Part Import/Export &lt;- what does this refer to?<br></blockquote><div><br></div><div>Midi-parts are xml based and can be stored and retrieved from disk. This gives the possibility to produce a library of parts. Creating a public library of parts (mainly for drums) has been discussed.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
- Several types of audio tracks<br>
      * Audio inputs<br>
      * Audio outputs<br>
      * Wave tracks    &lt;- those sound weird, I hope I don&#39;t need to<br></blockquote><div><br></div><div>They are regular tracks where you can put/record wave-parts, if you tried older versions of MusE this is nothing new.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
create separate tracks for everything<br>
- the following link (found here:<br>
  <a href="http://muse-sequencer.org/index.php/Download" target="_blank">http://muse-sequencer.org/index.php/Download</a>) is more distracting than anything:<br>
  <a href="http://sourceforge.net/scm/?type=svn&amp;group_id=93414" target="_blank">http://sourceforge.net/scm/?type=svn&amp;group_id=93414</a></blockquote><div><br></div><div>Too much information? It&#39;s the standard sourceforge page, though you may be right, we should probably rework that in the wiki.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
building:<br>
you seem to have switched to cmake but half way it seems. The build<br>
instructions are rather weird and unusual for cmake.<br>
creating build, cd&#39;ing there and invoking cmake .. is not how it&#39;s<br>
usually done.<br>
Usually you configure using &#39;ccmake .&#39; when you build manually or<br>
-DCMAKE_BLA (which you do use) for automatic building.<br>
A DESTDIR is a good thing to have since often enough software<br>
is build in a chroot and hence &quot;make install&quot; as root will fail if it<br>
tries to install into the real /usr.<br></blockquote><div><br></div><div>I&#39;m not convinced there is a usual way. Though you are right we are beginners with cmake and it can probably be improved. </div><div>ccmake is just a curses frontend is it not? You can try to convince me but instinctively I think we should steer clear of gui tools for building.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Well, I&#39;m looking forward to using a hopefully improved muse :)<br></blockquote><div><br></div><div>Thank you, we will try to improve the build and get it compiling on all systems we can :)</div><div><br></div><div>Regards,</div>
<div>Robert</div><div><br></div></div>