Hi!<div><br></div><div>I'll try to write in english because I dont want give you more work. But, I warn that my english is very very bad.</div><div><br></div><div>First of all, the way that I 'fixed' the id3lib to make it install was change the configuration of mac ports, not really a patch. I changed the configuration of the architectures to compile in the "universal" variant. It was set to "x86_64 i386", and I seted temporally to "x86_64". It's not a good solution, and probably, that library will not work on 32bit systems. But, I didn't want to spend a lot of time on it. Anyway, I think that I'm building the library for the x86_64 architecture because I'm not using any kind of cross compiling directive, but I'm not sure what is the default architecture of the compiler.</div>
<div><br></div><div>I think that a solution for the qt4-mac executables suffixes is add a line in clam/CLAM/scons/sconstools/qt4.py after line 226:</div><div><div><font face="'courier new', monospace">219</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">def locateQt4Command(env, command, qtdir) :</font></div>
<div><font face="'courier new', monospace">220</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">suffixes = [</font></div>
<div><font face="'courier new', monospace">221</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">'-qt4',</font></div>
<div><font face="'courier new', monospace">222</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">'-qt4.exe',</font></div>
<div><font face="'courier new', monospace">223</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">'4',</font></div>
<div><font face="'courier new', monospace">224</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">'4.exe',</font></div>
<div><font face="'courier new', monospace">225</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">'',</font></div>
<div><font face="'courier new', monospace">226</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">'.exe',</font></div>
<div><div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">'-mac',</font></div>
</div><div><font face="'courier new', monospace">227</font><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">]</font></div>
</div><div><br></div><div>I think it will work fine meanwhile the qt4 project fix the <span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse">pkg-config bug, a</span>nd I think that it's better solution than the unsuffixed symbolic links.</div>
<div><br></div><div>Second, I've found why scons doesn't include the soname link while compiles the bundle. It's because there is a bug in a scons script of the main lib, and it doesn't create the soname link during the install. The bug is in file clam/CLAM/scons/libs/clam_build_helpers.py at line 358 and in the file scons/sconstools/clam.py at line 186 too:</div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">def generate_so_name( target, source, env ) :</font></div><div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">source_dir = os.path.dirname( str(source[0]) )</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">cwd = os.getcwd()</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">os.chdir( source_dir )</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">if sys.platform == 'linux2' :</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">os.system( "/sbin/ldconfig -n ." )</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">os.chdir(cwd)</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">return None</font></div>
</div><div>I've modified it to:</div><div><div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">def generate_so_name( target, source, env ) :</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">if sys.platform == 'linux2' :</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">source_dir = os.path.dirname( str(source[0]) )</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">cwd = os.getcwd()</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">os.chdir( source_dir )</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">os.system( "/sbin/ldconfig -n ." )</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">os.chdir(cwd)</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">elif sys.platform == 'darwin':</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">source_file = os.path.basename( str(source[0]) )</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">os.system( "ln -sf %s %s"%(source_file,str(target[0]) ))</font></div>
<div><span style="white-space:pre-wrap"><font face="'courier new', monospace"> </font></span><font face="'courier new', monospace">return None</font></div>
</div><div><br></div><div>With this changes, I could build the Annotator.app, NetworkEditor.app and Chordata.app bundles, and all of them include their dependencies. But now, they crashes when they init the qt lib. I'm attaching the log that the OS throws. I didn't ever work with Qt, and I don't know why it crashes, maybe some non-binary dependencies not included in the bundle.</div>
<div><br></div><div>The problem what I've experienced compiling Chordata was because I didn't make the "scons install" of the networkeditor app :P </div><div><br></div><div>
I don't have so much time, and I don't know if I could lead :S ......but I still try to spend some time if I could.</div><div><br></div><div>Roberto.</div><div><br></div><div><div class="gmail_quote">On Fri, Jun 18, 2010 at 9:30 AM, David García Garzón <span dir="ltr"><<a href="mailto:david.garcia@barcelonamedia.org" target="_blank">david.garcia@barcelonamedia.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Translated in short. Context: compiling in mac 'snow leopard'.<br>
<div><br>
On Friday 18 June 2010 01:08:42 Roberto Chauderlot Marchamalo wrote:<br>
> Hello again!<br>
><br>
> Os escribo en español otra vez....sorry.<br>
><br>
> He hecho avances intentando compilar la librería. De hecho, lo que es la<br>
> librería en sí, ya la he conseguido compilar.<br>
><br>
> Primero quería comentaros que he tenido algún problemilla con las<br>
> dependencias que pone en la wiki que hay que instalar. Primero, las<br>
> librerías xercesc y id3lib, no compilan en mi snow leopard. Creo que es<br>
> debido a que en macports están teniendo algún problema con el snow leopard<br>
> y la arquitectura i386, y hay cosas que no compilan bien. Solucionar el<br>
> problema de la primera librería fue fácil, existe un paquete que se llama<br>
> xercesc3 (en vez de xercesc a secas, como pone en la wiki, que es para la<br>
> versión 2), y este compila bien. Para arreglar la librería id3lib, he<br>
> tenido que hacer un pequeño apaño y no compilarlo para la arquitectura<br>
> i386, y hacerlo sólo para la x86_64. Espero que esto no acarree<br>
> consecuencias después.<br>
<br>
</div>Trans: problems with xercesc and id3lib; installed xercesc3, id3lib patched.<br>
<br>
Comment: we moved to xercesc3 recently so the option you took is the correct.<br>
Would be nice if you send the id3lib patch to the list and to the macport<br>
maintainers.<br>
<div><br>
> Por cierto, también os quería comentar que en la wiki sólo indica la manera<br>
> "deprecated" de instalar jack. Ahora mismo está paqueteado, y se puede<br>
> instalar fácilmente con un "sudo port install jack". Y tampoco se comenta<br>
> nada de instalar portmidi, que también está paqueteado y sería lo mismo<br>
> "sudo port install portmidi". Todo se puede instalar desde macports.<br>
<br>
</div>Trans: jack and portmidi are available now as ports.<br>
<br>
Comment: Feel free to update the wiki yourself. If the old methods still have<br>
sense for old mac version you can move them to a chapter in the end. If the<br>
macports are available for all the versions, just remove those paragraphs.<br>
<div><br>
> Después compilé la librería en sí, y sin problemas. Pero el resto de<br>
> aplicaciones sí me ha dado problemas. Primero es que, el paquete de<br>
> qt4-mac que hay en macports llama a todos los ejecutables de qt con el<br>
> sufijo "-mac" (moc-mac, uic-mac, rcc-mac, lupdate-mac, lrelease-mac, etc),<br>
> y los scripts de compilación buscan los normales. Y como no tengo ni idea<br>
> de scons, lo solucioné creando enlaces simbólicos con los nombres 'linux'<br>
> apuntando a los de mac y añadiendo las siguientes variable de entorno:<br>
> export QTDIR=/opt/local/bin<br>
> export PKG_CONFIG_PATH=/opt/local/libexec/qt4-mac/lib/pkgconfig/<br>
> (supongo que habría que poner en la wiki lo de las variables y para lo de<br>
> los ejecutables supongo que habría que modificar los scripts :S)<br>
<br>
</div>Trans: clam libs compiled with no problem, apps gave problems with qt, qt4-mac<br>
suffixes -mac all the binaries. He fixed it by adding unsuffixed links and<br>
defining QTDIR and PKG_CONFIG_PATH as above.<br>
<br>
Comment: The perfect solution would be using pkg-config to locate the qt<br>
binaries and just setting the PKG_CONFIG_PATH. The problem is that rcc,<br>
lupdate, lrelease can not be taken from the pkg-config by now. I want to file<br>
a bug in qt. Meanwhile your option should work.<br>
<div><br>
> Luego, el programa NetworkEditor, tiene como parámetro la aplicación<br>
> QtDesigner.app, pero en el paquete qt4-mac de macports ya no viene en<br>
> forma de bundle '.app' (pero sí que es invocable desde la consola). Así<br>
> que, aunque lo he compilado no me deja crear el paquete.<br>
<br>
</div>Trans: QtDesigner is no more a bundle so the package build which ask for the<br>
builder fails.<br>
<br>
Comment: No idea of the implications of QtDesigner not being a bundle on how<br>
we should package it. Any other mac developer reading?<br>
<div><div></div><div><br>
> Después, el SMSTools no me deja compilarlo porque dice que no encuentra<br>
> unas cabeceras (de qt): Macario:SMSTools chauder$ scons prefix=/opt/local<br>
> clam_prefix=/opt/local release=1 scons: Reading SConscript files ...<br>
> Loading nsis tool...<br>
> Loading Bundle tool<br>
> Lodading dmg tool...<br>
> Version: 0.4.13<br>
> Package version: 0.4.13~svn14280<br>
> scons: done reading SConscript files.<br>
> scons: Building targets ...<br>
> == Compiling vmqt/CLAM/QtWaitMessageImpl.cxx<br>
> vmqt/CLAM/QtWaitMessageImpl.cxx:1:21: error: qlayout.h: No such file or<br>
> directory vmqt/CLAM/QtWaitMessageImpl.cxx:2:20: error: qlabel.h: No such<br>
> file or directory vmqt/CLAM/QtWaitMessageImpl.cxx:3:20: error: qtimer.h:<br>
> No such file or directory In file included from<br>
> vmqt/CLAM/QtWaitMessageImpl.cxx:4:<br>
> vmqt/CLAM/WaitMsgIndicator.hxx:4:20: error: qframe.h: No such file or<br>
> directory In file included from vmqt/CLAM/QtWaitMessageImpl.cxx:5:<br>
> vmqt/CLAM/QtWaitMessageImpl.hxx:5:21: error: qdialog.h: No such file or<br>
> directory In file included from vmqt/CLAM/QtWaitMessageImpl.cxx:4:<br>
> vmqt/CLAM/WaitMsgIndicator.hxx:11: error: expected class-name before ‘{’<br>
> token vmqt/CLAM/WaitMsgIndicator.hxx:12: error: ISO C++ forbids<br>
> declaration of ‘Q_OBJECT’ with no type vmqt/CLAM/WaitMsgIndicator.hxx:13:<br>
> error: expected ‘;’ before ‘public’ vmqt/CLAM/WaitMsgIndicator.hxx:17:<br>
> error: expected `:' before ‘slots’ vmqt/CLAM/WaitMsgIndicator.hxx:18:<br>
> error: expected primary-expression before ‘void’<br>
> vmqt/CLAM/WaitMsgIndicator.hxx:18: error: ISO C++ forbids declaration of<br>
> ‘slots’ with no type vmqt/CLAM/WaitMsgIndicator.hxx:18: error: expected<br>
> ‘;’ before ‘void’ vmqt/CLAM/WaitMsgIndicator.hxx:21: error: ‘QPaintEvent’<br>
> has not been declared In file included from<br>
> vmqt/CLAM/QtWaitMessageImpl.cxx:5:<br>
> vmqt/CLAM/QtWaitMessageImpl.hxx:16: error: expected class-name before ‘{’<br>
> token vmqt/CLAM/QtWaitMessageImpl.hxx:18: error: expected `)' before ‘*’<br>
> token vmqt/CLAM/QtWaitMessageImpl.hxx:24: error: ‘QCloseEvent’ has not<br>
> been declared vmqt/CLAM/QtWaitMessageImpl.cxx:11: error: expected `)'<br>
> before ‘*’ token vmqt/CLAM/QtWaitMessageImpl.cxx: In member function ‘void<br>
> CLAM::VM::QtWaitMessageImpl::LabelText(const std::string&)’:<br>
> vmqt/CLAM/QtWaitMessageImpl.cxx:32: error: invalid use of incomplete type<br>
> ‘struct QLabel’ vmqt/CLAM/QtWaitMessageImpl.hxx:7: error: forward<br>
> declaration of ‘struct QLabel’ vmqt/CLAM/QtWaitMessageImpl.cxx: At global<br>
> scope:<br>
> vmqt/CLAM/QtWaitMessageImpl.cxx:35: error: variable or field ‘closeEvent’<br>
> declared void vmqt/CLAM/QtWaitMessageImpl.cxx:35: error: ‘QCloseEvent’ was<br>
> not declared in this scope vmqt/CLAM/QtWaitMessageImpl.cxx:35: error: ‘e’<br>
> was not declared in this scope scons: *** [vmqt/CLAM/QtWaitMessageImpl.o]<br>
> Error 1<br>
> scons: building terminated because of errors.<br>
><br>
> Supongo que esto se arreglará instalando el qt4-mac-devel, que no lo<br>
> instalé porque en la wiki no lo decía y todavía no he tenido tiempo (el<br>
> qt4-mac me tardó unas 8 horas en instalarse, esto tardará.......).<br>
<br>
</div></div>Trans: Problems compiling SMSTools with the output above, maybe a missing<br>
install for qt4-mac-devel?<br>
<br>
Comment: Maybe. They might have split the package but then no qt app should<br>
compile. A more likely reason is the way SMSTools includes Qt without the<br>
QtGui/ QtCore/... prefixes. That would highlight a bug in the qt4.py tool we<br>
provide when specifying the CPPPATH. If Qt includes are in /what/ever/include<br>
that directory and also /what/ever/include/{QtGui,QtCore,...} should be added.<br>
Try to compile with the verbose=1 option and send the command line to see<br>
which -I options appear.<br>
<div><br>
> Luego seguí con Annotator, que si que compiló, creo la aplicación ".app" y<br>
> un dmg para instalarlo, pero cuando intentas ejecutarlo dice que faltan 3<br>
> librerías que no están en el paquete: libclam_core.1.4.dylib<br>
> libclam_processing.1.4.dylib<br>
> libclam_audioio.1.4.dylib<br>
> Y por lo que he visto es el script de compilación el que no las copia :S Lo<br>
> he intentado hacer a mano de las que he encontrado en /opt/local/lib/<br>
> pero, primero sólo encuentro la versión 1.4.1, y que luego, incluir esas<br>
> versiones, la aplicación me empieza a pedir las librerías en /opt/local/ y<br>
> no debería. Dyld Error Message:<br>
> Library not loaded: /opt/local//lib/libclam_core.1.4.dylib<br>
> Referenced from:<br>
> /Users/chauder/Documents/Proyectos/clam/clam/Annotator/Annotator.app/Conte<br>
> nts/MacOS/../Frameworks/libclam_audioio.1.4.dylib Igual, si vuelvo a<br>
> compilar la librería con la opción de sandbox, esto se soluciona.<br>
<br>
</div>Trans: Annotator creates the dmg but when installed it complains about missing<br>
libraries.<br>
<br>
Comment: We changed the way to name libraries including mac but we didn't test<br>
mac. So sorry for the inconvenience. Maybe what is missing is a 'soname' link<br>
with that name pointing to the fully versioned library. If that solves the<br>
problem tell me and i will add the step in the scons.<br>
<div><div></div><div><br>
> Es script de compilación de chordata no deja tampoco, me da el siguiente<br>
> error: Macario:chordata chauder$<br>
> PKG_CONFIG_PATH=/opt/local/libexec/qt4-mac/lib/pkgconfig/:/Users/chauder/D<br>
> ocuments/Proyectos/clam/clam/NetworkEditor/ scons prefix=/opt/local<br>
> clam_prefix=/opt/local release=1 scons: Reading SConscript files ...<br>
> Loading nsis tool...<br>
> Loading Bundle tool<br>
> Lodading dmg tool...<br>
> Version: 1.1.0<br>
> Package version: 1.1.0~svn14280<br>
> Package clam_qtmonitors was not found in the pkg-config search path.<br>
> Perhaps you should add the directory containing `clam_qtmonitors.pc'<br>
> to the PKG_CONFIG_PATH environment variable<br>
> No package 'clam_qtmonitors' found<br>
> OSError: 'PKG_CONFIG_PATH=/opt/local/lib/pkgconfig pkg-config clam_core<br>
> clam_audioio clam_processing clam_qtmonitors --libs --cflags' exited 1:<br>
> File "/Users/chauder/Documents/Proyectos/clam/clam/chordata/SConstruct",<br>
> line 70: ], CLAMInstallDir)<br>
> File<br>
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/scons-1.3<br>
> .0/SCons/Environment.py", line 224: return apply(self.method, nargs,<br>
> kwargs)<br>
> File "/opt/local/share/clam/sconstools/clam.py", line 166:<br>
> ' '.join(libs)))<br>
> File<br>
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/scons-1.3<br>
> .0/SCons/Environment.py", line 1477: return function(self,<br>
> self.backtick(command))<br>
> File<br>
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/scons-1.3<br>
> .0/SCons/Environment.py", line 596: raise OSError("'%s' exited %d" %<br>
> (command, status))<br>
> Yo le pongo la variable de entorno que pide, pero el script la<br>
> sobreescribe. Así que no funciona.<br>
<br>
</div></div>Trans: chordata fails to locate<br>
<br>
Comment: it complains about a library qtmonitor that is installed with<br>
NetworkEditor. Maybe you should 'scons install' NetworkEditor and then try<br>
compile chordata. Anyway no guarantees that the chordata bundle will work at<br>
all. Some scons hacking could be needed to include such library in the bundle.<br>
<div><br>
> Y luego el programa Voice2Midi tiene las directivas de compilación para<br>
> crear el "distribuible" a medio hacer.<br>
<br>
</div>Trans: Voice2Midi is work in progress.<br>
<br>
Comment: I guess we never really addressed Voice2Midi on mac.<br>
<div><br>
> Así que después de una larga sesión de compilacion, no he conseguido nada<br>
> útil. Pero espero que a vosotros si que os sea útil este feedback.<br>
><br>
> Si tengo un poco de tiempo libre intento aprender scons y os ayudo con los<br>
> scripts, que están un poco desastrillos :P<br>
<br>
</div>Trans: Nothing useful from compilation. He will help as he gets expertise with<br>
scons.<br>
<br>
Sorry, Roberto, for the inconveniences. Thanks for your effort. The mac<br>
platform needs some love. We would be very grateful if you take the lead on<br>
that. We will help you as most as we can with scons or any other problem it<br>
could jump.<br>
<br>
I hope that, by adding the soname links, you will be able to run dmg's that<br>
built. Are the binaries you built without dmg, at least, runnable?<br>
<br>
David.<br>
<div><br>
<br>
<br>
> On Mon, Jun 7, 2010 at 3:35 PM, David García Garzón<br>
</div>> <<a href="mailto:david.garcia@barcelonamedia.org" target="_blank">david.garcia@barcelonamedia.org</a><mailto:<a href="mailto:david.garcia@barcelonamedia.org" target="_blank">david.garcia@barcelonamedia.org</a>>><br>
<div>> wrote:<br>
><br>
> On Monday 07 June 2010 14:33:03 Roberto Chauderlot Marchamalo wrote:<br>
> > Hello,<br>
> > Pau, I'll try it. I have windows and linux devel skills but no<br>
> > experience with the mac development enviroment. But, I'm interested in<br>
> > learning hat enviroment :D<br>
> > David, yes I've followed the link on the mac os x build page of the<br>
> > wiki: <a href="http://clam-project.org/wiki/Devel/Mac_OSX_build" target="_blank">http://clam-project.org/wiki/Devel/Mac_OSX_build</a> It has this<br>
> > text:<br>
> ><br>
> > "You can choose either download a source tarball from the clam website:<br>
> ><br>
> > <a href="http://clam.iua.upf.edu//download-source.html" target="_blank">http://clam.iua.upf.edu//download-source.html</a><br>
> ><br>
> > or get the latest version of subversion. In this case you'll also need<br>
> ><br>
> > to install subversion macport:<br>
> > $ sudo port install subversion<br>
> > $ svn co <a href="http://iua-share.upf.edu/svn/clam/trunk" target="_blank">http://iua-share.upf.edu/svn/clam/trunk</a>"<br>
> ><br>
> > thank you!<br>
><br>
> I fixed it. Thanks.<br>
><br>
> > 2010/6/7 David García Garzón<br>
</div>> > <<a href="mailto:david.garcia@barcelonamedia.org" target="_blank">david.garcia@barcelonamedia.org</a><mailto:<a href="mailto:david.garcia@barcelonamedia.org" target="_blank">david.garcia@barcelonamedia.org</a>><br>
<div><div></div><div>> > ><br>
> ><br>
> > > BTW, Roberto, did you take the wrong link from any clam related page we<br>
> > > could fix?<br>
> > ><br>
> > > David.<br>
> > ><br>
> > > On Monday 07 June 2010 10:43:49 Pau Arumí wrote:<br>
> > > > clam is not longer hosted at iua since long time ago. clam lives in<br>
> > > > <a href="http://clam-project.org" target="_blank">http://clam-project.org</a><br>
> > > > we used to have a redirection to but it is no longer active.<br>
> > > ><br>
> > > > about generating mac binaries, you are welcomed. it is basically<br>
> > > > documented <a href="http://clam-project.org/wiki/Devel/Mac_OSX_build" target="_blank">http://clam-project.org/wiki/Devel/Mac_OSX_build</a><br>
> > > > but requires some development experience.<br>
> > > ><br>
> > > > P<br>
> > > ><br>
> > > > El dl 07 de 06 de 2010 a les 05:49 +0200, en/na Roberto va escriure:<br>
> > > > > Hola!!<br>
> > > > ><br>
> > > > ><br>
> > > > > Perdonad que os escriba en español, pero es que no me manejo muy<br>
> > > > > bien con el ingles. Pero espero que esto no suponga un problema :P<br>
> > > > ><br>
> > > > ><br>
> > > > > He visto publicado el programa CHORDATA en varios blogs de guitarra<br>
> > > > > y me ha encantado. Llevaba años buscando una herramienta similar,<br>
> > > > > incluso, empecé a programar algo parecido en matlab años atrás.<br>
> > > > > Pero nunca llegué a hacer nada funcional (en otro lenguaje) por<br>
> > > > > falta de tiempo. Así que, os felicito por el proyecto!!!! Me<br>
> > > > > encanta.<br>
> > > > ><br>
> > > > ><br>
> > > > > He leido en un blog, que no habéis sacado versión para mac del<br>
> > > > > chordata porque no tenéis ninguna máquina mac a mano. Pues, si<br>
> > > > > queréis yo os hago el binario para mac. Tengo un macbook blanquito<br>
> > > > > aunque no he desarrollado nunca para mac. He intentado bajarme el<br>
> > > > > código de <a href="http://clam.iua.upf.edu/download-source.html" target="_blank">http://clam.iua.upf.edu/download-source.html</a> pero me ha<br>
> > > > > dado un bonito error 500, así que no he podido probar a compilar<br>
> > > > > nada.<br>
> > > > ><br>
> > > > ><br>
> > > > > Entonces, si queréis que os ayude generando la versión para mac, yo<br>
> > > > > encantado, que le daré buen uso ;)<br>
> > > > ><br>
> > > > ><br>
> > > > > Un saludo!<br>
> > > > > Roberto<br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > clam-devel mailing list<br>
</div></div>> > > > <a href="mailto:clam-devel@lists.clam-project.org" target="_blank">clam-devel@lists.clam-project.org</a><mailto:<a href="mailto:clam-devel@lists.clam-projec" target="_blank">clam-devel@lists.clam-projec</a><br>
<div>> > > > <a href="http://t.org" target="_blank">t.org</a>><br>
> > > > <a href="http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.o" target="_blank">http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.o</a><br>
> > > > rg<br>
> > ><br>
> > > _______________________________________________<br>
> > > clam-devel mailing list<br>
</div>> > > <a href="mailto:clam-devel@lists.clam-project.org" target="_blank">clam-devel@lists.clam-project.org</a><mailto:<a href="mailto:clam-devel@lists.clam-project" target="_blank">clam-devel@lists.clam-project</a>.<br>
<div>> > > org><br>
> > > <a href="http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org" target="_blank">http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org</a><br>
> ><br>
> > _______________________________________________<br>
> > clam-devel mailing list<br>
</div>> > <a href="mailto:clam-devel@lists.clam-project.org" target="_blank">clam-devel@lists.clam-project.org</a><mailto:<a href="mailto:clam-devel@lists.clam-project.or" target="_blank">clam-devel@lists.clam-project.or</a><br>
> > g> <a href="http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org" target="_blank">http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org</a><br>
><br>
> _______________________________________________<br>
> clam-devel mailing list<br>
> <a href="mailto:clam-devel@lists.clam-project.org" target="_blank">clam-devel@lists.clam-project.org</a><mailto:<a href="mailto:clam-devel@lists.clam-project.org" target="_blank">clam-devel@lists.clam-project.org</a>><br>
<div><div></div><div>> <a href="http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org" target="_blank">http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org</a><br>
_______________________________________________<br>
clam-devel mailing list<br>
<a href="mailto:clam-devel@lists.clam-project.org" target="_blank">clam-devel@lists.clam-project.org</a><br>
<a href="http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org" target="_blank">http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org</a><br>
</div></div></blockquote></div><br></div>