<div>This are the links of the packages what Ive compiled. I thing they are x86_64 architecture instead the name that the scons gives.</div><a href="http://dl.dropbox.com/u/5675094/CLAM_Annotator-0.5.1%7Esvn14316-i386.dmg" target="_blank">http://dl.dropbox.com/u/5675094/CLAM_Annotator-0.5.1%7Esvn14316-i386.dmg</a><div>
<a href="http://dl.dropbox.com/u/5675094/CLAM_Chordata-1.1.0%7Esvn14316-i386.dmg" target="_blank">http://dl.dropbox.com/u/5675094/CLAM_Chordata-1.1.0%7Esvn14316-i386.dmg</a></div>
<div><a href="http://dl.dropbox.com/u/5675094/CLAM_NetworkEditor-1.4.1%7Esvn14316-i386.dmg" target="_blank">http://dl.dropbox.com/u/5675094/CLAM_NetworkEditor-1.4.1%7Esvn14316-i386.dmg</a><br><br></div><div>If someone could test it on other mac box they could be uploaded to the downloads section of the web ;)</div>
<div><br></div><div>Roberto.</div><div><br><div class="gmail_quote">On Tue, Jun 22, 2010 at 1:23 AM, Roberto Chauderlot Marchamalo <span dir="ltr"><<a href="mailto:rchauderlot@gmail.com" target="_blank">rchauderlot@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br><div class="gmail_quote"><div>On Mon, Jun 21, 2010 at 9:52 PM, 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">
<div>On Monday 21 June 2010 17:25:35 Roberto Chauderlot Marchamalo wrote:<br>
> Hi!<br>
><br>
> I'll try to write in english because I dont want give you more work. But, I<br>
> warn that my english is very very bad.<br>
><br>
> First of all, the way that I 'fixed' the id3lib to make it install was<br>
> change the configuration of mac ports, not really a patch. I changed the<br>
> configuration of the architectures to compile in the "universal" variant.<br>
> It was set to "x86_64 i386", and I seted temporally to "x86_64". It's not<br>
> a good solution, and probably, that library will not work on 32bit<br>
> systems. But, I didn't want to spend a lot of time on it. Anyway, I think<br>
> that I'm building the library for the x86_64 architecture because I'm not<br>
> using any kind of cross compiling directive, but I'm not sure what is the<br>
> default architecture of the compiler.<br>
<br>
</div>Anyway, could you point up the problems (error messages) you found when you<br>
decided took that path?<br>
<div><br></div></blockquote><div><br></div></div><div>I didn't remember exactly, but the error says something like "No executable for platform i386" followed by several compiling errors. So, I decided compile it only for x86_64........I'll try to reproduce the error to report it to macports.</div>
<div><div></div><div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
> I think that a solution for the qt4-mac executables suffixes is add a line<br>
> in clam/CLAM/scons/sconstools/qt4.py after line 226: 219 def<br>
> locateQt4Command(env, command, qtdir) :<br>
> 220 suffixes = [<br>
> 221 '-qt4',<br>
> 222 '-qt4.exe',<br>
> 223 '4',<br>
> 224 '4.exe',<br>
> 225 '',<br>
> 226 '.exe',<br>
> '-mac',<br>
> 227 ]<br>
<br>
</div>Yes, that would work pretty well. Not sure whether it is a general solution<br>
for the qt tool as other users (not just clam as the tool is used for other<br>
projects) would want to use the x11 version. I already filled a bug report for<br>
qt so that this can be obtained from the pc file whatever the situation as now<br>
we could do with moc and uic. Indeed a better solution would be obtaining the<br>
binaries location for moc and uic using pkgconfig and deducing prefixes and<br>
suffixes for the rest.<br>
<div><div></div><div><br>
> I think it will work fine meanwhile the qt4 project fix the pkg-config bug,<br>
> and I think that it's better solution than the unsuffixed symbolic links.<br>
><br>
> Second, I've found why scons doesn't include the soname link while compiles<br>
> the bundle. It's because there is a bug in a scons script of the main lib,<br>
> and it doesn't create the soname link during the install. The bug is in<br>
> file clam/CLAM/scons/libs/clam_build_helpers.py at line 358 and in the<br>
> file scons/sconstools/clam.py at line 186 too: def generate_so_name(<br>
> target, source, env ) :<br>
> source_dir = os.path.dirname( str(source[0]) )<br>
> cwd = os.getcwd()<br>
> os.chdir( source_dir )<br>
> if sys.platform == 'linux2' :<br>
> os.system( "/sbin/ldconfig -n ." )<br>
> os.chdir(cwd)<br>
> return None<br>
> I've modified it to:<br>
> def generate_so_name( target, source, env ) :<br>
> if sys.platform == 'linux2' :<br>
> source_dir = os.path.dirname( str(source[0]) )<br>
> cwd = os.getcwd()<br>
> os.chdir( source_dir )<br>
> os.system( "/sbin/ldconfig -n ." )<br>
> os.chdir(cwd)<br>
> elif sys.platform == 'darwin':<br>
> source_file = os.path.basename( str(source[0]) )<br>
> os.system( "ln -sf %s %s"%(source_file,str(target[0]) ))<br>
> return None<br>
<br>
</div></div>Perfect. Could you send us a patch. When sending changes to code is a lot more<br>
convenient to send them as a patch. This way we can see which code actually<br>
changes and apply it with a single command line. See:<br>
<a href="http://clam-project.org/wiki/Devel#Prepare_and_apply_a_patch" target="_blank">http://clam-project.org/wiki/Devel#Prepare_and_apply_a_patch</a><br>
<div><br></div></blockquote><div><br></div></div></div><div>Yes of course. Here you are!</div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
> With this changes, I could build the Annotator.app, NetworkEditor.app and<br>
> Chordata.app bundles, and all of them include their dependencies. But now,<br>
> they crashes when they init the qt lib. I'm attaching the log that the OS<br>
> throws. I didn't ever work with Qt, and I don't know why it crashes, maybe<br>
> some non-binary dependencies not included in the bundle.<br>
<br>
</div>That's a weird backtrace. It crashes just when creating the QApplication, so<br>
no actual app logic really has happen. The backtrace shows that the crash has<br>
printed out a message maybe in the console, its contents could help to<br>
diagnose.<br></blockquote><div><br></div></div><div>I didn't try to run from console :S It was giving this error:</div><div><div><font face="'courier new', monospace">Macario:MacOS chauder$ ./NetworkEditor </font></div>
<div><font face="'courier new', monospace">Qt internal error: qt_menu.nib could not be loaded. The .nib file should be placed in QtGui.framework/Versions/Current/Resources/ or in the resources directory of your application bundle.</font></div>
<div><font face="'courier new', monospace">Abort trap</font></div></div><div>It seems that otool didn't copy that directory.</div><div><br></div><div>I've read here (<a href="http://doc.qt.nokia.com/4.6/deployment-mac.html" target="_blank">http://doc.qt.nokia.com/4.6/deployment-mac.html</a>) that qt comes with a program to install qt resources in a bundle: macdeployqt-mac. Then I've modified de scons script what build os x bundles, but i did it in the simplest way: calling it directly, with the macdeployqt command "hard-wired" in the script. </div>
<div><br></div><div>And that's it! It works! </div><div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> The problem what I've experienced compiling Chordata was because I didn't<br>
> make the "scons install" of the networkeditor app :P<br></div></blockquote><div><br></div></div><div>For chordata I made an icns file with the ico in the resources folder, but it doesn't have so much quality :S I'm attaching the icns file too.</div>
<div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
><br>
> I don't have so much time, and I don't know if I could lead :S ......but I<br>
> still try to spend some time if I could.<br> </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
</div>Leading just means that previous mac centered clam developers have not been<br>
active for a while, so do not worry on messing someone else work. No one else<br>
doing it, so you lead the task. ;-)<br>
<div><br>
<br></div></blockquote><div><br></div></div><div>Uoo It's a big honor for me!</div><div><br></div><div>Im going to upload to somewhere the dmgs that Ive created, and I'll give you the links (the 3 dmgs: Annotator, NetworkEditor and Chordata, are 500mb). And I'll update the wiki.</div>
<div><br></div><font color="#888888"><div>Roberto.</div></font><div><div></div><div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
> On Fri, Jun 18, 2010 at 9:30 AM, David García Garzón<br>
</div><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: Translated in short. Context: compiling in mac 'snow leopard'.<br>
<div><div></div><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<br>
> > leopard y la arquitectura i386, y hay cosas que no compilan bien.<br>
> > Solucionar el problema de la primera librería fue fácil, existe un<br>
> > paquete que se llama xercesc3 (en vez de xercesc a secas, como pone en<br>
> > la wiki, que es para la versión 2), y este compila bien. Para arreglar<br>
> > la librería id3lib, he tenido que hacer un pequeño apaño y no compilarlo<br>
> > para la arquitectura i386, y hacerlo sólo para la x86_64. Espero que<br>
> > esto no acarree<br>
> > consecuencias después.<br>
><br>
> Trans: problems with xercesc and id3lib; installed xercesc3, id3lib<br>
> patched.<br>
><br>
> Comment: we moved to xercesc3 recently so the option you took is the<br>
> correct. Would be nice if you send the id3lib patch to the list and to the<br>
> macport maintainers.<br>
><br>
> > Por cierto, también os quería comentar que en la wiki sólo indica la<br>
> > manera "deprecated" de instalar jack. Ahora mismo está paqueteado, y se<br>
> > puede instalar fácilmente con un "sudo port install jack". Y tampoco se<br>
> > comenta nada de instalar portmidi, que también está paqueteado y sería<br>
> > lo mismo "sudo port install portmidi". Todo se puede instalar desde<br>
> > macports.<br>
><br>
> Trans: jack and portmidi are available now as ports.<br>
><br>
> Comment: Feel free to update the wiki yourself. If the old methods still<br>
> have sense for old mac version you can move them to a chapter in the end.<br>
> If the macports are available for all the versions, just remove those<br>
> paragraphs.<br>
><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,<br>
> > etc), y los scripts de compilación buscan los normales. Y como no tengo<br>
> > ni idea de scons, lo solucioné creando enlaces simbólicos con los<br>
> > nombres 'linux' apuntando a los de mac y añadiendo las siguientes<br>
> > variable de entorno: 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>
> Trans: clam libs compiled with no problem, apps gave problems with qt,<br>
> qt4-mac suffixes -mac all the binaries. He fixed it by adding unsuffixed<br>
> links and 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<br>
> file a bug in qt. Meanwhile your option should work.<br>
><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>
> Trans: QtDesigner is no more a bundle so the package build which ask for<br>
> the builder fails.<br>
><br>
> Comment: No idea of the implications of QtDesigner not being a bundle on<br>
> how we should package it. Any other mac developer reading?<br>
><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<br>
> > ‘void 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’<br>
> > was not declared in this scope vmqt/CLAM/QtWaitMessageImpl.cxx:35:<br>
> > error: ‘e’ was not declared in this scope scons: ***<br>
> > [vmqt/CLAM/QtWaitMessageImpl.o] 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>
> 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<br>
> we provide when specifying the CPPPATH. If Qt includes are in<br>
> /what/ever/include that directory and also<br>
> /what/ever/include/{QtGui,QtCore,...} should be added. Try to compile with<br>
> the verbose=1 option and send the command line to see which -I options<br>
> appear.<br>
><br>
> > Luego seguí con Annotator, que si que compiló, creo la aplicación ".app"<br>
> > y un dmg para instalarlo, pero cuando intentas ejecutarlo dice que<br>
> > faltan 3 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<br>
> > Lo 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/<br>
> > y<br>
> ><br>
> > no debería. Dyld Error Message:<br>
> > Library not loaded: /opt/local//lib/libclam_core.1.4.dylib<br>
> ><br>
> > Referenced from:<br>
> > /Users/chauder/Documents/Proyectos/clam/clam/Annotator/Annotator.app/Cont<br>
</div></div>> > e nts/MacOS/../Frameworks/libclam_audioio.1.4.dylib Igual, si vuelvo a<br>
<div><div></div><div>> > compilar la librería con la opción de sandbox, esto se soluciona.<br>
><br>
> Trans: Annotator creates the dmg but when installed it complains about<br>
> missing libraries.<br>
><br>
> Comment: We changed the way to name libraries including mac but we didn't<br>
> test mac. So sorry for the inconvenience. Maybe what is missing is a<br>
> 'soname' link with that name pointing to the fully versioned library. If<br>
> that solves the problem tell me and i will add the step in the scons.<br>
><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/<br>
> > D 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>
> ><br>
> > File<br>
> ><br>
> > "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/scons-1.<br>
> > 3 .0/SCons/Environment.py", line 224: return apply(self.method, nargs,<br>
> > kwargs)<br>
> ><br>
> > File "/opt/local/share/clam/sconstools/clam.py", line 166:<br>
> > ' '.join(libs)))<br>
> ><br>
> > File<br>
> ><br>
> > "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/scons-1.<br>
> > 3 .0/SCons/Environment.py", line 1477: return function(self,<br>
> > self.backtick(command))<br>
> ><br>
> > File<br>
> ><br>
> > "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/scons-1.<br>
> > 3 .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>
> 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<br>
> at all. Some scons hacking could be needed to include such library in the<br>
> bundle.<br>
><br>
> > Y luego el programa Voice2Midi tiene las directivas de compilación para<br>
> > crear el "distribuible" a medio hacer.<br>
><br>
> Trans: Voice2Midi is work in progress.<br>
><br>
> Comment: I guess we never really addressed Voice2Midi on mac.<br>
><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<br>
> > los scripts, que están un poco desastrillos :P<br>
><br>
> Trans: Nothing useful from compilation. He will help as he gets expertise<br>
> with 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>
><br>
> > On Mon, Jun 7, 2010 at 3:35 PM, David García Garzón<br>
> > <<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>> > mailto:<a href="mailto:david.garcia@barcelonamedia.org" target="_blank">david.garcia@barcelonamedia.org</a><mailto:<a href="mailto:david.garcia@barcelonamedia" target="_blank">david.garcia@barcelonamedia</a><br>
<div>> > .org>>> 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>
> > > <<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>> > > ><mailto:<a href="mailto:david.garcia@barcelonamedia.org" target="_blank">david.garcia@barcelonamedia.org</a><mailto:<a href="mailto:david.garcia@barcelonam" target="_blank">david.garcia@barcelonam</a><br>
<div><div></div><div>> > > <a href="http://edia.org" target="_blank">edia.org</a>>><br>
> > ><br>
> > > > BTW, Roberto, did you take the wrong link from any clam related page<br>
> > > > we 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<br>
> > > > > > :P<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > He visto publicado el programa CHORDATA en varios blogs de<br>
> > > > > > guitarra y me ha encantado. Llevaba años buscando una<br>
> > > > > > herramienta similar, incluso, empecé a programar algo parecido<br>
> > > > > > en matlab años atrás. Pero nunca llegué a hacer nada funcional<br>
> > > > > > (en otro lenguaje) por falta de tiempo. Así que, os felicito por<br>
> > > > > > el proyecto!!!! Me 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<br>
> > > > > > blanquito aunque no he desarrollado nunca para mac. He intentado<br>
> > > > > > bajarme el código de<br>
> > > > > > <a href="http://clam.iua.upf.edu/download-source.html" target="_blank">http://clam.iua.upf.edu/download-source.html</a> pero me ha dado un<br>
> > > > > > bonito error 500, así que no he podido probar a compilar nada.<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > Entonces, si queréis que os ayude generando la versión para mac,<br>
> > > > > > yo encantado, que le daré buen uso ;)<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > Un saludo!<br>
> > > > > > Roberto<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-proj" target="_blank">clam-devel@lists.clam-proj</a><br>
</div></div>> > > > > <a href="http://ect.org" target="_blank">ect.org</a>><mailto:<a href="mailto:clam-devel@lists.clam-projec" target="_blank">clam-devel@lists.clam-projec</a><mailto:<a href="mailto:clam-devel@list" target="_blank">clam-devel@list</a><br>
> > > > > s.clam-projec> <a href="http://t.org" target="_blank">t.org</a><<a href="http://t.org" target="_blank">http://t.org</a>>><br>
<div>> > > > > <a href="http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project" target="_blank">http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project</a>.<br>
> > > > > o rg<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-projec" target="_blank">clam-devel@lists.clam-projec</a><br>
</div>> > > > <a href="http://t.org" target="_blank">t.org</a>><mailto:<a href="mailto:clam-devel@lists.clam-project" target="_blank">clam-devel@lists.clam-project</a><mailto:<a href="mailto:clam-devel@lists.c" target="_blank">clam-devel@lists.c</a><br>
<div>> > > > lam-project>. org><br>
> > > > <a href="http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.or" target="_blank">http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.or</a><br>
> > > > g<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" target="_blank">clam-devel@lists.clam-project</a>.<br>
</div>> > > org><mailto:<a href="mailto:clam-devel@lists.clam-project.or" target="_blank">clam-devel@lists.clam-project.or</a><mailto:<a href="mailto:clam-devel@lists.cl" target="_blank">clam-devel@lists.cl</a><br>
<div>> > > am-project.or> g><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>
> > <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>
</div>> > g><mailto:<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-" target="_blank">clam-devel@lists.clam-</a><br>
<div>> > <a href="http://project.org" target="_blank">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>
><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.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>
</div></div></blockquote></div></div></div><br>
</blockquote></div><br></div>